docs(wiki): refresh status to 436cbf9d - DDX/X-stability walls closed, sections execute, push bodies decode above 10 GiB; remaining wall = direct-GL payload delivery (setup push recycled; draws 0x4250000)

1 files changed, 11 insertions, 8 deletions

diff --git a/wiki/Physical-GPU-Backend.md b/wiki/Physical-GPU-Backend.md
index bfd89bf..1f82bdf 100644
--- a/wiki/Physical-GPU-Backend.md
+++ b/wiki/Physical-GPU-Backend.md
@@ -5,7 +5,7 @@
 > guest-facing emulation. Canonical sources: [`../docs/03-architecture/08-physical-gpu-integration.md`](../docs/03-architecture/08-physical-gpu-integration.md)
 > and [`../docs/03-architecture/11-physical-backend-guest-wiring.md`](../docs/03-architecture/11-physical-backend-guest-wiring.md); the docs tree wins on disagreement.
 
-Status: 2026-11-12, tree `master @ 800c108f`. Tags: `[live]` proven with the
+Status: 2026-11-13, tree `master @ 436cbf9d`. Tags: `[live]` proven with the
 stock guest driver; `[gated]` implemented default-off; `[wip]` partially
 built; `[wall]` current blocker; `[target]` planned end state.
 
@@ -109,7 +109,7 @@ FAIL  a failed mutating operation parks the device in a locked fail-safe;
 | Host RM client and first real engine work (static config, real objects, 4 KiB CE copy) | done `[live]` |
 | Guest-copy forwarding, deferred release, hardware-primary copies, engine-authored relay, fault relay | verified live (seams parameterised and fail-open); the staged-transfer class is under repair `[live]` |
 | CUDA kernel execution (`vectorAdd` and further clients) | done `[live]` — stock guest CUDA clients (vector-add, matrix-multiply, transformer) execute on the physical engine with verified results and engine-authored completions relayed to the guest |
-| Graphics method-stream execution (verbatim 3D replay, synthesized launches, direct-GL client channels) | `[wip]` — the engine retires real graphics streams, the display/KMS stack registers and X + stock GLX are green, and the first non-black GPU-rendered frames are captured off-screen; delivery of the direct-GL client's own command stream and the window/screen present are the frontier ([`Graphics-Execution.md`](Graphics-Execution.md)) |
+| Graphics method-stream execution (verbatim 3D replay, synthesized launches, direct-GL client channels) | `[wip]` — the engine retires real graphics streams, the display/KMS stack registers and X + stock GLX are green (the DDX/ScreenInit stability walls are closed, X green >10 minutes), captured GL sections execute, and the first non-black GPU-rendered frames are captured off-screen; registration of the direct-GL payload user/UVM VAS (setup/draw pushes still resolve to zero/implausible PAs) and the window/screen present are the frontier ([`Graphics-Execution.md`](Graphics-Execution.md)) |
 
 ## 7. The execution frontier
 
@@ -123,12 +123,15 @@ same machinery in three shapes (a verbatim 3D method-stream replay,
 synthesized launches, and the direct GL client's own GR/CE channels); the
 captured and synthesized streams execute on the engine, and the direct GL
 client's ring/USERD machinery is hardened. The display/KMS stack registers,
-the X DDX waits are fixed, X and the stock GLX path are fully green
-(`glxinfo -B` rc 0, ~520 FPS `glxgears`), the DDX 3D replay executes, and the
-first non-black GPU-rendered frames are proven (500/500 off-screen frames per
-run plus captured videos); the remaining graphics gates are delivery of the
-direct-GL client's own 59,556-byte setup push, the window/screen present, and
-X screen-init stability before non-black window pixels. The remaining
+the X DDX waits are fixed (the idle-DMA/ScreenInit, USERD-latch, re-probe,
+kernel-mode-spin and flip-event walls are closed, X green >10 minutes), X and
+the stock GLX path are fully green (`glxinfo -B` rc 0, ~520 FPS `glxgears`),
+the DDX 3D replay executes, captured GL sections execute on the engine, and
+the first non-black GPU-rendered frames are proven (500/500 off-screen frames
+per run plus captured videos); the remaining graphics gates are registration
+of the direct-GL payload user/UVM VAS (setup/draw pushes still resolve to
+zero/implausible PAs), the window/screen present, and the X first-generation
+screen-init lottery before non-black window pixels. The remaining
 compute work is the staged-transfer class (under repair), the every-boot
 acceptance campaign, and per-guest execution isolation — see
 [`Execution-Frontier.md`](Execution-Frontier.md) and