docs(performance): close modern runtime slice H

docs/plans/2026-07-25-modern-runtime-slice-h.md

@@ -1,6 +1,6 @@
 # Modern runtime Slice H execution plan
 
-**Status:** ACTIVE  
+**Status:** COMPLETE (2026-07-25)
 **Parent plan:** `2026-07-24-modern-runtime-architecture.md`, Slice H  
 **Prerequisite state:** Slice G4 production cutover is automated-gated; its
 user visual gate remains pending.
@@ -204,3 +204,27 @@ fixtures are committed under `docs/research/` or the matching test project.
   measured after H-a and scheduled only if still material.
 - Slices I–L start only after Slice H is measured and documented, but no
   additional authorization is required.
+
+## 7. Closeout
+
+All H-a, H-b, and H-c implementation units are complete. The Release build
+and complete solution pass 8,292 tests with 5 skips. The connected
+login/portal/dungeon/revisit/graceful-disconnect/fresh-process-reconnect gate
+passed on commit `41c1a593927fcf71ef83b4825c659a4970e9b858` with all seven
+checkpoints ready, no invariant or transport failure, and both sessions
+closing through the normal logout path.
+
+The connected automation deliberately constructs the retained G4 current-path
+oracle, so its scene-sized per-frame allocation is comparison-instrumentation
+cost and not representative of production. A separate normal uncapped Release
+session, with neither lifecycle automation nor the oracle composed, stabilized
+at 25.6 KiB/frame and roughly 500 presented frames/second under RDP. Allocation
+stack attribution identifies the remaining dominant production owners as
+`Transition` query scratch (Slice I) and the retained current partition/referee
+path (G5). The H-owned packet decode and recurring outbound framing paths
+independently allocate zero bytes when warm. The program-wide 4 KiB/frame
+target therefore remains an end-of-G5/Slice-I acceptance condition rather than
+being misreported as achieved by H alone.
+
+Closeout evidence:
+[`../research/2026-07-25-slice-h-closeout.md`](../research/2026-07-25-slice-h-closeout.md).