fix(rendering): publish scene deltas at update boundary

Move the ordinary shadow-scene drain out of the conditional spatial reconciler and into an explicit final update-frame commit phase. This publishes deltas after streaming, network, teleport, camera, and conditional reconciles even while world simulation is quiesced.

Release gate: 3,733 App tests / 3 skips; 8,217 complete-solution tests / 5 skips.

Co-Authored-By: OpenAI Codex <codex@openai.com>

docs/plans/2026-07-24-modern-runtime-slices-f-g-render-scene.md

@@ -429,6 +429,20 @@ updates, and active animated-static synchronization. The capped, uncapped, and
 dense-town routes are all rerun from the corrective commit; no F5 success is
 claimed from the rejected `056bbd4e` route.
 
+The next exact capped route on `91463db5` completed all nine stops and shut
+down gracefully, but F5 again rejected it. A transition frame reached the
+post-render referee with 5,111 pending deltas because the only ordinary drain
+was embedded in the spatial reconciler, which is intentionally skipped while
+the world is quiesced. Later revisit frames also diverged, but the bounded
+first-mismatch recorder correctly retained the earlier journal-ordering fault.
+The correction makes scene publication an explicit final update-frame commit
+phase after streaming, network, teleport, camera, and every conditional
+spatial reconcile. It runs even while world simulation is quiesced. The former
+reconciler drain is removed, leaving one ordinary update/render-boundary
+publication; session reset retains its separate ordered teardown drain. The
+next capped redrive must prove both zero pending deltas and expose or clear any
+remaining projection mismatch before uncapped evidence begins.
+
 ## 6. Slice G — Frame product and production cutover
 
 ### G0 — Borrowed double-buffered frame product