docs(runtime): record J0 and physical I6 evidence

Pin the exact J0 rollback, synchronize the roadmap and agent handoff files, and distinguish the observer-heavy two-gigabyte soak from the ordinary-client physical sample. Keep parsed collision graph removal explicitly behind the pending user collision and visual gate.

Co-authored-by: Codex <codex@openai.com>
This commit is contained in:
Erik 2026-07-25 17:35:44 +02:00
parent b632672e5c
commit 574a6c454f
7 changed files with 104 additions and 16 deletions

View file

@ -141,8 +141,16 @@ queries with zero mismatch, fault, or artifact; graph/flat cell residency
matched at every stable checkpoint and teardown converged. Release build and
8,396 solution tests / 5 skips pass. Slice H is complete: retained UI/frame
work, exact bounded light selection, and pooled/borrowed/direct network I/O
pass. Slice I is active at I6 under
pass. Slice I6 is committed: gameplay is flat-authoritative, its dense-Arwic
referee gate matched 46,309/46,309 queries, and the physical nine-stop soak
converged without publication, retirement, upload, or warmup backlog. Parsed
graph deletion remains gated on the user's collision/visual acceptance. Slice
J0 established and enforced the presentation-independent `AcDream.Runtime`
boundary without moving behavior; Release build and 8,406 tests / 5 skips
pass. Slice I7 closeout is active under
[`2026-07-25-modern-runtime-slice-i.md`](2026-07-25-modern-runtime-slice-i.md).
The coherent Slice J campaign is pinned in
[`2026-07-25-modern-runtime-slice-j.md`](2026-07-25-modern-runtime-slice-j.md).
The historical exact G4 visual rollback remains
`git revert ef1d263337997bb030eadb7b8e71d73dc659907a`.