Repository navigation
World: canonical admission holds, typed finalization and placement - #3044
benhook1013 wants to merge 36 commits into
Conversation
…it1b-authenticated-world-preparation
…it1b-authenticated-world-preparation
…it1b-authenticated-world-preparation # Conflicts: # design/project-management/implementation-tracking/world-runtime-and-movement.md
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configuration
You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
…ex/unit1b-authenticated-world-preparation
Codecov Report❌ Patch coverage is 📢 Thoughts on this report? Let us know! |
…it1b-authenticated-world-preparation # Conflicts: # design/project-management/implementation-tracking/world-runtime-and-movement.md
Validation Summary❌ One or more validation checks failed
Coverage reports and failure logs are available in the workflow artifacts. |
…it1b-world-canonical-hold-preparation-20261007 # Conflicts: # design/project-management/implementation-tracking/world-runtime-and-movement.md
…it1b-world-canonical-hold-preparation-20261007 # Conflicts: # design/project-management/implementation-tracking/game-authoring-publishing-and-activation.md
Boundary
Published
59eb1d22ac3ec906a64d2db378c79f3353e263d3, 87 unique files, stacked on Game Design prerequisite #3055d3ec30d5de9a9011b77eaa39649ef04cf1a2e1e2. This coherent World boundary includes authenticated canonical preparation/activation carriers, operational-region allocation, canonical first-admission acquisition/readback, exact ACTIVE read, typed terminal reconciliation and placement/current-location consumers. It is not enabled activation or completed LOGIN → PLAY → LOOK proof.The complete canonical identity comes from independent authenticated Game Design and Game Session evidence and actual World source/association/materialization storage. Private numeric IDs do not substitute for UUID ownership. Historical preparation/activation/terminal receipts do not supply current admission authority. Canonical and operational region UUIDs remain distinct.
Canonical hold and terminal handoff
NO_PRIOR_POINTERandEXPECT_CLOSED, to the complete canonical scope, current ACTIVE instance/version/epoch, immutable operation and World hold identity. Retained legacy rows remain untyped and uninferred; termination checks still include them.NO_PRIOR_POINTERorEXPECT_CLOSED, preserving V46/V49 history and every other canonical request/result/immutability check. New SQL negatives deny null and unknown origins without creating an operation or location.EXPECT_CLOSEDrequires genuine Game Session proof of the exact never-OPEN catalog pointer, not missing history or a fixture assertion. Actual ACTIVE lifecycle, authored ROOM mapping, actor/assignment and immutable APPLIED readback remain independently checked.Preparation, activation and player-location adapters remain unregistered/default-denied where their genuine held-authority producer is missing. No runtime activation, canonical writer, membership RPC, credential path or key-ring mount is enabled. Movement/occupancy delivery, family registration, replay/cleanup retention and live owner composition remain open.
Validation and preservation
Normal merge of #3055 preserved all World implementation/test hunks byte-for-byte; only the shared authoring tracker conflict was reconciled to retain both producer and consumer obligations. The composed World/Game Design local fullCheck, both boot JARs and docs gate passed in 2m 03s. World test/integration execution tasks were UP-TO-DATE: their retained XML shows 511 executed unit cases and 197 integration skips, not fresh PostgreSQL execution. Game Design source tests and static checks were included; Docker is unavailable. This head needs its own CI; the historical exact 0ace proof below is not attributed to 59eb. No preserved history was rewritten.
At exact published head
0ace6389ec0e85e1a2a29ffa0be420f7583cb1f0, CI 37577805764 completed: World Build/Test passed. Actual runner checkoutf81346b7f999110404dc7a04f682e365d6da5349has ordered #3041/head parents and a head-identical tree. Raw Graph XML proves 52 PostgreSQL cases executed with zero failures/errors/skips, including EXPECT_CLOSED placement, canonical placement/retry, null/unknown-origin no-mutation denial and retained V39/V41 history; V50 applied. Raw XML SHA-256 is80d6b4b89a8bf1fe40254698d9f942f4744ee2b4a021e3360330fab569dfc92a. The full verifier reports 101 suites/708 tests, but the bounded captured artifacts do not establish all 197 unique integration definitions or separately capture the three operational-region cases. Do not replace those proof limits with an inferred count. Aggregate failed in Game Session, TCP and Validation Gate; their latest causes are not relabeled from older runs. Upstream owner inputs in World fixtures remain explicitly isolated, not live Game Session/Account/Game Design proof.The corrected World full gate passed in 2m 16s with the build cache disabled: 511 unit cases executed with zero failures/errors/skips; all 197 integration definitions compiled/discovered but skipped locally without Docker. jOOQ generation, formatting, Checkstyle, SpotBugs, coverage, boot JAR, links and Markdown passed. A final documentation-only gate passed after the tracker clarification. This is not corrected PostgreSQL execution or live owner proof. Physical mTLS units retain explicit owner-store/result doubles.
Prior exact head
a36b152fdaf7f5bb5447094cd72718c66f7977deCI 37573659922 executed 196 World integration cases, zero skips, with three failures. Named PostgreSQL suites: graph/application51 cases/two failures and operational-region3 cases/one failure. Runner mergea9ada9077941141a1d3f8b315d1a0bb0cb1ae0f5has the exact base/head as ordered parents and a head-identical tree. The owned SQL omission rejected legitimate EXPECT_CLOSED placement; V50 supplies its forward correction. The changed actor/assignment fixture now expects the earlier complete-request denial and compares unchanged operation/location storage. The operational-region fixture now expects Spring’s translated integrity exception and the actual immutable-tuple denial, retaining all four attempted substitutions. The connection pool was not the failure cause. The exact current Graph execution above supersedes its corrected-state gap; full-suite and live owner limits remain explicit.Normal source merge retains exact #3035
1b38b0d5c6c7aa5558ec985e50227bb4bf0b4258and preserved World history without rewrites. Source adds three actual Account SQL-store/reconciliation-service cases with explicit synthetic remote-owner responses. Its focused source and composed-child checks pass; selected23 cases all skip locally without Docker. Earlier synthetic capture tests are not counted as database proof. Published migration order and Gameplay’s complete owner-proof codecs/API remain intact.The prior aggregate was also red on Game Session’s unchanged retained-tenant suite (17 cases/three failures) and required LOGIN capture, plus TCP javac heap exhaustion. All Game Session paths are byte-identical to #3041; Gameplay owns the retained-mapping and final-playable consumer correction, with receiving PR unassigned until published. These do not justify weakening the World guard. Exact corrected CI is completed with World success and an outside-World aggregate failure; no aggregate-green or merge-ready claim is made.
Earlier source database proof — not this new migration proof
Source #3035 CI 37569958133 executed 128 PostgreSQL cases plus three non-database component cases, all without failures or skips. Database cases: Account Draft fence 19, JOIN event 7 and publication fence 20; Game Design publication operation 12 and Draft publish selection 9; World graph/application 34, association 12, Draft abort 7 and publication fence 8. Account terminal reconciliation's three cases use mocked repository/clients and a synthetic transaction manager; they are not PostgreSQL or authenticated two-owner settlement proof. The three owner jobs checked out synthetic merge
1f2788d887969c92d754a45bf5133afdd06e626c, whose tree is identical to sourcea9f32559f. Actual capture verifies the bounded repair removed only the redundant filtered Account rerun while retaining strict proof verification.That source run's aggregate remains red: TCP reported 13 failures among 17 cases, including
PLAY_IDENTITY_UNAVAILABLEafter LOGIN; Game Session was cancelled. The component fixtures isolate upstream authority and do not establish genuine multi-owner authorization, this later V47–V49 database behavior or a playable flow. The current exact-head World result above is consumed and does not establish an enabled multi-owner flow.Remaining mission and review limits
All four Gameplay handoffs remain OPEN: original Account-authorized World APPLIED; genuine immutable Game Design release; authenticated World prepare/ACTIVE with actual Game Session/Entity actor and operational-region delivery; and Account settlement after both exact owner outcomes. Frozen Game Design realm-entry policy delivery is a concrete producer gap recorded in the authoring tracker, not inferred from a roster or numeric source version.
This draft remains outside the configured queue. No provider review, corpus taper, merge readiness, deployment or live owner proof is claimed. FireController retains the bounded Luna implementation/verification records and historical checkpoint evidence.
FireMUD LOC impact
Compared
d3ec30d5de9a→59eb1d22ac3e(PR merge-base → head).PR scope: 87 changed files · 22,809 added textual lines / 71 deleted textual lines.
Rows are hierarchical and overlapping views; do not add them together.
LOC means cloc code lines; blank and comment-only lines are excluded.