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, 13 deletions

diff --git a/wiki/System-Overview.md b/wiki/System-Overview.md
index 6ad4d3e..26da5df 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-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; `[wip]` partial;
 `[wall]` current blocker; `[target]` designed end state.
 
@@ -35,7 +35,7 @@ PASS THROUGH  (real hardware; correctness and performance)
   channel execution: guest push buffers on real channels   [wip]
   compute (CUDA) kernel launches on the real engine        [live]
   3D graphics method streams on the real engine            [wip]
-  rendered 3D pixels / video work                          [wall/planned]
+  rendered 3D pixels / video work (off-screen proven)      [wip]
   DMA, completion and fault interrupts relayed to the guest
 ```
 
@@ -140,17 +140,18 @@ RPC from the guest to "firmware":
    ([`Execution-Frontier.md`](Execution-Frontier.md)).
 6. On the graphics side, the emulated display engine serves the modeset push
    buffers and the display notifier/completion (class-aware arm), so
-   nvidia-modeset/NvKms registers (`/dev/dri`), X settles and `glxinfo`
-   reports OpenGL 4.6.0 with direct rendering; the direct GL client's
-   channels submit, the X DDX waits are fixed, the DDX 3D replay executes,
-   the 2D path is green, the first non-black GPU-rendered frames and a
-   45.4 s video are captured off-screen, the direct-GL GR ring resolves with
-   advancing releases, and the guest Vulkan pipeline runs end to end. The
-   direct-GL CE ring `0xbeef0101` still does not resolve, a window draw
-   wedges X (glxgears' window is black), and X window creation wedges on some
-   boots, so the remaining gate is the window/screen present before the
-   first non-black window frame ([`OpenGL.md`](OpenGL.md),
-   [`Vulkan.md`](Vulkan.md)).
+   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
+   ([`OpenGL.md`](OpenGL.md), [`Vulkan.md`](Vulkan.md)).
 
 ## 6. Where the detail lives