Owner: Codex in the triage and delivery thread. Updated . -88 of 88 issues assessed. Source revision b1c0f9400a31a2522b9385f6870a9eb8f8f92c76.
-All 88 issues are assessed. Aura rollback and fixture cast protection are merged. Motion diagnostics are merged; the reported long-running freeze remains unverified. The second wave is underway.
Owner: Codex in the triage and delivery thread. Updated . +89 of 89 issues assessed. 77 open on GitHub. +Source revision b4c17c481f66784fd24677f583e0368fc3ac8c95.
+77 open issues assessed; 12 closed issues retained for history. Finishing existing PRs and implementing the next independent checks.
-Importance measures the cost of leaving the problem open. Gain measures reach and the work it unlocks. Both use 1 to 5, with 5 highest. Effort uses 1 for a small local change, 3 for a substantial slice, @@ -42,12 +43,13 @@
| Order | Issue and assessment | Importance | Gain | Effort | Return | -State and owner | Next action |
|---|---|---|---|---|---|---|---|
| 1 | #63Loot-roll promotion remains non-idempotent: concurrent Gateways can create duplicate rolls and split the party's votes.The current Gateway still promotes a staging roll on Realm-core and only then clears the World Shard copy. Both periodic and synchronous promotion paths can run in different Gateway processes. Realm-core's game_loot_roll has only an auto-increment primary key and insert_roll_rows always inserts a new roll and vote set. Module reducers serialize calls, so an idempotent Realm-core check or a compatible uniqueness key can close the race at its authoritative side. Confidence: high. Issue updated 2026-08-11.
| 5 | 4 | 3 | 6.7 | In progress GPT-6 Astra, loot-roll agent | A private concurrent START test reproduced two rolls and now passes with one complete vote set. Finish validation and review. Delayed replay after a resolved roll is deleted remains a separate lifecycle gap. |
| 2 | #367Locked GOOBER use bypasses its openerThe Defias Cannon can trigger without its required item. Current GOOBER dispatch skips locked_shut, while CHEST and DOOR/BUTTON apply it. Confidence: high. Issue updated 2026-08-28.
| 3 | 4 | 2 | 6.0 | In progress GPT-5.6 Sol, GOOBER agent | Prove locked refusal has no effects, then apply the existing lock Gate and verify unlocked and lockless use. |
| 3 | #398Trust Review omits shipped Package DeltasRuntime Script names already landed in CLI PR #55. The remaining Datascript line falsely says nothing reads them. It obscures what an Operator installs. Confidence: high. Issue updated 2026-09-03.
| 3 | 4 | 2 | 6.0 | In progress GPT-5.6 Sol, CLI review agent | Implement generated Package Delta counts in an isolated CLI worktree. Test through fake adapters, publish the CLI PR, then make a core pin PR after reviewed merge. |
| 4 | #80A cross-map teleport still removes the Character's world entity without deleting its public motion row, leaving a stale AOI-visible row on the source Shard.The exact outlier remains in current code. teleport_player drops only game_entity_motion_pending, then deletes game_world_entity in the cross-map branch. Other teardown paths delete the public motion row. Confidence: high. Issue updated 2026-08-11.
| 4 | 3 | 1 | 12.0 | PR review GPT-5.6 Sol, teleport agent | Coordinating review and all CI checks passed. CodeRabbit is rate-limited; request its review after the window reopens at about 07:18 UTC. |
| 5 | #346Finish enforcing the repository checks in CIThe claim that no workflows exist is stale. Rust tests and wasm checks now run; formatting and clippy remain advisory until PR #419. PR #426 adds durable tests. Confidence: high. Issue updated 2026-08-28. Blocked by
| 4 | 5 | 3 | 6.7 | PR review Codex | Finish the existing CI PRs and record which preflight coverage remains before closing this umbrella issue. |
| 6 | #353Make workspace lint checks pass and block regressionsPR #419 already implements the cleanup and blocking checks. Its branch conflicts with current main and is under active review in another worktree. Confidence: high. Issue updated 2026-08-28. Blocked by
| 4 | 5 | 3 | 6.7 | PR review Codex | Monitor the existing owner, rebase after the other open PRs, and require fresh blocking checks. |
| 7 | #50The character-owned Architecture Test still misses tables that refer to a Character through unit-shaped columns such as target_guid or attacker_guid.The source scanner still recognizes only character_guid, player_guid, and owner_guid. Existing manual cleanup for aura, melee, threat, and combo state shows that unit-keyed tables remain a real transfer blind spot. This is a localized Architecture Test change that prevents future cross-database state loss without changing runtime behavior. Confidence: high. Issue updated 2026-08-11.
| 4 | 4 | 2 | 8.0 | Ready Codex | Extend character_owned_tripwire to inventory unit-guid columns and require each discovered table to have character_owned markers or an explicit exclusion with a reason; add a scanner fixture that fails on an unclassified target_guid table. |
| 8 | #368Detect generated Gateway binding drift in CISubscribed-table parity leaves other generated definitions unchecked. A reproducible generation check would catch drift before unrelated schema work encounters it. Confidence: high. Issue updated 2026-08-28. Blocked by
| 4 | 5 | 3 | 6.7 | Ready Codex | Build a deterministic offline generation check using the documented exceptions, after the active CI cleanup settles. |
| 9 | #341Service unit parsing misses continued directivesThe CLI parser still splits physical lines. Continued directives can hide a conflicting Standalone service. The fix is testable without changing a host. Confidence: high. Issue updated 2026-08-26.
| 4 | 3 | 2 | 6.0 | Ready Codex | Implement systemd logical-line parsing through the existing process Fake and test tracked and conflicting units. |
| 10 | #75The pinned raid benchmark neither reports dead Characters nor sends Release Spirit, so later additive stages can silently measure a mostly inactive population.The exact harness release named in the issue is still pinned. Its benchmark source has raid mode but no death counter, CMSG_REPOP_REQUEST, or revive flow. Reporting the count is a bounded first slice that restores measurement honesty. Confidence: high. Issue updated 2026-08-11. Blocked by
| 4 | 4 | 3 | 5.3 | Ready Codex | Add a dead-at-window-end count to the wire-harness benchmark report and tests first. Treat automatic Release Spirit and recovery as a second protocol slice, then release and bump the LyraCore pin. |
| 11 | #340Service Reconciliation misses effective command driftThe current verifier reads ActiveState, LimitNOFILE and StandardError. It does not compare the effective ExecStart or name relevant drop-ins. A success report can therefore describe the wrong service. Confidence: high. Issue updated 2026-08-26.
| 4 | 4 | 3 | 5.3 | Ready Codex | Compare the effective command with the tracked contract and report overriding drop-ins, using a process Fake. |
| 12 | #40Early Warlock pet quest chains still lack the imported hostile summon encounters and item-use path needed to earn the Voidwalker and Succubus.This is the strongest ready feature candidate because it restores core class progression and the issue already names concrete creatures, items, and spells. Most behavior can be covered with Module and Headless Client Gates; only the final presentation check needs a human. Confidence: high. Issue updated 2026-08-11. Blocked by
| 4 | 4 | 4 | 4.0 | Ready Codex | Write a scoped Ticket for the hostile ownerless summon effect, required importer rows, item-use route, and kill credit, then implement it with Headless Client coverage and leave the visual check for a real client. |
| 13 | #272A creature that enters a viewer's AOI during an active movement leg can stand still and then jump forward; delayed motion flushes and the four-second sensing cadence can produce similar symptoms.The cheapest defect is still present: peer CREATE replays a resident taxi spline but never the creature's current spline. Motion shedding and sensing cadence are separate policy choices, so they should not hold up that localized fix. Confidence: high. Issue updated 2026-08-18. Blocked by
| 3 | 4 | 3 | 4.0 | Ready Codex | Implement resident creature-spline replay immediately after peer CREATE with an ordering test. Split motion shedding and sensing cadence into separate decisions before changing either. |
| 14 | #72SpellCastEvent still multiplexes several wire signals through independent booleans and zero-value conventions.The row contains is_completion, is_interrupted, delay_ms, and is_proc_log alongside ordinary START and GO fields. The Gateway decodes them in ordered branches, while comments state which fields must be the only active signal. Typed signal constructors reduced literal duplication but do not enforce mutual exclusion. An additive kind would make the union explicit, but schema publication and generated bindings make this more than a local refactor, and the unused is_completion field needs a compatibility choice. Confidence: high. Issue updated 2026-08-11.
| 3 | 3 | 3 | 3.0 | Ready Codex | Approve an additive event-kind contract and is_completion policy, then stamp every constructor, regenerate Gateway bindings, switch decoding to the kind, and publish all fixture databases before removing reliance on the old fields. |
| 15 | #137Bank storage and purchase behavior are implemented, but the pinned Headless Client has no end-to-end bank adapter and the stock-client window has not been checked.The parent and both blocking code issues are closed. Current Gateway paths cover activate, deposit, withdraw, and slot purchase, while the pinned adapter tree has no bank script. Confidence: high. Issue updated 2026-08-12. Blocked by
| 3 | 3 | 3 | 3.0 | Ready Codex | Add the bank-flow adapter in wire-harness, release it, and bump the pin. Then run the adapter and the listed real-client window checks on an approved development Realm. |
| 16 | #142Drowning works in Module and Gateway tests, but there is no pinned Headless Client adapter for a complete dive cycle and no real-client calibration of the submerge threshold.The code half shipped in PRs 150 and 166. The pinned wire-harness tree contains no drowning or breath adapter, so a bounded cross-repository implementation remains before the human pass. Confidence: high. Issue updated 2026-08-13. Blocked by
| 3 | 3 | 3 | 3.0 | Ready Codex | Add the LyraCore dive adapter in wire-harness with no stored credentials, then release and bump the pin. Run it on an approved development Realm before calibrating the real client. |
| 17 | #31Random item properties are absent from imported data and item state, and all relevant Gateway packet paths still emit random property id zero.This is the second-best ready feature candidate. The issue has a current two-Ticket Spec, the missing storage and packet fields are confirmed in code, and the first Tracer can establish one deterministic affix end to end without a design decision. Confidence: high. Issue updated 2026-08-22. Blocked by
| 3 | 4 | 5 | 2.4 | Ready Codex | Implement the Spec's Tracer Ticket first: import the minimum property data, persist one rolled property, and carry it through loot, inventory, mail, and auction packets; follow with the weighted generalization Ticket. |
| 18 | #30The Realm has no seasonal game-event data model, calendar activation, spawn participation, or Operator debug controls.The issue has a detailed current Spec and carries the ready-for-agent label. It is implementable, but it spans importer data, persistent state, spawn lifecycle, calendar logic, and tooling, so it should be split before code work begins. Confidence: high. Issue updated 2026-08-21.
| 2 | 4 | 5 | 1.6 | Ready Codex | Split the Spec into a deterministic single-event Tracer, calendar generalization, spawn integration, and Operator control Tickets, then implement the Tracer first. |
| 19 | #28Drink item use does not create or decay an inebriation state, update PLAYER_BYTES_3, or apply chat slurring.The feature is self-contained once the exact 1.12 field encoding, decay rate, and text transform are taken from a primary reference. No competing architecture or open dependency is visible. Confidence: high. Issue updated 2026-08-11.
| 2 | 2 | 4 | 1.0 | Ready Codex | Confirm the 1.12 constants and transform from a primary emulator source, then implement persistent inebriation, timed decay, PLAYER_BYTES_3 projection, and deterministic chat Gates as one Ticket. |
| 20 | #60The two historical crashes during roughly 500 simultaneous disconnects have no current rerun, so core availability is still unverified.The Gateway has since gained pre-auth deadlines, bounded blocking-task admission, file-descriptor checks, and more resilient accept handling, all of which can change failure behavior. None proves that the post-auth mass-disconnect crash is gone. The issue's done condition remains two clean Runbook B runs with process, kernel, and application evidence. Confidence: high. Issue updated 2026-08-11. Blocked by
| 5 | 4 | 3 | 6.7 | Verify existing work Codex | Run the pinned Headless Client Runbook B twice against the current release Gateway, recording exit status, kernel OOM or signal evidence, file descriptors, task counts, session cleanup, and recovery. |
| 21 | #424Motion delivery can stop until the Gateway restartsAn offline test now proves that 172 healthy motion callbacks can produce the reported warning when the mover has no peer viewer. The current counter counts peer packets. The report does not yet prove a stopped subscription or a root cause for visible freezing. Confidence: medium. Issue updated 2026-09-04.
| 5 | 5 | 4 | 6.2 | Verify existing work Codex | Use the new per-Shard queue, callback and pump diagnostics to reproduce a stopped stream. A real-realm capture requires a named host and authorization; the original 15-hour freeze is not yet explained. |
| 22 | #46A deleted Character previously left a realm-core party member row, but the Gateway now relays Character disappearance and removes membership only after the Character is absent from every Shard.PR #384 implements the missing cleanup while preserving Transfer safety. The workaround named in the issue is no longer present, so this open issue appears stale and needs a focused regression check before closure. Confidence: high. Issue updated 2026-08-11.
| 4 | 4 | 1 | 16.0 | Verify existing work Codex | Run the existing party cleanup and Transfer tests against main, then close the issue if both pass. |
| 23 | #88Movement heartbeat batching is already active at 40 ms with 128-entry calls; the remaining work is an approved load acceptance run and tuning only if its timing signals regress.The current code contradicts the original title: gw_movement_batch, chunking across call pipes, entry isolation, and metrics all exist. PR 234 added a guarded acceptance runner but explicitly left the 500-mover and real-client checks undone. Confidence: high. Issue updated 2026-08-11. Blocked by
| 4 | 5 | 2 | 10.0 | Verify existing work Codex | Run docs/movement-batch-acceptance.md against an approved disposable Realm with at least 500 movers, record batch factor and both latency signals, and tune one lever only if the tripwire fires. |
| 24 | #399Replay no longer needs client data for a completed planCurrent CLI main reads target provenance before resolving client data. The script-only no-op test already runs without client data. The original control-flow complaint appears fixed by the replay work. Confidence: high. Issue updated 2026-09-02.
| 3 | 3 | 1 | 9.0 | Verify existing work Codex | Run the empty-inventory/no-client regression against the pinned CLI, then close with evidence if it passes. |
| 25 | #84The current Gateway has explicit world-Shard promotion to Realm-core and settlement fan-out, but the reported three-Shard failure has never been rerun against this implementation.Current Store code and Fake-based tests cover the topology the issue said was suspect. That is meaningful newer evidence, but it does not reproduce the exact development stack. The issue also combines an unrelated bot-party combat failure that should be split if it remains. Confidence: medium. Issue updated 2026-08-11. Blocked by
| 4 | 4 | 2 | 8.0 | Verify existing work Codex | Rerun group loot on a fresh current three-Shard development stack with schedules armed. If it fails, capture promotion, Realm-core resolution, and settlement rows separately. Split any bot-party combat failure into its own issue. |
| 26 | #59The old crowd-cliff numbers cannot answer current capacity after movement and Relay changes; Runbook A still needs a fresh end-to-end run.The current movement model writes one row per mover and uses AOI selection instead of the former per-recipient event rows. PR #421 also reduced distributed event Relay work, but its benchmark explicitly measured selection and encoding rather than realm capacity or latency. The 150/371-client measurements therefore describe neither the current writer load nor the current Gateway work. Confidence: high. Issue updated 2026-08-11. Blocked by
| 4 | 5 | 3 | 6.7 | Verify existing work Codex | Run Runbook A against a release build at the current main commit and publish capacity, latency, disconnect, writer-occupancy, QUEUESTAT, AOISTAT, and SHARDLOAD results with exact revisions. |
| 27 | #86Per-viewer motion supersession is implemented, but there is no current evidence that dense-crowd login starvation still has the 2026-08-09 shape after the shared WorldView changes.The first coalescing rung is present. Later work replaced per-Character subscriptions with one per-Shard stream and an in-memory cell index, invalidating part of the old cost account. Dense fan-out is still inherently large, but a login-priority lane or interest cap needs fresh evidence. Confidence: medium. Issue updated 2026-08-11. Blocked by
| 4 | 5 | 3 | 6.7 | Verify existing work Codex | Run the current dense-crowd measurement from issue 59 and record login completion, queue depth, relay latency, CPU, and delivered motion. Choose a priority lane or interest cap only if starvation reproduces. |
| 28 | #104The Rust CLI now has import world and import vmaps, but fresh-provision parity is unrecorded and the old import-world.sh still exists.lyracore-cli PR 25 implemented the verbs and the current pin includes them. That PR explicitly left fresh-provision Verification and retirement of the script for later, and the script remains in the tree. Confidence: high. Issue updated 2026-08-11. Blocked by
| 3 | 4 | 2 | 6.0 | Verify existing work Codex | Run import world and import vmaps on a fresh approved development stack. If their results match the old flow, inventory remaining script consumers, repoint them, and delete import-world.sh. |
| 29 | #55The residual crowd disconnects remain unclassified and require a fresh correlated load run.The issue's static audit found no corruption path and deliberately parked the symptom until logs could separate peer exits, writer failures, and subscription recovery. The Gateway still logs the terminal World Session error, while the current movement and load-shedding paths have changed enough that the old 3 to 8 per 150 result cannot establish today's behavior. Confidence: high. Issue updated 2026-08-11. Blocked by
| 3 | 3 | 3 | 3.0 | Verify existing work Codex | Run the current crowd scenario with stable peer IDs and collect Gateway session-end causes, Headless Client disconnect reasons, QUEUESTAT, AOISTAT, and SHARDLOAD for the same time window. |
| 30 | #78GridBox still recenters at every cell crossing, but this no longer tears down SpacetimeDB subscriptions; it now applies a bounded in-memory index delta and may cause only entity create and destroy churn.The original measured subscription cost is retired by the shared WorldView. Widening the AOI to 7 by 7 would raise steady audience and relay work, so the old proposed fix should not ship without new evidence of visible churn. Confidence: high. Issue updated 2026-08-11. Blocked by
| 2 | 2 | 2 | 2.0 | Verify existing work Codex | Measure current AOI recenter deltas and client create and destroy traffic near cell boundaries. Close as superseded if bounded in-memory churn is harmless; otherwise write a new Spec that prices the wider AOI. |
| 31 | #103The dynamic door-collision parent has one imported-mesh slice shipped, while runtime collision and instance-aware acceptance remain in issues 113 and 114.The parent is now a tracker rather than an implementation unit. Its original request for a Spec and split is complete, but the implemented behavior is not. Current eligibility conflicts must be resolved in issue 113 before the parent can advance. Confidence: high. Issue updated 2026-08-11. Blocked by
| 4 | 5 | 1 | 20.0 | Dependency Codex | Keep this as the parent. Resolve issue 113's eligibility decision, implement 113, then complete issue 114 and close the parent from its acceptance evidence. |
| 32 | #105The pinned Headless Client suite still invokes file-based scenarios relative to the LyraCore checkout, so many scenarios fail to spawn while the summary looks like an ordinary test failure.The current pin is still v0.1.0-alpha.3 at the exact reported commit. Its wire-suite.sh contains the broken relative calls, and no newer release exists. This undermines confidence in every live suite claim that uses the pin. Confidence: high. Issue updated 2026-08-11. Blocked by
| 4 | 5 | 3 | 6.7 | Dependency Codex | Fix every scenario call to use ADAPTER_DIR, add subset arguments and a distinct spawn-failure summary in wire-harness, then publish a release and bump the LyraCore pin. |
| 33 | #66The two-Gateway capacity experiment remains valuable, but its baseline and three correctness prerequisites are still open.The duplicate bot-invite defect in #62 is fixed, while #61, #63, and #65 remain. The coordinator and Relay cost model also changed: shared Shard connections and cell audiences make the issue's original query-count assumptions stale. A second Gateway measurement can decide whether horizontal Gateway scaling earns its operational cost, but only against a fresh one-Gateway baseline and after known cross-process corruption paths are closed. Confidence: high. Issue updated 2026-08-11. Blocked by
| 4 | 5 | 4 | 5.0 | Dependency Codex | Complete #59, #61, #63, and #65, then run one and two Gateway processes against the same Realm with identical Headless Client load and compare writer occupancy, subscriptions, Gateway CPU, latency, and disconnects. |
| 34 | #64The Gateway still has no SIGTERM drain path and both listeners end only when their tasks fail.Current main binds ordinary Tokio listeners and does not register a Unix signal handler. A stop therefore does not close admission, wait for World Sessions, or perform orderly logout. Session leases reduce how long crash residue survives, but they do not provide a drain. The issue correctly waits for #60 because mass teardown behavior must be known before building shutdown around it. Confidence: high. Issue updated 2026-08-11. Blocked by
| 4 | 4 | 4 | 4.0 | Dependency Codex | After #60, add a shared shutdown signal that closes both listeners, stops new logons, drains World Sessions to a deadline, records clean logout, and exits with observable phase logs. |
| 35 | #65Logon still advertises one configured world address and has no Realm-core registry of Gateway address, load, or draining state.The logon Store returns a one-element realm list built from the configured world address. Realm-core has per-Gateway Shard load samples, but their gateway_key is a hash for accounting rather than a routable address, and no row says a Gateway accepts new World Sessions or is draining. The old estimate that selection is a tiny change no longer matches the required registration and lease work. Confidence: high. Issue updated 2026-08-11. Blocked by
| 4 | 4 | 4 | 4.0 | Dependency Codex | After #69, define a leased Gateway process row on Realm-core with advertised address, admission state, and load; make realm-list selection deterministic and test drain exclusion and stale-row expiry. |
| 36 | #114Instance-aware door collision and Deadmines acceptance cannot start until dynamic door collision exists and its map-36 eligibility conflict is resolved.The ray functions and debug reducer still lack instance_id. Issue 113 is unimplemented, and current vmap eligibility requires an active static generation even though the canonical import skips open-world vmaps on the Instance Pool. Confidence: high. Issue updated 2026-08-13. Blocked by
| 4 | 4 | 4 | 4.0 | Dependency Codex | After issue 113 has an approved eligibility rule and implementation, thread instance_id through ray callers and run isolated sibling-instance tests before the Deadmines acceptance run. |
| 37 | #39Static world collision is shipped, while dynamic GameObject collision, fresh-provision parity, and the final real-client movement checks remain open.The epic's main collision slices landed in PR #115. Completion now depends on open issue #103 and its remaining children, issue #104's provisioning Gate, and a human Blink and line-of-sight check, so the umbrella is not a single implementation candidate. Confidence: high. Issue updated 2026-08-11. Blocked by
| 3 | 5 | 5 | 3.0 | Dependency Codex | Finish #103 through its remaining dynamic collision Tickets, complete #104 on a fresh provision, then run the real-client Blink and line-of-sight matrix and close the epic. |
| 38 | #138The repository quickstart is still the only complete guide; the public site exists only as an unbuilt specification, so there is nothing safe to point the 819-line document at.The issue body contains only a dash. The public-site repository says it is not built yet and has no quickstart content. Shrinking the local guide now would remove the usable instructions. Confidence: high. Issue updated 2026-08-13. Blocked by
| 1 | 2 | 1 | 2.0 | Dependency Codex | Wait for the public site to publish and version a complete quickstart, then replace docs/quickstart.md with a short durable pointer and check inbound links. |
| 39 | #33The protocol can expose a Realm list, but the Gateway still presents one configured Realm and the deployment lacks the shared account foundation needed for multiple Realms.Issue #33 explicitly depends on the shared authentication and account work in #34. Starting independent multi-Realm implementation would duplicate or constrain that unfinished design. Confidence: high. Issue updated 2026-08-11. Blocked by
| 2 | 4 | 5 | 1.6 | Dependency Codex | Complete and verify issue #34, then rewrite this issue around Realm directory discovery, selection, routing, and a two-Realm Gate. |
| 40 | #68Zero-disconnect file-descriptor handoff remains a large optional architecture project with all of its prerequisites open.The Gateway keeps DecrypterHalf in the reader and EncrypterHalf in the writer; there is no cipher snapshot, SCM_RIGHTS transport, or receiving process protocol. The proposed handoff must also reconstruct WorldView state and coordinate ownership without letting either process write stale data. This complexity is only justified after measured restart cost and two-Gateway gain show that ordinary drain and reconnect are insufficient. Confidence: high. Issue updated 2026-08-11. Blocked by
| 2 | 2 | 5 | 0.8 | Dependency Codex | Do not implement before #64, #66, and #67. If measurements justify it, first isolate and test vanilla header-cipher snapshot restoration, then specify the Unix handoff state machine and real-client acceptance check. |
| 41 | #61Deterministic bound identity shipped, but World Session epochs still live inside each Gateway process and cannot reject stale teardown across processes.One half of the issue is stale: each Gateway now derives the same synthetic owner identity from the Account. The more serious half remains. SessionEpochs is an AtomicU64 plus a process-local map, and disconnect cleanup trusts that local release result before logout. Two Gateways can therefore each believe their World Session is current and let an older socket remove the newer live Character. The issue should be narrowed to a Realm-core Session generation or lease. Confidence: high. Issue updated 2026-08-11. Blocked by
| 5 | 5 | 4 | 6.2 | Design first Codex | Rewrite the issue around a Realm-core-owned Session generation or lease, pass its token through login and logout, and add a two-Gateway test where the losing socket disconnects after the winner enters the world. |
| 42 | #71Item GUID allocation can leave a Character's 256-value packed block and collide with another Character; transfer relies on the opposite invariant.item_guid_for keeps only 24 owner bits and reserves eight bits for a starting slot. next_item_guid then uses the owner's maximum GUID plus one without checking the low-byte boundary. Enough grants, splits, mail, trade, or inventory churn can enter the next owner's block, while owner GUIDs that differ above bit 24 share a block immediately. A primary-key collision can abort an inventory reducer, and cross-database transfer preserves these GUIDs as globally safe identifiers. Existing rows prevent a casual packing change. Confidence: high. Issue updated 2026-08-11. Blocked by
| 5 | 3 | 5 | 3.0 | Design first Codex | Choose a durable allocation scheme and live-row migration before implementation; define saturation behavior, preserve client-visible identifiers through transfer, and test allocation beyond 256 creations plus owners that share the low 24 bits. |
| 43 | #184The staged vmap import workflow exists, but the issue still asks for map 0 on the Instance Pool, which current canonical rollout rules explicitly forbid.PR 192 shipped the source workflow. PR 275 later introduced the Eastern and Kalimdor World Import Profiles and changed the target matrix. The latest issue comment repeats the retired Instance Pool target, so following it would populate the wrong Shard. Confidence: high. Issue updated 2026-09-01. Blocked by
| 4 | 4 | 2 | 8.0 | Design first Codex | Replace the acceptance checklist with map 0 on the Eastern World Shard, map 1 on the Kalimdor World Shard, and an explicit open-world exclusion for the Instance Pool. Only then schedule operator Verification. |
| 44 | #195Generation-scoped navigation coverage is implemented, but rollout acceptance has not been recorded and the issue's old Shard examples conflict with the current import topology.PR 258 shipped preparation, finalization, matched-generation selection, and route-planner use. The latest comment says only rollout remains, but it predates the canonical profile change that moved open-world coverage to two World Shards and excluded the Instance Pool. Confidence: high. Issue updated 2026-09-01. Blocked by
| 4 | 4 | 2 | 8.0 | Design first Codex | Correct the rollout matrix to the current World Import Profiles, then prepare and finalize matching coverage on each eligible World Shard and record route and client Verification before enabling nav_coverage_enabled. |
| 45 | #69The claimed choice between free-form Gateways and Gateway-per-Shard affinity no longer matches the shared connection model and needs a narrower decision.Current Gateways keep shared coordinator connections to Shards, maintain a local WorldView, and select event audiences by spatial cells. That is already a hybrid: any Gateway can serve a viewer while local indexes avoid broadcasting most Relays to every World Session. Motion still comes from per-mover Shard rows, so the remaining question is measured subscription and writer cost, not the issue's original strict architectural fork. Confidence: medium. Issue updated 2026-08-11. Blocked by
| 3 | 4 | 2 | 6.0 | Design first Codex | Rewrite the decision around the current shared connection and WorldView model, then use #59 and #66 measurements to decide whether process-to-Shard affinity adds enough gain to justify routing and failover constraints. |
| 46 | #113Door collision meshes can be imported, but no per-GameObject collider registry or state-gated ray merge consumes them.The prerequisite importer is merged and the runtime work is absent. The Spec now conflicts with active-generation eligibility: it expects dynamic doors to work on map 36 with no static chunks, while vmap_enabled returns false without an active generation. That decision affects the central Gate and must be settled first. Confidence: high. Issue updated 2026-08-13. Blocked by
| 4 | 5 | 4 | 5.0 | Design first Codex | Choose and document the map-36 eligibility rule. Then implement game_go_collider, lifecycle registration, transforms, state gating, and synthetic ray behavior against that rule. |
| 47 | #34Realm-core authentication is active, but role-selectable Gateway processes, cross-Realm ban kicks, GM baselines, account migration, registration guidance, and a two-Realm Gate remain.The data seam has shipped, but the remaining slices change deployment roles and account policy across Realm processes. The issue still requires Operator sequencing and does not identify which operational slice should land first. Confidence: high. Issue updated 2026-08-11. Blocked by
| 4 | 5 | 5 | 4.0 | Design first Codex | Choose the next operational slice, preferably explicit Gateway role flags, and write separate Tickets for role selection, ban propagation, GM policy, migration, registration, and the two-Realm Gate. |
| 48 | #29Basic GM playtest commands exist, while moderation audit, mute, kick, ban enforcement, summon or appear, and freeze behavior remain absent.The issue now mixes shipped playtest tooling with unimplemented moderation and policy work. The remaining work crosses Gateway sessions, Module state, realm-core account policy, and audit retention, so the umbrella needs a current moderation-only Spec. Confidence: high. Issue updated 2026-08-11. Blocked by
| 4 | 4 | 5 | 3.2 | Design first Codex | Rewrite the issue around moderation outcomes, permission levels, audit records, and ban or mute propagation, then split it into one command and enforcement path per Ticket. |
| 49 | #36Speed and teleport movement checks exist, but fall, gravity, Z-axis, and wall-crossing checks remain undefined and unimplemented.The Module reserves violation codes for the remaining checks, but the issue does not set thresholds or a false-positive budget from observed traces. Those policy choices affect legitimate movement and should be settled before more enforcement is added. Confidence: high. Issue updated 2026-08-11. Blocked by
| 4 | 3 | 4 | 3.0 | Design first Codex | Choose the next check and its false-positive budget from recorded movement traces, then write one Ticket with deterministic Module Gates and a Headless Client scenario. |
| 50 | #35Package authoring, trust, provenance, and the compiled CLI are present; the remaining public-host work is the install script, Server manifest design, and fresh-machine acceptance.PR #397 closed the package API and lint slice, and the cross-repository CLI workflow is established. The unresolved Server manifest is a product and deployment design choice, while issue #58 and fresh-machine verification are separate executable slices. Confidence: high. Issue updated 2026-09-01. Blocked by
| 3 | 5 | 5 | 3.0 | Design first Codex | Decide the minimum Server manifest contract, then delegate issue #58 and a separate fresh-machine Gate in the lyracore-cli repository before returning here for the pin bump. |
| 51 | #82A real Realm still has no tracked TCP load balancer, backend admission cap, or drain procedure for a Gateway pool.The repository contains only the Standalone Supervisor deployment artifact. The issue is explicitly tied to host topology and kill-a-backend acceptance, while the old capacity numbers need refresh after shared connections and batching. Confidence: high. Issue updated 2026-08-11. Blocked by
| 3 | 4 | 4 | 3.0 | Design first Codex | After current capacity and dense-crowd Verification, choose the supported load balancer and tracked deployment shape. Build static backend caps, health checks, drain commands, and a failure drill against a named non-production host first. |
| 52 | #73The pinned CLI has a useful text dev status command and no Ratatui dependency; choosing a TUI remains a product decision.The sibling lyracore-cli repository at the pinned revision has no ratatui or crossterm dependency. dev status already renders process, topology, and per-database health directly from the CLI's existing state and health checks. A TUI could make local observation easier, but the spatial seam map is retired and a remote GM console has different authentication and reach. The remaining work is to select one bounded surface rather than adopt a rendering library first. Confidence: high. Issue updated 2026-08-11. Blocked by
| 2 | 3 | 2 | 3.0 | Design first Codex | Have the Operator choose whether local dev status needs an interactive TUI; if yes, scope a read-only local process and database view before considering remote Realm or spatial editing. |
| 53 | #27Groups remain limited to parties; raid conversion, subgroups, assistants, raid roster packets, and raid quest-credit rules are absent.Current code explicitly excludes raid groups. The issue spans data modeling, protocol behavior, permissions, quest credit, and multi-client acceptance without a current packet or policy Spec. Confidence: high. Issue updated 2026-08-11. Blocked by
| 3 | 4 | 5 | 2.4 | Design first Codex | Define the 1.12 raid roster packet shapes and quest-credit policy, then split conversion, subgroup movement, assistant permissions, roster projection, and credit behavior into separate Tickets. |
| 54 | #313Choose which non-spell DBC catalogues Packages may editThe proposal names a concrete update-only set, but explicitly awaits maintainer approval. Positional keys and cross-family ordering affect the contract and should be settled before implementation. Confidence: medium. Issue updated 2026-09-02. Blocked by
| 3 | 4 | 5 | 2.4 | Design first Codex | Approve or revise the proposed table set, stable keys, family boundaries and replay order, then assign a Tracer. |
| 55 | #11Self-resurrection effects such as Soulstone and Reincarnation have no stored eligibility, consume-on-use flow, or self-resurrect packet handling.Existing resurrection code handles requests from another Character, while the importer leaves Reincarnation scripted. The exact 1.12 duration, death-screen option, reagent, cooldown, and consumption behavior need observation before the state model is fixed. Confidence: medium. Issue updated 2026-08-11. Blocked by
| 3 | 3 | 4 | 2.2 | Design first Codex | Research the missing protocol and gameplay facts from primary sources, then define a complete implementation Ticket. Keep the final real-client check separate. |
| 56 | #198Exact vmap consumption still depends on a realm-wide boolean as well as an active map generation, but the issue's rollout topology no longer matches the canonical World Import Profiles.The implementation is absent and the prerequisites remain open. More seriously, current rollout docs route open-world vmaps to the two World Shards and skip the Instance Pool, contradicting the issue's map-0 account. Removing the Gate from this stale Spec would be unsafe. Confidence: high. Issue updated 2026-09-01. Blocked by
| 3 | 3 | 4 | 2.2 | Design first Codex | Rewrite the supported-map inventory and eligibility rule against the current World Import Profiles, then wait for corrected rollout and matching navigation-coverage Verification before removing the Gate. |
| 57 | #4The imported world has no continent-crossing transport or synthetic AreaTrigger link, and the issue offers two different destinations with different content costs.The Operator must choose between the cheap Ratchet to Stormwind synthetic link and waiting for a real dock path that needs wider map-0 content. Code work before that choice risks implementing the wrong world route. Confidence: high. Issue updated 2026-08-11. Blocked by
| 2 | 3 | 3 | 2.0 | Design first Codex | Choose the temporary synthetic route or the real-dock route; for the temporary route, write one importer plus teleport Gate Ticket using the selected trigger ids. |
| 58 | #67SO_REUSEPORT is still absent, but its value depends on the chosen drain and world-address routing design.Both Gateway listeners still use TcpListener::bind, and there is no reuse-port setup. That proves the feature is unimplemented, but not that it is the best deploy mechanism. If logon sends new clients only to a fresh advertised address and the old Gateway drains, overlapping binds may add little. Platform behavior and failure reporting also need an explicit support policy. Confidence: high. Issue updated 2026-08-11. Blocked by
| 2 | 2 | 3 | 1.3 | Design first Codex | Decide after #64 and #65 whether overlapping binds are required; if yes, specify supported operating systems and add socket creation plus an overlap acceptance test. |
| 59 | #79Gateway connections still use the SpacetimeDB confirmed-read default, and the current shared Coordinator gives no movement-only connection on which to disable it safely.No confirmed-read override exists. The issue's proposed one-line movement-path change no longer fits the architecture: a Coordinator carries all subscribed state and Durable Reads for a Shard, so the durability trade affects more than movement. Confidence: medium. Issue updated 2026-08-11. Blocked by
| 2 | 2 | 3 | 1.3 | Design first Codex | Measure confirmed-read latency on the current Coordinator, list which state would become visible before durability, and decide whether to keep confirmation or introduce a narrowly scoped connection before changing the setting. |
| 60 | #10Distract has no destination checks, temporary Creature attention state, facing update, or combat and expiry rules.The desired idle, combat, radius, duration, and facing semantics are not specified precisely, and the current Creature behavior has no matching investigation or attention state. Observation should precede a new AI state seam. Confidence: medium. Issue updated 2026-08-11. Blocked by
| 2 | 2 | 4 | 1.0 | Design first Codex | Research the missing protocol and gameplay facts from primary sources, then define a complete implementation Ticket. Keep the final real-client check separate. |
| 61 | #41Ritual of Summoning still lacks the ritual portal, two-assistant interaction, and targeted teleport flow.The requested behavior depends on exact 1.12 group and GameObject interaction semantics that are not specified in the issue or represented in current code. A multi-client observation is needed before implementation can be split safely. Confidence: medium. Issue updated 2026-08-11. Blocked by
| 2 | 2 | 5 | 0.8 | Design first Codex | Research the missing protocol and gameplay facts from primary sources, then define a complete implementation Ticket. Keep the final real-client check separate. |
| 62 | #92client sync and the later Client Artifact command are implemented; only a real client sync load check remains.CLI PR 32 and core PR 322 shipped sync. Issue 303 and PR 392 later shipped the distributable Client Artifact that the original issue deferred. The latest issue evidence correctly leaves only stock-client loading. Confidence: high. Issue updated 2026-09-02. Blocked by
| 3 | 4 | 1 | 12.0 | Human acceptance Codex | Run lyracore client sync against a configured stock client and record that patch-3.MPQ and every enabled Package addon load. |
| 63 | #318Confirm Package script removal across a realmPR #358 ships Module reconciliation and four durable tests were recorded green. CLI replay wiring also shipped through #393. The remaining recorded acceptance is visible login effects and removal on a named realm. Confidence: high. Issue updated 2026-09-03. Blocked by
| 3 | 4 | 1 | 12.0 | Human acceptance Codex | Run the existing install, login, disable and login acceptance sequence; preserve cross-Shard evidence. |
| 64 | #3Realm-wide mail, auctions, guilds, whispers, parties, and loot coordination are present, but the reopened epic still lacks a consolidated two-client, multi-Shard acceptance record and contains stale mirror-removal wording.The major systems named by the epic now use realm-core authority, including cross-Shard party and whisper paths. The remaining useful work is a real-client system Gate and an acceptance update that distinguishes authoritative state from deliberate Shard read mirrors. Confidence: medium. Issue updated 2026-08-11. Blocked by
| 4 | 5 | 2 | 10.0 | Human acceptance Codex | Run two real clients on different Shards through mail, auction, guild, whisper, party, loot-roll, Transfer, and delete scenarios; update the mirror criterion and file only concrete failures. |
| 65 | #38The Gateway now installs Shard event callbacks once and performs a single ordered login visibility sweep; the remaining work is the issue's real-client login matrix.PRs #421 and #433 replaced the subscription and login ordering paths described by the issue. Code-level Gates cover callback placement and sweep ordering, but the acceptance criteria still require fresh and geared Characters, auras, and questgivers on a real client. Confidence: high. Issue updated 2026-08-11. Blocked by
| 4 | 4 | 2 | 8.0 | Human acceptance Codex | Run the stated 5875 login matrix on main and close the issue if every initial snapshot and following delta is correct; file narrow failures separately. |
| 66 | #1The public package-manager proposal is largely implemented, while the remaining work is human product review, a real-client sync check, and maintenance of the proposal as a tracker.Most linked slices are closed, and the repository documents package, build, config, replay, client sync, and client pack workflows. The issue comments say not to implement the umbrella directly; open issue #92 now retains only a real-client sync acceptance step. Confidence: high. Issue updated 2026-08-24. Blocked by
| 3 | 5 | 2 | 7.5 | Human acceptance Codex | Complete issue #92's real-client sync check, review the installed workflow against the public proposal, and refresh or close the umbrella without starting code from it. |
| 67 | #42The scripted and package-based Playerbot work has shipped; the remaining acceptance bar is a human-run real-client session that judges believable behavior and completes Deadmines.Core PRs #394 and #395 and the linked package, CLI, and wire-harness work are merged. The issue's latest checklist explicitly leaves human judgment of believability, serendipity, and a full real 1.12.1 client dungeon run. Confidence: high. Issue updated 2026-09-02. Blocked by
| 3 | 5 | 2 | 7.5 | Human acceptance Codex | Run issue #373's imported-node playbook, then complete issue #366 through VanCleef and record the observed failures as narrow follow-up issues. |
| 68 | #154Aura stacking-family code and its single insertion boundary are covered; the documented live stacking sequence has no recorded evidence.PR 217 shipped the code and Architecture Test. The issue's latest comment and the still-empty evidence template agree that only operator-run aura and client Verification remains. Confidence: high. Issue updated 2026-09-01. Blocked by
| 4 | 3 | 2 | 6.0 | Human acceptance Codex | Run docs/aura-stacking-probes.md on an approved development Realm, fill its evidence template, and close this issue if every persisted and visible result agrees. |
| 69 | #112The DOOR and BUTTON model importer is merged; only an approved client-data dry run and apply to a named development Shard remain.PR 254 shipped DBC lookup, M2 extraction, storage reducers, limits, and tests. The latest evidence correctly says runtime use belongs to issue 113 and this issue needs Operator-owned data acceptance only. Confidence: high. Issue updated 2026-09-01. Blocked by
| 3 | 4 | 2 | 6.0 | Human acceptance Codex | Run --go-models as a dry run against approved client data, record nonzero Deadmines door triangles, then apply to a named development Shard. |
| 70 | #196Bounded ground-snapped patrol return is implemented; only a real-client observation of a badly displaced patroller remains.PR 253 added repeated return steps and pure coverage for long displacement and ordinary patrol behavior. The latest issue comment correctly narrows the remainder to visual Verification. Confidence: high. Issue updated 2026-09-01. Blocked by
| 3 | 2 | 1 | 6.0 | Human acceptance Codex | Displace a patroller across uneven terrain in a stock client and record its return, route rejoin, and resumed patrol. |
| 71 | #366Verify Deadmines choreography in the real clientThe Package has durable tests. Visible door changes, Smite movement and chat still need observation. The stomp decision is settled, but packages issue #18 remains open. Confidence: high. Issue updated 2026-09-01. Blocked by
| 3 | 4 | 2 | 6.0 | Human acceptance Codex | Finish the stomp content, then combine dungeon visuals and bot acceptance in one imported-map session. |
| 72 | #37Spell rank supersession and trainer plus relog behavior have shipped; only the real 1.12 client acceptance check remains.PR #256 merged the specified packet behavior, and the issue comment confirms the trainer and relog Gate shipped. No further code slice is identified. Confidence: high. Issue updated 2026-09-01. Blocked by
| 2 | 3 | 1 | 6.0 | Human acceptance Codex | Learn a higher spell rank in a real 1.12.1 client, relog, and confirm the spellbook contains the expected visible rank before closing. |
| 73 | #304Verify FrameXML and GlueXML transforms on the real clientThe transform engine, conflict checks and content hashes already shipped in PR #392. Current issue comments explicitly leave separate FrameXML and GlueXML client checks outstanding. Confidence: high. Issue updated 2026-09-02. Blocked by
| 3 | 3 | 2 | 4.5 | Human acceptance Codex | Run the existing transform Tracer against the Operator baseline in both client phases. |
| 74 | #373Observe imported bots and a fresh Deadmines entryMechanics tests cannot establish believable motion or a fresh real-client instance entry. The issue already contains a combined one-hour acceptance runbook. Confidence: high. Issue updated 2026-09-02. Blocked by
| 3 | 3 | 2 | 4.5 | Human acceptance Codex | Run the combined bot and dungeon acceptance session after the missing dungeon content ships. |
| 75 | #202The low gossip text identifier is implemented, but nobody has confirmed that Marshal McBride's gossip and quest window renders in the stock client.The code already sends identifier 1 and answers its text query. The remaining question is client rendering, which the Headless Client cannot decide. Confidence: high. Issue updated 2026-08-13. Blocked by
| 2 | 2 | 1 | 4.0 | Human acceptance Codex | Right-click Marshal McBride in a stock build-5875 client and record whether the greeting and quest offer appear. |
| 76 | #107GameObject template scale is imported and sent on the wire; current data and stock-client proportions have not been checked.PR 110 shipped all three code layers and fallback tests. The issue's latest comment correctly limits the remainder to import, row and wire checks, and visual proportions. Confidence: high. Issue updated 2026-09-01. Blocked by
| 2 | 3 | 2 | 3.0 | Human acceptance Codex | Publish and import on a named development Shard, compare Peacebloom and Copper Vein template sizes with the source data, inspect OBJECT_FIELD_SCALE_X, and check both in a stock client. |
| 77 | #53A maintained public demo realm still needs deployment, backup, restore, and operations work despite recent pre-auth hardening.Recent work closed two unauthenticated denial-of-service paths, and an open PR adds proof limits and Session expiry. Those changes cover part of the security section, but the issue also requires a named host, TLS and network policy, durable backup and restore, monitoring, restart practice, and a real Internet client drill. This is an Operator project rather than one source change. Confidence: high. Issue updated 2026-08-11. Blocked by
| 4 | 3 | 5 | 2.4 | Human acceptance Codex | Split the remaining work into a reviewed public-host runbook and reversible automation, then have an Operator name the host and approve the first deployment and restore drill. |
| 78 | #70A fresh clone now runs a four-database sharded fixture, while the requested Northshire region seam was deliberately retired.The issue's product goal, showing Sharding out of the box, is shipped in an evolved form. dev up publishes Eastern Kingdoms, Kalimdor, an Instance Pool, and Realm-core, so contributors exercise both continental and instance routing. The same docs explicitly record removal of the second Elwynn database and walkable Northshire seam. Keeping the exact original issue open would reverse a later Operator decision. Confidence: high. Issue updated 2026-08-11.
| 4 | 5 | 1 | 20.0 | Retired or shipped Codex | Close as shipped in revised form: retain the four-database fixture and cite the documented retirement of the Northshire region seam. |
| 79 | #77The reported per-Character AOI query cost and roughly 525-seat result describe the retired connection model, while its follow-up concerns are tracked by narrower capacity issues.The Gateway now uses shared per-Shard Coordinators, an in-memory viewer index, call pipes, and batched movement. Issue 88 records 1,735 seats after batching, contradicting the original ceiling. The remaining blocking-thread cap is documented and bounded under issue 76's work. Confidence: high. Issue updated 2026-08-11.
| 4 | 5 | 1 | 20.0 | Retired or shipped Codex | Close this broad diagnosis as superseded by issues 76, 82, 86, and 88. Keep future capacity work tied to fresh acceptance runs rather than its old numbers. |
| 80 | #51The old away-Shard subscription path is gone, and the replacement shared connection model enforces ghost and stealth visibility.The issue targets ensure_away and fold_home_shard, neither of which exists. The Gateway now keeps shared Shard connections and selects visible peers through WorldView. ViewerGates carries the viewer's ghost state, and peer creation consults ghost and stealth state before sending CREATE. A later merged fix also restores a peer's aura state when stealth ends. Confidence: high. Issue updated 2026-08-11.
| 4 | 4 | 1 | 16.0 | Retired or shipped Codex | Close the issue as superseded by the shared connection model and the current visibility gates; retain the existing WorldView coverage. |
| 81 | #76The blocking-pool limit is now configured, logged, documented, and enforced before a socket enters Tokio's blocking queue, satisfying the issue's stated completion rule.Current code and PR 410 go beyond the original acceptance criteria by sharing a non-waiting capacity across both listeners. The title's old 477 and 535 observations remain historical evidence, not an open implementation request. Confidence: high. Issue updated 2026-08-11.
| 4 | 4 | 1 | 16.0 | Retired or shipped Codex | Close the issue against the current configuration, startup log, architecture documentation, and PR 410 admission bound. Track new capacity failures from fresh measurements in narrower issues. |
| 82 | #58The curl-to-shell local bootstrap is already present as install.sh and is the documented first-run path.The repository root contains a POSIX installer with the exact raw-GitHub curl command. It checks prerequisites, offers user-local tool installs, clones the repository, installs the checkout-resolving CLI launcher, and points the user to lyracore dev up. README and quickstart both lead with it. The implementation evolved from fetching a Gateway binary to a source-first, pinned-CLI checkout, but it satisfies the bootstrap outcome. Confidence: high. Issue updated 2026-08-11.
| 3 | 4 | 1 | 12.0 | Retired or shipped Codex | Close as shipped under the current source-first installer; optionally record one clean Linux and one clean macOS smoke before closure. |
| 83 | #45The old question about per-Character AOI subscription cost no longer matches the event relay design, which now uses one stable event subscription per Shard and computes viewer audiences in Gateway memory.PR #421 removed the fan-out pattern that motivated the table-collapse decision. Its 2,000-Character benchmark reduced queued jobs from 4,000,000 to 336,124 in the distributed case, so the proposed comparison would measure an obsolete architecture. Confidence: high. Issue updated 2026-08-11.
| 2 | 2 | 1 | 4.0 | Retired or shipped Codex | Close the issue as superseded by PR #421 and retain future performance work under a benchmark that exercises the current viewer-audience path. |
| 84 | #48The reported warm-handoff seam feel belongs to the retired region tier; the current Gateway has no seam state machine to tune.The repository removed sub-map regions and mid-walk warm handoff. All recorded angle tests also passed before that removal, so further work on the old hysteresis design would target code that no longer exists. Confidence: high. Issue updated 2026-08-11.
| 1 | 1 | 1 | 1.0 | Retired or shipped Codex | Close the issue with links to the retired region-sharding design and current architecture. |
| 85 | #56The requested walkable-seam presentation polish has no active region seam after the region tier was retired.Abrupt range-leave presentation and repeated crossings were properties of the removed Northshire-to-Elwynn region handoff. Current fixture Shard crossings are escrowed continent or instance transfers, not an overlapping walkable view merge. Keeping this issue open implies an active feature that the current topology deliberately removed. Confidence: high. Issue updated 2026-08-11.
| 2 | 1 | 3 | 0.7 | Retired or shipped Codex | Close with the region tier retirement; restore or rewrite the issue only if a walkable region seam returns. |
| 86 | #49The seam operations console has no active region tier to operate; only the underlying load samples remain useful.The fixture and production topology no longer activate region assignments. Current documentation explicitly retires the walkable region seam and keeps continental and instance routing. Building the requested editor now would put a large UI around inert topology data. Shard load telemetry can support a smaller future operations surface after #73 selects one. Confidence: high. Issue updated 2026-08-11. Blocked by
| 2 | 1 | 5 | 0.4 | Retired or shipped Codex | Close this issue as retired with the region tier; file a smaller load-telemetry issue only after #73 chooses the CLI or remote console surface. |
| 87 | #425Aura tick aborts after a due aura is removedA creature death can remove a due aura before the scheduler advances its old snapshot. The fix advances only rows that still exist, so death and unrelated periodic effects commit together. Confidence: high. Issue updated 2026-09-04.
| 5 | 5 | 2 | 12.5 | Done GPT-6, Codex | Merged after coordinating review and passing CI. No remaining acceptance check for this issue. |
| 88 | #404Package casts can change fixture creaturesThe shared creature identifier policy exists on main through PR #405. The casts entry points do not consistently apply it, so this small fix protects fixtures and Package testing. Confidence: high. Issue updated 2026-09-03.
| 4 | 4 | 1 | 16.0 | Done GPT-5.6 Sol, Package Delta agent | Merged in PR #434. Coordinating review caught partial-update and retarget-away bypasses; durable regressions now prove both are refused. |
The source scanner still recognizes only character_guid, player_guid, and owner_guid. Existing manual cleanup for aura, melee, threat, and combo state shows that unit-keyed tables remain a real transfer blind spot. This is a localized Architecture Test change that prevents future cross-database state loss without changing runtime behavior.
Confidence: high. Issue updated 2026-08-11.
The current pin is still v0.1.0-alpha.3 at the exact reported commit. Its wire-suite.sh contains the broken relative calls, and no newer release exists. This undermines confidence in every live suite claim that uses the pin.
Confidence: high. Issue updated 2026-08-11.
The current Gateway still promotes a staging roll on Realm-core and only then clears the World Shard copy. Both periodic and synchronous promotion paths can run in different Gateway processes. Realm-core's game_loot_roll has only an auto-increment primary key and insert_roll_rows always inserts a new roll and vote set. Module reducers serialize calls, so an idempotent Realm-core check or a compatible uniqueness key can close the race at its authoritative side.
Confidence: high. Issue updated 2026-08-11.
The exact outlier remains in current code. teleport_player drops only game_entity_motion_pending, then deletes game_world_entity in the cross-map branch. Other teardown paths delete the public motion row.
Confidence: high. Issue updated 2026-08-11.
The Defias Cannon can trigger without its required item. Current GOOBER dispatch skips locked_shut, while CHEST and DOOR/BUTTON apply it.
Confidence: high. Issue updated 2026-08-28.
Runtime Script names already landed in CLI PR #55. The remaining Datascript line falsely says nothing reads them. It obscures what an Operator installs.
Confidence: high. Issue updated 2026-09-03.
Subscribed-table parity leaves other generated definitions unchecked. A reproducible generation check would catch drift before unrelated schema work encounters it.
Confidence: high. Issue updated 2026-08-28.
The CLI parser still splits physical lines. Continued directives can hide a conflicting Standalone service. The fix is testable without changing a host.
Confidence: high. Issue updated 2026-08-26.
The exact harness release named in the issue is still pinned. Its benchmark source has raid mode but no death counter, CMSG_REPOP_REQUEST, or revive flow. Reporting the count is a bounded first slice that restores measurement honesty.
Confidence: high. Issue updated 2026-08-11.
Blocked by
The current verifier reads ActiveState, LimitNOFILE and StandardError. It does not compare the effective ExecStart or name relevant drop-ins. A success report can therefore describe the wrong service.
Confidence: high. Issue updated 2026-08-26.
This is the strongest ready feature candidate because it restores core class progression and the issue already names concrete creatures, items, and spells. Most behavior can be covered with Module and Headless Client Gates; only the final presentation check needs a human.
Confidence: high. Issue updated 2026-08-11.
Blocked by
The cheapest defect is still present: peer CREATE replays a resident taxi spline but never the creature's current spline. Motion shedding and sensing cadence are separate policy choices, so they should not hold up that localized fix.
Confidence: high. Issue updated 2026-08-18.
Blocked by
The parent and both blocking code issues are closed. Current Gateway paths cover activate, deposit, withdraw, and slot purchase, while the pinned adapter tree has no bank script.
Confidence: high. Issue updated 2026-08-12.
Blocked by
The code half shipped in PRs 150 and 166. The pinned wire-harness tree contains no drowning or breath adapter, so a bounded cross-repository implementation remains before the human pass.
Confidence: high. Issue updated 2026-08-13.
Blocked by
This is the second-best ready feature candidate. The issue has a current two-Ticket Spec, the missing storage and packet fields are confirmed in code, and the first Tracer can establish one deterministic affix end to end without a design decision.
Confidence: high. Issue updated 2026-08-22.
Blocked by
The issue has a detailed current Spec and carries the ready-for-agent label. It is implementable, but it spans importer data, persistent state, spawn lifecycle, calendar logic, and tooling, so it should be split before code work begins.
Confidence: high. Issue updated 2026-08-21.
The feature is self-contained once the exact 1.12 field encoding, decay rate, and text transform are taken from a primary reference. No competing architecture or open dependency is visible.
Confidence: high. Issue updated 2026-08-11.
The Gateway has since gained pre-auth deadlines, bounded blocking-task admission, file-descriptor checks, and more resilient accept handling, all of which can change failure behavior. None proves that the post-auth mass-disconnect crash is gone. The issue's done condition remains two clean Runbook B runs with process, kernel, and application evidence.
Confidence: high. Issue updated 2026-08-11.
Blocked by
An offline test now proves that 172 healthy motion callbacks can produce the reported warning when the mover has no peer viewer. The current counter counts peer packets. The report does not yet prove a stopped subscription or a root cause for visible freezing.
Confidence: medium. Issue updated 2026-09-04.
Shared Coordinator connections and movement batching change the reported bottlenecks. The issue still requires a comparable run beyond roughly 525 seated Characters and a movement-cost breakdown. Code changes alone cannot satisfy that result.
Confidence: high. Issue updated 2026-08-11.
Blocked by
The Character disappearance Relay exists, but its current Architecture Tests check call names rather than proving deletion and Transfer outcomes. The generic read signature can fail, although the production cache read currently returns Ok. A source scan alone is insufficient closure evidence.
Confidence: medium. Issue updated 2026-08-11.
The current code contradicts the original title: gw_movement_batch, chunking across call pipes, entry isolation, and metrics all exist. PR 234 added a guarded acceptance runner but explicitly left the 500-mover and real-client checks undone.
Confidence: high. Issue updated 2026-08-11.
Blocked by
Current Store code and Fake-based tests cover the topology the issue said was suspect. That is meaningful newer evidence, but it does not reproduce the exact development stack. The issue also combines an unrelated bot-party combat failure that should be split if it remains.
Confidence: medium. Issue updated 2026-08-11.
Blocked by
The current movement model writes one row per mover and uses AOI selection instead of the former per-recipient event rows. PR #421 also reduced distributed event Relay work, but its benchmark explicitly measured selection and encoding rather than realm capacity or latency. The 150/371-client measurements therefore describe neither the current writer load nor the current Gateway work.
Confidence: high. Issue updated 2026-08-11.
Blocked by
The first coalescing rung is present. Later work replaced per-Character subscriptions with one per-Shard stream and an in-memory cell index, invalidating part of the old cost account. Dense fan-out is still inherently large, but a login-priority lane or interest cap needs fresh evidence.
Confidence: medium. Issue updated 2026-08-11.
Blocked by
lyracore-cli PR 25 implemented the verbs and the current pin includes them. That PR explicitly left fresh-provision Verification and retirement of the script for later, and the script remains in the tree.
Confidence: high. Issue updated 2026-08-11.
Blocked by
The issue's static audit found no corruption path and deliberately parked the symptom until logs could separate peer exits, writer failures, and subscription recovery. The Gateway still logs the terminal World Session error, while the current movement and load-shedding paths have changed enough that the old 3 to 8 per 150 result cannot establish today's behavior.
Confidence: high. Issue updated 2026-08-11.
Blocked by
The original measured subscription cost is retired by the shared WorldView. Widening the AOI to 7 by 7 would raise steady audience and relay work, so the old proposed fix should not ship without new evidence of visible churn.
Confidence: high. Issue updated 2026-08-11.
Blocked by
The parent is now a tracker rather than an implementation unit. Its original request for a Spec and split is complete, but the implemented behavior is not. Current eligibility conflicts must be resolved in issue 113 before the parent can advance.
Confidence: high. Issue updated 2026-08-11.
Blocked by
The duplicate bot-invite defect in #62 is fixed, while #61, #63, and #65 remain. The coordinator and Relay cost model also changed: shared Shard connections and cell audiences make the issue's original query-count assumptions stale. A second Gateway measurement can decide whether horizontal Gateway scaling earns its operational cost, but only against a fresh one-Gateway baseline and after known cross-process corruption paths are closed.
Confidence: high. Issue updated 2026-08-11.
Blocked by
Current main binds ordinary Tokio listeners and does not register a Unix signal handler. A stop therefore does not close admission, wait for World Sessions, or perform orderly logout. Session leases reduce how long crash residue survives, but they do not provide a drain. The issue correctly waits for #60 because mass teardown behavior must be known before building shutdown around it.
Confidence: high. Issue updated 2026-08-11.
Blocked by
The logon Store returns a one-element realm list built from the configured world address. Realm-core has per-Gateway Shard load samples, but their gateway_key is a hash for accounting rather than a routable address, and no row says a Gateway accepts new World Sessions or is draining. The old estimate that selection is a tiny change no longer matches the required registration and lease work.
Confidence: high. Issue updated 2026-08-11.
Blocked by
The ray functions and debug reducer still lack instance_id. Issue 113 is unimplemented, and current vmap eligibility requires an active static generation even though the canonical import skips open-world vmaps on the Instance Pool.
Confidence: high. Issue updated 2026-08-13.
Blocked by
The epic's main collision slices landed in PR #115. Completion now depends on open issue #103 and its remaining children, issue #104's provisioning Gate, and a human Blink and line-of-sight check, so the umbrella is not a single implementation candidate.
Confidence: high. Issue updated 2026-08-11.
Blocked by
The issue body contains only a dash. The public-site repository says it is not built yet and has no quickstart content. Shrinking the local guide now would remove the usable instructions.
Confidence: high. Issue updated 2026-08-13.
Blocked by
Issue #33 explicitly depends on the shared authentication and account work in #34. Starting independent multi-Realm implementation would duplicate or constrain that unfinished design.
Confidence: high. Issue updated 2026-08-11.
Blocked by
The Gateway keeps DecrypterHalf in the reader and EncrypterHalf in the writer; there is no cipher snapshot, SCM_RIGHTS transport, or receiving process protocol. The proposed handoff must also reconstruct WorldView state and coordinate ownership without letting either process write stale data. This complexity is only justified after measured restart cost and two-Gateway gain show that ordinary drain and reconnect are insufficient.
Confidence: high. Issue updated 2026-08-11.
Blocked by
One half of the issue is stale: each Gateway now derives the same synthetic owner identity from the Account. The more serious half remains. SessionEpochs is an AtomicU64 plus a process-local map, and disconnect cleanup trusts that local release result before logout. Two Gateways can therefore each believe their World Session is current and let an older socket remove the newer live Character. The issue should be narrowed to a Realm-core Session generation or lease.
Confidence: high. Issue updated 2026-08-11.
Blocked by
PR #439 deduplicates active rolls. Resolution deletes that identity. A durable generation must distinguish retries from a later valid kill before changing storage.
Confidence: high. Issue updated 2026-09-05.
Blocked by
item_guid_for keeps only 24 owner bits and reserves eight bits for a starting slot. next_item_guid then uses the owner's maximum GUID plus one without checking the low-byte boundary. Enough grants, splits, mail, trade, or inventory churn can enter the next owner's block, while owner GUIDs that differ above bit 24 share a block immediately. A primary-key collision can abort an inventory reducer, and cross-database transfer preserves these GUIDs as globally safe identifiers. Existing rows prevent a casual packing change.
Confidence: high. Issue updated 2026-08-11.
Blocked by
install.sh clones the source and installs a pinned CLI launcher. The original issue instead requires both CLI and Gateway binaries in the installation folder. Treating the source-first flow as full completion would hide that difference.
Confidence: high. Issue updated 2026-08-11.
PR 192 shipped the source workflow. PR 275 later introduced the Eastern and Kalimdor World Import Profiles and changed the target matrix. The latest issue comment repeats the retired Instance Pool target, so following it would populate the wrong Shard.
Confidence: high. Issue updated 2026-09-01.
Blocked by
PR 258 shipped preparation, finalization, matched-generation selection, and route-planner use. The latest comment says only rollout remains, but it predates the canonical profile change that moved open-world coverage to two World Shards and excluded the Instance Pool.
Confidence: high. Issue updated 2026-09-01.
Blocked by
Current Gateways keep shared coordinator connections to Shards, maintain a local WorldView, and select event audiences by spatial cells. That is already a hybrid: any Gateway can serve a viewer while local indexes avoid broadcasting most Relays to every World Session. Motion still comes from per-mover Shard rows, so the remaining question is measured subscription and writer cost, not the issue's original strict architectural fork.
Confidence: medium. Issue updated 2026-08-11.
Blocked by
The prerequisite importer is merged and the runtime work is absent. The Spec now conflicts with active-generation eligibility: it expects dynamic doors to work on map 36 with no static chunks, while vmap_enabled returns false without an active generation. That decision affects the central Gate and must be settled first.
Confidence: high. Issue updated 2026-08-13.
Blocked by
The data seam has shipped, but the remaining slices change deployment roles and account policy across Realm processes. The issue still requires Operator sequencing and does not identify which operational slice should land first.
Confidence: high. Issue updated 2026-08-11.
Blocked by
The issue now mixes shipped playtest tooling with unimplemented moderation and policy work. The remaining work crosses Gateway sessions, Module state, realm-core account policy, and audit retention, so the umbrella needs a current moderation-only Spec.
Confidence: high. Issue updated 2026-08-11.
Blocked by
The Module reserves violation codes for the remaining checks, but the issue does not set thresholds or a false-positive budget from observed traces. Those policy choices affect legitimate movement and should be settled before more enforcement is added.
Confidence: high. Issue updated 2026-08-11.
Blocked by
PR #397 closed the package API and lint slice, and the cross-repository CLI workflow is established. The unresolved Server manifest is a product and deployment design choice, while issue #58 and fresh-machine verification are separate executable slices.
Confidence: high. Issue updated 2026-09-01.
Blocked by
The row contains is_completion, is_interrupted, delay_ms, and is_proc_log alongside ordinary START and GO fields. The Gateway decodes them in ordered branches, while comments state which fields must be the only active signal. Typed signal constructors reduced literal duplication but do not enforce mutual exclusion. An additive kind would make the union explicit, but schema publication and generated bindings make this more than a local refactor, and the unused is_completion field needs a compatibility choice.
Confidence: high. Issue updated 2026-08-11.
Blocked by
The repository contains only the Standalone Supervisor deployment artifact. The issue is explicitly tied to host topology and kill-a-backend acceptance, while the old capacity numbers need refresh after shared connections and batching.
Confidence: high. Issue updated 2026-08-11.
Blocked by
The sibling lyracore-cli repository at the pinned revision has no ratatui or crossterm dependency. dev status already renders process, topology, and per-database health directly from the CLI's existing state and health checks. A TUI could make local observation easier, but the spatial seam map is retired and a remote GM console has different authentication and reach. The remaining work is to select one bounded surface rather than adopt a rendering library first.
Confidence: high. Issue updated 2026-08-11.
Blocked by
Current code explicitly excludes raid groups. The issue spans data modeling, protocol behavior, permissions, quest credit, and multi-client acceptance without a current packet or policy Spec.
Confidence: high. Issue updated 2026-08-11.
Blocked by
The proposal names a concrete update-only set, but explicitly awaits maintainer approval. Positional keys and cross-family ordering affect the contract and should be settled before implementation.
Confidence: medium. Issue updated 2026-09-02.
Blocked by
Existing resurrection code handles requests from another Character, while the importer leaves Reincarnation scripted. The exact 1.12 duration, death-screen option, reagent, cooldown, and consumption behavior need observation before the state model is fixed.
Confidence: medium. Issue updated 2026-08-11.
Blocked by
The implementation is absent and the prerequisites remain open. More seriously, current rollout docs route open-world vmaps to the two World Shards and skip the Instance Pool, contradicting the issue's map-0 account. Removing the Gate from this stale Spec would be unsafe.
Confidence: high. Issue updated 2026-09-01.
Blocked by
The Operator must choose between the cheap Ratchet to Stormwind synthetic link and waiting for a real dock path that needs wider map-0 content. Code work before that choice risks implementing the wrong world route.
Confidence: high. Issue updated 2026-08-11.
Blocked by
Both Gateway listeners still use TcpListener::bind, and there is no reuse-port setup. That proves the feature is unimplemented, but not that it is the best deploy mechanism. If logon sends new clients only to a fresh advertised address and the old Gateway drains, overlapping binds may add little. Platform behavior and failure reporting also need an explicit support policy.
Confidence: high. Issue updated 2026-08-11.
Blocked by
No confirmed-read override exists. The issue's proposed one-line movement-path change no longer fits the architecture: a Coordinator carries all subscribed state and Durable Reads for a Shard, so the durability trade affects more than movement.
Confidence: medium. Issue updated 2026-08-11.
Blocked by
The desired idle, combat, radius, duration, and facing semantics are not specified precisely, and the current Creature behavior has no matching investigation or attention state. Observation should precede a new AI state seam.
Confidence: medium. Issue updated 2026-08-11.
Blocked by
The requested behavior depends on exact 1.12 group and GameObject interaction semantics that are not specified in the issue or represented in current code. A multi-client observation is needed before implementation can be split safely.
Confidence: medium. Issue updated 2026-08-11.
Blocked by
CLI PR 32 and core PR 322 shipped sync. Issue 303 and PR 392 later shipped the distributable Client Artifact that the original issue deferred. The latest issue evidence correctly leaves only stock-client loading.
Confidence: high. Issue updated 2026-09-02.
Blocked by
PR #358 ships Module reconciliation and four durable tests were recorded green. CLI replay wiring also shipped through #393. The remaining recorded acceptance is visible login effects and removal on a named realm.
Confidence: high. Issue updated 2026-09-03.
Blocked by
The major systems named by the epic now use realm-core authority, including cross-Shard party and whisper paths. The remaining useful work is a real-client system Gate and an acceptance update that distinguishes authoritative state from deliberate Shard read mirrors.
Confidence: medium. Issue updated 2026-08-11.
Blocked by
PRs #421 and #433 replaced the subscription and login ordering paths described by the issue. Code-level Gates cover callback placement and sweep ordering, but the acceptance criteria still require fresh and geared Characters, auras, and questgivers on a real client.
Confidence: high. Issue updated 2026-08-11.
Blocked by
Most linked slices are closed, and the repository documents package, build, config, replay, client sync, and client pack workflows. The issue comments say not to implement the umbrella directly; open issue #92 now retains only a real-client sync acceptance step.
Confidence: high. Issue updated 2026-08-24.
Blocked by
Core PRs #394 and #395 and the linked package, CLI, and wire-harness work are merged. The issue's latest checklist explicitly leaves human judgment of believability, serendipity, and a full real 1.12.1 client dungeon run.
Confidence: high. Issue updated 2026-09-02.
Blocked by
PR 217 shipped the code and Architecture Test. The issue's latest comment and the still-empty evidence template agree that only operator-run aura and client Verification remains.
Confidence: high. Issue updated 2026-09-01.
Blocked by
PR 254 shipped DBC lookup, M2 extraction, storage reducers, limits, and tests. The latest evidence correctly says runtime use belongs to issue 113 and this issue needs Operator-owned data acceptance only.
Confidence: high. Issue updated 2026-09-01.
Blocked by
PR 253 added repeated return steps and pure coverage for long displacement and ordinary patrol behavior. The latest issue comment correctly narrows the remainder to visual Verification.
Confidence: high. Issue updated 2026-09-01.
Blocked by
The Package has durable tests. Visible door changes, Smite movement and chat still need observation. The stomp decision is settled, but packages issue #18 remains open.
Confidence: high. Issue updated 2026-09-01.
Blocked by
PR #256 merged the specified packet behavior, and the issue comment confirms the trainer and relog Gate shipped. No further code slice is identified.
Confidence: high. Issue updated 2026-09-01.
Blocked by
The transform engine, conflict checks and content hashes already shipped in PR #392. Current issue comments explicitly leave separate FrameXML and GlueXML client checks outstanding.
Confidence: high. Issue updated 2026-09-02.
Blocked by
Mechanics tests cannot establish believable motion or a fresh real-client instance entry. The issue already contains a combined one-hour acceptance runbook.
Confidence: high. Issue updated 2026-09-02.
Blocked by
The code already sends identifier 1 and answers its text query. The remaining question is client rendering, which the Headless Client cannot decide.
Confidence: high. Issue updated 2026-08-13.
Blocked by
PR 110 shipped all three code layers and fallback tests. The issue's latest comment correctly limits the remainder to import, row and wire checks, and visual proportions.
Confidence: high. Issue updated 2026-09-01.
Blocked by
Pre-auth limits and Session Expiry shipped in merged PR #416. A public demo Realm still needs a named host, backup and restore procedures, operational ownership and an approved deployment.
Confidence: high. Issue updated 2026-08-11.
Blocked by
A creature death can remove a due aura before the scheduler advances its old snapshot. The fix advances only rows that still exist, so death and unrelated periodic effects commit together.
Confidence: high. Issue updated 2026-09-04.
The issue's product goal, showing Sharding out of the box, is shipped in an evolved form. dev up publishes Eastern Kingdoms, Kalimdor, an Instance Pool, and Realm-core, so contributors exercise both continental and instance routing. The same docs explicitly record removal of the second Elwynn database and walkable Northshire seam. Keeping the exact original issue open would reverse a later Operator decision.
Confidence: high. Issue updated 2026-08-11.
The issue targets ensure_away and fold_home_shard, neither of which exists. The Gateway now keeps shared Shard connections and selects visible peers through WorldView. ViewerGates carries the viewer's ghost state, and peer creation consults ghost and stealth state before sending CREATE. A later merged fix also restores a peer's aura state when stealth ends.
Confidence: high. Issue updated 2026-08-11.
Current code and PR 410 go beyond the original acceptance criteria by sharing a non-waiting capacity across both listeners. The title's old 477 and 535 observations remain historical evidence, not an open implementation request.
Confidence: high. Issue updated 2026-08-11.
The shared creature identifier policy exists on main through PR #405. The casts entry points do not consistently apply it, so this small fix protects fixtures and Package testing.
Confidence: high. Issue updated 2026-09-03.
Current CLI main reads target provenance before resolving client data. The script-only no-op test already runs without client data. The original control-flow complaint appears fixed by the replay work.
Confidence: high. Issue updated 2026-09-02.
PRs #419 and #426 are merged. Reassess the original checklist against current workflows rather than starting another workflow.
Confidence: high. Issue updated 2026-08-28.
PR #419 is merged. The blocking clippy, formatting and Rust jobs passed on main b4c17c4; the GitHub closure cites that run.
Confidence: high. Issue updated 2026-08-28.
PR #421 removed the fan-out pattern that motivated the table-collapse decision. Its 2,000-Character benchmark reduced queued jobs from 4,000,000 to 336,124 in the distributed case, so the proposed comparison would measure an obsolete architecture.
Confidence: high. Issue updated 2026-08-11.
The repository removed sub-map regions and mid-walk warm handoff. All recorded angle tests also passed before that removal, so further work on the old hysteresis design would target code that no longer exists.
Confidence: high. Issue updated 2026-08-11.
Abrupt range-leave presentation and repeated crossings were properties of the removed Northshire-to-Elwynn region handoff. Current fixture Shard crossings are escrowed continent or instance transfers, not an overlapping walkable view merge. Keeping this issue open implies an active feature that the current topology deliberately removed.
Confidence: high. Issue updated 2026-08-11.
The fixture and production topology no longer activate region assignments. Current documentation explicitly retires the walkable region seam and keeps continental and instance routing. Building the requested editor now would put a large UI around inert topology data. Shard load telemetry can support a smaller future operations surface after #73 selects one.
Confidence: high. Issue updated 2026-08-11.
Blocked by
Each implementer owns their PR until it merges or has a named blocker. Codex checks CI, CodeRabbit reviews, human comments and unresolved threads after each push. Accepted findings get a fix and fresh checks; disputed findings get a reasoned response. Rebase before opening a PR and recheck the reviewed commit before merge.
-| PR | Change | Owner | State | Next action |
|---|---|---|---|---|
| #426 | ci(module): run the durable test suite and drop its fixed sleeps | Existing PR review owner; Codex monitors | Durable CI failed on current head | Existing owner fixes the durable CI failure and refreshes review. |
| #419 | ci: make fmt and clippy blocking, and clear the workspace to match | Existing PR review owner; Codex monitors | Test failed on current head | Existing owner fixes the failing test and rebases after the other changes. |
| #416 | fix(logon): cap proof attempts per peer and expire session keys | Existing PR review owner; Codex monitors | Current CI passed; security and human review remain | Existing owner handles security review. The new schema requires human review before shipping. |
| #415 | refactor(auction): let the Module own the auctioneer interaction Gate | Existing PR review owner; Codex monitors | Merged | Complete; preserve the reviewed result. |
| #434 | Protect fixture creatures from cast Claims | GPT-5.6 Sol, Package Delta agent | Merged; all CI checks passed | Complete. Coordinating review passed with no unresolved findings. |
| #435 | Keep periodic deaths from rolling back the aura tick | GPT-6, Codex | Merged; all CI checks passed | Complete. Coordinating review passed with no unresolved findings. |
| #436 | Maintain the issue order and delivery report | GPT-6, Codex | Addressing CodeRabbit publisher finding | Pin the local publisher and lock its dependencies, update the report, then finish review and CI. |
| #437 | Measure motion delivery at each Shard callback | GPT-6 Astra, motion diagnosis agent | Merged; CI and review passed | Diagnostic fix complete. Issue #424 remains open until the reported freeze is reproduced and resolved. |
| #438 | Remove public motion after cross-map teleport | GPT-5.6 Sol, teleport agent | CI and coordinating review passed; CodeRabbit rate-limited | Request CodeRabbit review after 07:18 UTC and resolve any findings before merge. |
Codex takes the final merge after current-head checks pass and review findings are resolved. Explicit human review requirements and real-client acceptance remain separate.
+| PR | Change | Owner | State | Next action |
|---|---|---|---|---|
| #426 | ci(module): run the durable test suite and drop its fixed sleeps | Existing PR review owner; Codex monitors | Merged | Complete. Reassess linked issues for any remaining acceptance. |
| #419 | ci: make fmt and clippy blocking, and clear the workspace to match | Existing PR review owner; Codex monitors | Merged | Complete. Reassess linked issues for any remaining acceptance. |
| #416 | fix(logon): cap proof attempts per peer and expire session keys | Existing PR review owner; Codex monitors | Merged | Complete. Reassess linked issues for any remaining acceptance. |
| #415 | refactor(auction): let the Module own the auctioneer interaction Gate | Existing PR review owner; Codex monitors | Merged | Complete. Reassess linked issues for any remaining acceptance. |
| #434 | Protect fixture creatures from cast Claims | GPT-5.6 Sol, Package Delta agent | Merged | Complete. Reassess linked issues for any remaining acceptance. |
| #435 | Keep periodic deaths from rolling back the aura tick | GPT-6, Codex | Merged | Complete. Reassess linked issues for any remaining acceptance. |
| #436 | Maintain the issue order and delivery report | GPT-6, Codex | Merged | Complete. Reassess linked issues for any remaining acceptance. |
| #437 | Measure motion delivery at each Shard callback | GPT-6 Astra, motion diagnosis agent | Merged | Complete. Reassess linked issues for any remaining acceptance. |
| #438 | fix(world): remove motion after cross-map teleport | GPT-5.6 Sol, PR completion agent | Open; fresh review audit assigned | Read all reviews and threads, address valid findings, and verify current-head CI. Merge policy pending. |
| #440 | fix(gameobject): require opener for locked goobers | GPT-5.6 Sol, PR completion agent | Open; fresh review audit assigned | Read all reviews and threads, address valid findings, and verify current-head CI. Merge policy pending. |
| #439 | fix(loot): keep concurrent promotions on one live roll | GPT-5.6 Sol, PR completion agent | Open; fresh review audit assigned | Read all reviews and threads, address valid findings, and verify current-head CI. Merge policy pending. |
| #56 | fix(packages): count Package Deltas in trust review | GPT-5.6 Sol, CLI completion agent | Open in lyracore-cli; review audit assigned | Resolve review findings, verify CLI tests and MSRV, then publish the core pin update. |
| #444 | docs(triage): refresh issue order and resume PR ownership | GPT-6 Astra, Codex | Addressed three CodeRabbit findings; durable CI rerun underway | Refresh stale evidence and recorded heads, finish the failed-job retry, and verify the revised commit. |
| #6 | fix(suite): run scenarios from the adapter directory | GPT-6 Astra, Codex | PR open; CI running | Complete independent review and CI, then publish a release tag and core pin. |
This report is the working dispatch list. Codex updates the same published URL after triage, assignment, PR creation, review changes and merge. Scores change when new evidence changes the expected benefit or effort. @@ -56,7 +58,7 @@
Production changes require a named host and explicit authorization. Work that crosses section 1 of danger-zones.md needs human review before shipping. Product UI changes follow the repository's mock-selection requirement.