docs(runtime): approve render scene program

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

@@ -2,7 +2,8 @@
 
 **Date:** 2026-07-24
 
-**Status:** Slices A–E complete. Slices F/G await their explicit approval gate.
+**Status:** Slices A–E complete. Slices F–L explicitly approved 2026-07-24;
+Slice F is active.
 
 **Scope:** Reconcile and sequence the existing Modern Pipeline (`MP`) and
 Linux/headless (`LH`) tracks using the 2026-07-24 connected performance audit.
@@ -34,7 +35,10 @@ section 13.
    do not touch that deferral. **Slices F and G resume the deferred MP3
    work and MUST NOT start without explicit user approval recorded against
    this section**, taken on the post-Slice-E corrected uncapped-local
-   profile (does partition/submission cost still dominate?). Note the prior
+   profile (does partition/submission cost still dominate?).
+   **Approval recorded 2026-07-24:** after reviewing the post-E result and
+   rewrite risk, the user authorized "all slices." F/G may proceed from the
+   pre-runtime rollback anchor `e7d9d6fa`. Note the prior
    "GPU-bound at ~200 FPS" Sawato reading is itself invalidated by the
    `GpuFrameTimer` boundary artifact this plan's Slice A corrects — the
    question is genuinely open until re-measured.
@@ -45,9 +49,10 @@ section 13.
    covers streaming and WB rendering only. Slice H's network-I/O item and
    Slice J's gameplay-owner moves touch otherwise-frozen subsystems
    (network, chat, input) and each requires its own recorded user
-   authorization before starting. (The 2026-07-24 receive-thread robustness
-   fix was separately reviewed and user-approved as a bug fix, not a
-   rework.)
+   authorization before starting. **Approval recorded 2026-07-24:** the
+   user's authorization for "all slices" lifts the Slice J gate as well.
+   (The 2026-07-24 receive-thread robustness fix was separately reviewed and
+   user-approved as a bug fix, not a rework.)
 4. **Evidence-base corrections.** The §1 exception-traffic row previously
    cited "4,520 + 1,168" — figures with no derivation in the audit or its
    committed artifacts; the verifiable figures are the focused-trace 1,587
@@ -799,6 +804,8 @@ Slices G and H.
 
 ### Slice F — Incremental render scene foundation
 
+**Prepared plan:** [`2026-07-24-modern-runtime-slices-f-g-render-scene.md`](2026-07-24-modern-runtime-slices-f-g-render-scene.md).
+
 **Purpose:** Stop rebuilding/partitioning the world each frame.
 
 - Add acdream-owned `IRenderScene`, identifiers, components, and delta journal.
@@ -1170,14 +1177,21 @@ an improvement" carries the same evidence burden as a regression claim.
 
 ## 14. Current execution point
 
-Slices A–C are complete. Slice C replaced production live-DAT world-mesh
-extraction with the validated prepared source and passed all connected,
-performance, lifetime, automated, and user-visual gates. Its physical
-uncapped result is CPU p50/p95/p99 1.409/4.909/6.496 ms, GPU
-0.832/2.510/2.706 ms, a 39.9 MiB largest frame allocation, zero invalid Setup
-probe exceptions, and a passing warm repeated-Caul memory assertion. Slice D
-is the next execution point; it unifies accounting and policy around the
-specialized caches that remain, rather than replacing their working storage.
+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.
+
+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 intended order is therefore:
 
@@ -1186,8 +1200,8 @@ honest metrics + committed baselines        (A — exit criteria block C)
   -> prepared content                       (B, C)
   -> typed residence                        (D — unify/retune, not rebuild)
   -> cost-budgeted streaming                (E)
-  -> [user decision gate: lift the ECS deferral? §0.1]
-  -> incremental render scene               (F — referee sub-slice first)
+  -> [APPROVED 2026-07-24: ECS deferral lifted under §0.1]
+  -> incremental render scene               (F — CURRENT; referee first)
   -> delta GPU submission                   (G)
   -> residual frame cleanup                 (H-a, H-b, H-c)
   -> flat collision assets                  (I — floats; depends only on B)