Status snapshot /
The status data could not be loaded. Do not infer project completion from this page.
Verification, separated
What passes. What doesn’t.
Next execution boundary
Harden the prototype
No committed completion date. Remaining work is ordered by dependencies, not invented calendar deadlines.
Full scope, no skipped phases
Roadmap at a glance
Delivery history
What happened, and when
Chronological milestone dates in UTC. Completion applies only to the named scope; failed attempts remain visible.
All work items
Delivered work. Remaining gates.
Historical milestones are date-sorted. Undated phase and M2 work follows the plan’s dependency order. A blank schedule is shown as TBD.
No work items match. Choose All and clear the search to restore the complete ledger.
Provenance and limits
Evidence before completion
Generated . Evidence baseline — the newest commit touching the sources this describes, at the time it was generated. A dated snapshot, not a live monitor. Private source records and owner-held ROM data are not published.
Lane reports
Every lane report in the repository, with both freshness signals. A lane is current only when it passed and no commit touching the runtime paths has landed since it was regenerated. Code drift is an over-approximation: a stale lane may still be valid, but a current lane is not stale.
Build identity pins
The hashes the build currently declares. A lane asserting anything else describes an artifact no commit now produces.
Owner-supplied inputs
Required by name only. Commercial ROM data is never committed, published, or embedded, and no filesystem path is recorded here.
Still unverified: Real-hardware controller-two behavior, worst-room timing, instruction-boundary NMI/mapper recovery, full co-op playthrough, movement soak and human release acceptance.