docs(wiki): 2026-11-15 evening status refresh - held-window release carrier deterministic (c772), slot-34/SA[34] settled (0x265), call order is the blocker; eng64 chains the release behind the pack carrier; STATE-CURRENT snapshot

1 files changed, 14 insertions, 8 deletions

diff --git a/wiki/Execution-Plane.md b/wiki/Execution-Plane.md
index 567f41c..4a84457 100644
--- a/wiki/Execution-Plane.md
+++ b/wiki/Execution-Plane.md
@@ -8,7 +8,7 @@
 > when the two disagree, the docs tree wins. Front door:
 > [`../docs/README.md`](../docs/README.md).
 
-Status: 2026-11-15, tree `master @ 692a7eb0`. Tags: `[live]` proven with the
+Status: 2026-11-15, tree `master @ 6aeb20c7`. Tags: `[live]` proven with the
 stock guest driver; `[gated]` implemented, default-off or parameter-gated;
 `[wip]` partial; `[wall]` current blocker; `[target]` named success latch;
 `[planned]` designed, not built.
@@ -169,13 +169,19 @@ guest: push + QMD + GPFIFO entry + doorbell (BAR0 0x88704)
   stage-0/1 image is now authored and live: a VTG SPH at `family+0x900`
   (first word `020a0481`) is fetched by both vertex slots
   (`DS-IMAGE st0=st1=020a0481`; DS fell `0x86040626 -> 0x84000420`,
-  reproduced on two boots). No non-black **window/screen** frame has been
-  produced through the NVIDIA path yet: the remaining DS bits are stage
-  type/context (SPH5/SPH10/SPH18), the 728-B draw window's released macros
-  (`0x33/0x39/0x1/0x0`) do not include the `DRAW_IAB` call, so the draw never
-  stores (`wrote=0`, `px0=0`); the window/screen present is unproven, and the
-  per-boot binding plus X first-generation lottery is the throughput limiter.
-  Those are the
+  reproduced on two boots). The release path is now host-deterministic when
+  the pack completes: the saved-window release carrier snapshots the held
+  window and re-submits it with the calls released once the pack is resident
+  (c772), and the held-CALL census plus the SA[34] golden fill prove the
+  slot-34 `DRAW_IAB` target (`client=golden=used=0x265`). No non-black
+  **window/screen** frame has been produced through the NVIDIA path yet: the
+  blocker is call order (the 728-B window places slot-34 after the `0x33/0x39`
+  setup, so the DS latch `0x84000420` pre-empts it; the 324-B window places it
+  first and ran `mac=0x22`), the reorder `a03a68ea` is landed but unexercised,
+  pack completion is still a per-boot lottery, the DS stage type/context bits
+  (SPH5/SPH10/SPH18) remain, and the draw does not store (`wrote=0`,
+  `px0=0`); the window/screen present is unproven, and the per-boot binding
+  plus X first-generation lottery is the throughput limiter. Those are the
   named blockers. The lanes and the ladder are on
   [`Graphics-Execution.md`](Graphics-Execution.md).