docs: 2026-11-12 status refresh - green X/GLX, non-black GPU captures, direct-GL stream frontier

Refresh STATE-CURRENT.md and the open-iov.org wiki pages with the 2026-11-12
state: stock-driver X + GLX green (glxinfo 4.6.0 direct rendering, glxgears
~520 FPS), the pbuffer frame path captured 500/500 non-black frames (50 s
640x480 h264) plus the earlier 45.4 s capture, and the named frontier
(direct-GL client command-stream delivery: setup push unreadable, CE ring
0xbeef0101 intermittent) alongside the guest-init/sizing fixes (RMInstLoc
modprobe single-source, FB info in KB, 256 MiB GART).

1 files changed, 14 insertions, 12 deletions

diff --git a/wiki/Execution-Plane.md b/wiki/Execution-Plane.md
index d88a1f3..88fbc9a 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-11, tree `master @ 4acac093`. Tags: `[live]` proven with the
+Status: 2026-11-12, tree `master @ 800c108f`. 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.
@@ -144,19 +144,21 @@ guest: push + QMD + GPFIFO entry + doorbell (BAR0 0x88704)
   isolation for simultaneous CUDA guests is in progress.
 * **The graphics pixel frontier.** Graphics work rides this plane in three
   shapes (verbatim 3D method-stream replay, synthesized launches, and the
-  direct GL client's own GR/CE channels, which now submit and retire). The
-  display/KMS path is served by the emulated display engine (modeset push
-  buffers plus the notifier/`UPDATE` completion, class-aware arm), so NvKms
-  registers, X settles and GL 4.6 is live, the X DDX waits are fixed, and
+  direct GL client's own GR/CE channels). The display/KMS path is served by
+  the emulated display engine (modeset push buffers plus the
+  notifier/`UPDATE` completion, class-aware arm), so NvKms registers, 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, and
   the guest's real GL draws now forward and execute on the physical GPU
   (`backend_ok=5-7`, `backend_timeout=0`); the DDX 3D replay executes, the 2D
-  path is green, the first non-black GPU-rendered frames are proven (500/500
-  off-screen frames plus a 45.4 s video), and the direct-GL **GR ring
-  `0xbeef0100` resolves with advancing releases**. No non-black **window/
-  screen** frame has been produced through the NVIDIA path yet: the direct-GL
-  **CE ring `0xbeef0101` never resolves** (the guest wedges ~90 s after
-  `V_Init`), glxgears' window is black, and X window creation wedges on some
-  boots, so those are the named blockers. The lanes and the ladder are on
+  path is green, the direct-GL ring/VAS and USERD machinery is hardened, and
+  the first non-black GPU-rendered frames are proven (500/500 off-screen
+  frames per run plus captured 45.4 s and 50 s videos). No non-black
+  **window/screen** frame has been produced through the NVIDIA path yet: the
+  direct-GL client's own 59,556-byte setup push does not yet resolve/read
+  host-side under its page-directory churn (so its draw sections never open),
+  glxgears' window is black, and X screen-init is a per-boot lottery, so
+  those are the named blockers. The lanes and the ladder are on
   [`Graphics-Execution.md`](Graphics-Execution.md).
 
 ## 6. Portability