Skip to content

Prepare v5.0.0 server compatibility - #18

Merged
valzargaming merged 22 commits into
mainfrom
v5-server-compatibility
Oct 22, 2026
Merged

valzargaming merged 22 commits into
mainfrom
v5-server-compatibility

Conversation

@valzargaming

@valzargaming valzargaming commented Oct 12, 2026 •

Copy link
Copy Markdown
Member

Behavior

Prepares v5 development source across engine-aware lifecycle routing, bounded LF file IPC, durable relay checkpoints, awaited list/unban writes, webhook delivery and source tooling. Main 821afe15822b5ecf5417210854970661394a0682, including merged #15 and #20, is integrated.

  • Admin-list message/panel replies await settlement; HTTP distinguishes observed success/failure from pending queueing. Staff lifecycle/map-select callbacks acknowledge privately before effects and await completion. Map message replies render structured engine receipts as text.
  • Preserves native supervisor readiness, OpenDream process completion and legacy scheduling distinctions, staff checks, disabled adapters and pending/unknown outcomes.
  • Fixes a migration defect: role-list updates retain the existing file object, mode/owner/ACL rather than replacing it with a temporary file. Complete writes, truncation and flush are checked. Native readers can still observe partial in-place updates; failures do not promise rollback or crash/power-loss atomicity.
  • Adds focused file-object/POSIX metadata, shorter/empty-list and failed-destination regressions. Existing Windows PHP 8.3–8.5 CI now runs IPC/list and durable-relay fixtures with two-minute step limits; Ubuntu runs them under the same bound.
  • Marks development source 5.0.0-dev, verifies source-derived API provenance and documents configuration/dependency/checkpoint migration and durability limits. Publication remains separate.

Verification

Final source head: 3cfd4b9e47891179e3c632af63c5305881f5dd45.

Final source review and later release

Completed exact-head Codex source review is recorded as a COMMENT review, with evidence and limits. This is not an independent maintainer APPROVE event. The normal merge completed as d276e97dc8b9bea1b86226c4dfbe485d71e43af5.

The ledger in docs/releases/v5.0.0.md separates reviewed source migration/durability from installation cutover and stable release. It supplies bounded offline follow-up commands and resource/effect limits. Real native/OpenDream lifecycle, Topic/player readiness, five game IPC consumers and actual Discord delivery remain unaccepted. They require an owner-supplied existing harness, isolated fixture/ports and separately coordinated approval; they remain activation/release gates, and source review does not authorize them. Installation-specific migration approval, fresh authorized Pages publication/readback and stable tagging remain later gates.

No official registration, runtime checkout update, bot/game control, deployment, credentials, production data or consumed test-reservation change occurred. OpenDream remains paused.

Final combined-head CI: all 58 substantive check records are completed/success; the separate publication job is completed/skipped. No pending or failed records remained before merge. Publication is not established by that skipped job.

@valzargaming
valzargaming marked this pull request as ready for review October 22, 2026 18:38

@valzargaming valzargaming left a comment

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Completed Codex source review of exact head 3cfd4b9 against main 821afe1.

No blocking source defect found in the reviewed engine-aware lifecycle routing, async message/panel/HTTP caller settlement, IPC framing and list-file metadata preservation, durable relay checkpoints/replay limits, configuration/dependency migration, development-version/API provenance and source tooling. The latest integration is a conflict-free merge of already merged #15. A separate source-only comparison of both parents found no regression in safehouse/v5 Slash coexistence, options defaults or native controls. Safehouse and directory remain disabled without explicit configuration.

Exact-head evidence was checked through workflow records and actual job steps: PHP 8.3–8.5 supervision/consumer/IPC/relay fixtures (https://github.com/Valgorithms/Civilizationbot/actions/runs/39874721044); Windows/Linux portable contracts, including all three Windows IPC/list and relay steps (https://github.com/Valgorithms/Civilizationbot/actions/runs/39874721157); combined safehouse spool/economics and injected Discord/schema fixtures (https://github.com/Valgorithms/Civilizationbot/actions/runs/39874721098); read-only API build/links/search/exact-source development provenance (https://github.com/Valgorithms/Civilizationbot/actions/runs/39874721029); locked-dependency, source MCP and heartbeat lanes. All 58 substantive check records are completed/success. The one publication job was skipped and supplies no publication acceptance. The only new local execution was syntax/whitespace checking; no broad local suite, install, game or bot ran.

Limits: this COMMENT records the completed Codex source review, not an independent maintainer APPROVE event. List updates preserve existing file access metadata but are in-place: native readers may observe partial contents and rejection does not promise rollback. Relay delivery is at least once; host power-loss guarantees and installation-specific cutover remain unaccepted. Real native/OpenDream lifecycle/Topic/player readiness, actual game IPC application/Discord delivery, registration, Pages publication and stable release remain separately authorized activation/release gates in docs/releases/v5.0.0.md. No runtime checkout, live Gaia, bot/game controls, credentials, production data or consumed test reservation changed.

@valzargaming
valzargaming merged commit d276e97 into main Oct 22, 2026
59 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant