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, 16 insertions, 10 deletions

diff --git a/wiki/System-Overview.md b/wiki/System-Overview.md
index 26da5df..33cf881 100644
--- a/wiki/System-Overview.md
+++ b/wiki/System-Overview.md
@@ -7,7 +7,7 @@
 > and [`../docs/03-architecture/10-interaction-and-scheduling.md`](../docs/03-architecture/10-interaction-and-scheduling.md)
 > for the full picture); 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]` partial;
 `[wall]` current blocker; `[target]` designed end state.
 
@@ -142,15 +142,21 @@ RPC from the guest to "firmware":
    buffers and the display notifier/completion (class-aware arm), so
    nvidia-modeset/NvKms registers (`/dev/dri`), X settles and the stock NVIDIA
    GLX path is fully green (`glxinfo -B` rc 0, OpenGL 4.6.0 direct, `glxgears`
-   ~520 FPS); the X DDX waits are fixed, the DDX 3D replay executes, the 2D
-   path is green, the direct-GL ring/USERD machinery is hardened, the first
-   non-black GPU-rendered frames and captured videos (45.4 s and 50 s) are
-   proven off-screen, and the guest Vulkan pipeline runs end to end. The
-   direct-GL client's own setup push still does not resolve/read host-side
-   (so its draws never reach the engine), the window/screen present is
-   unproven (a window draw can wedge X and glxgears' window is black), and X
-   screen-init is a per-boot lottery, so the remaining gate is the window/
-   screen present before the first non-black window frame
+   ~520 FPS); the X DDX waits are fixed (the idle-DMA/ScreenInit, USERD-latch,
+   re-probe, kernel-mode-spin and flip-event walls are closed, and X has stayed
+   green >10 minutes), the DDX 3D replay executes, captured GL sections now
+   execute on the engine, the 2D path is green, the direct-GL ring/USERD
+   machinery is hardened, the first non-black GPU-rendered frames and captured
+   videos (45.4 s and 50 s) are proven off-screen, and the guest Vulkan
+   pipeline runs end to end. The client's push bodies decode as real GR method
+   streams above 10 GiB through the VAS walk, but the direct-GL payload VAs
+   (setup push `0x4001004`, draws `0x4250000`/`0x4250110`) still resolve to
+   zero/implausible PAs because their user/UVM VAS is never registered (so
+   its draws never reach the engine); the window/screen present is unproven
+   (a window draw can wedge X and glxgears' window is black), and X
+   screen-init keeps a first-generation lottery, so the remaining gate is
+   that registration plus the window/screen present before the first
+   non-black window frame
    ([`OpenGL.md`](OpenGL.md), [`Vulkan.md`](Vulkan.md)).
 
 ## 6. Where the detail lives