docs(rendering): close retained-scene G5

Record the exact visual, route, lifecycle, production CPU/GPU/memory, and allocation evidence for retiring the normal InteriorEntityPartition. Reconcile the roadmap, milestones, shared session instructions, and Slice I handoff so the measured transition/query scratch remainder has one owner.

Co-authored-by: OpenAI Codex <codex@openai.com>

docs/plans/2026-07-24-modern-runtime-architecture.md

@@ -2,9 +2,8 @@
 
 **Date:** 2026-07-24
 
-**Status:** Slices A–F and H are complete; G0–G4 and I0 are complete. Slices
-F–L were explicitly approved 2026-07-24; G5 production-matrix closeout is
-active.
+**Status:** Slices A–H and I0 are complete. Slices F–L were explicitly
+approved 2026-07-24; Slice I1 is active.
 
 **Scope:** Reconcile and sequence the existing Modern Pipeline (`MP`) and
 Linux/headless (`LH`) tracks using the 2026-07-24 connected performance audit.
@@ -1184,21 +1183,23 @@ an improvement" carries the same evidence burden as a regression claim.
 
 ## 14. Current execution point
 
-Slices A–E are complete. Slice E's exact physical-local Release binary
-produced uncapped CPU p50/p95/p99 1.216/4.216/5.450 ms and GPU
-0.725/2.486/2.666 ms across the nine-stop route. Dense Arwic, with 15,530
-entities and 111 animated entities, produced CPU 2.652/4.153/5.736 ms and GPU
-1.576/2.504/2.662 ms. Every stable checkpoint converged without pending
-publication, retirement, upload, warmup, or resource backlog.
+Slices A–H are complete. The retained render scene is now the sole production
+entity source: G5 removed the old whole-world `InteriorEntityPartition` from
+normal mesh and attached-particle routing while preserving it only for
+standalone tests and explicit diagnostic/oracle probes. The user accepted the
+retained-path visual matrix. Capped/uncapped/dense routes and the exact
+seven-checkpoint lifecycle/reconnect gate pass with graceful shutdown.
 
-The dense median already satisfies the provisional 3.33 ms / 300 FPS target.
-CPU tail cost remains above GPU cost and the normal draw path still scans and
-partitions resident entities, so F/G can improve CPU utilization, scaling, and
-tail behavior, but a dramatic average-FPS gain is not promised. The
-implementation-ready F/G contract and ownership map are
-[`2026-07-24-modern-runtime-slices-f-g-render-scene.md`](2026-07-24-modern-runtime-slices-f-g-render-scene.md).
-The §0.1 and §0.3 gates were explicitly lifted 2026-07-24. Slice F is the
-current execution point; `e7d9d6fa` is the pre-runtime rollback anchor.
+The final ordinary-production minute on exact `14fbe92b` sustained 519.7 FPS:
+CPU p50/p95/p99 1.869/2.306/2.484 ms and GPU
+1.096/1.108/1.136 ms. Working/private memory was 652.1/928.3 MiB.
+Frame-thread allocation is now 22.34 KiB median; allocation-tick evidence and
+the four-mover baseline assign that remainder primarily to reset-complete
+`Transition` collision/query scratch. I0 has pinned the retail oracle and
+fixtures, so I1 is the current execution point. Evidence:
+[`../research/2026-07-25-slice-g5-production-profile.md`](../research/2026-07-25-slice-g5-production-profile.md)
+and
+[`2026-07-25-modern-runtime-slice-i.md`](2026-07-25-modern-runtime-slice-i.md).
 
 The intended order is therefore:
 
@@ -1208,10 +1209,10 @@ honest metrics + committed baselines        (A — exit criteria block C)
   -> typed residence                        (D — unify/retune, not rebuild)
   -> cost-budgeted streaming                (E)
   -> [APPROVED 2026-07-24: ECS deferral lifted under §0.1]
-  -> incremental render scene               (F — CURRENT; referee first)
+  -> incremental render scene               (F)
   -> delta GPU submission                   (G)
   -> residual frame cleanup                 (H-a, H-b, H-c)
-  -> flat collision assets                  (I — floats; depends only on B)
+  -> flat collision assets                  (I — CURRENT at I1)
   -> presentation-independent runtime       (J — §0.3 authorization)
   -> Linux/headless/multi-session           (K)
   -> evidence-gated GPU jobs                (L)