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

diff --git a/wiki/Host-Module.md b/wiki/Host-Module.md
index 6ffbed1..1fc6ee1 100644
--- a/wiki/Host-Module.md
+++ b/wiki/Host-Module.md
@@ -6,7 +6,7 @@
 > source: [`../docs/03-architecture/06-host-module-and-hybrid-model.md`](../docs/03-architecture/06-host-module-and-hybrid-model.md);
 > the docs tree wins on disagreement with this page.
 >
-> Status: 2026-11-11, tree `master @ 4acac093`. Tags: `[live]` observed with
+> Status: 2026-11-12, tree `master @ 800c108f`. Tags: `[live]` observed with
 > the stock guest driver; `[wip]` demonstrated live, being productized;
 > `[gated]` implemented default-off behind supervised gates; `[wall]` known
 > blocking limit; `[target]` designed, not built; `[planned]` roadmap.
@@ -127,12 +127,16 @@ own 2D push buffers the remaining host levers are publishing/advancing the
 GPU-written engine get word and recycling the notifier to `0xffff` after
 completion. The DDX 3D replay renders and reads back a pbuffer pixel
 (`pixel=ff0000ff`), the off-screen frame path produced 500/500 non-black
-animated frames and a 45.4 s video, the RM write-lock holder (Xorg in the
-DDX vidheap scrub wait) is fixed (`df6e71bb`), and the direct-GL GR ring
-`0xbeef0100` now resolves with advancing releases (`4acac093`). The remaining
-GL gap is the direct-GL CE ring `0xbeef0101` (it never resolves, so the
-client's CE work does not execute) and the window/screen present path, which
-currently wedges X or stays black.
+animated frames per run and captured videos (45.4 s and 50 s), the RM
+write-lock holder (Xorg in the DDX vidheap scrub wait) is fixed
+(`df6e71bb`), X and the stock GLX path are fully green (`glxinfo -B` rc 0,
+~520 FPS `glxgears`), and the direct-GL ring/VAS and USERD machinery is
+hardened (verified page-directory discovery, eager push pins,
+client-allocated USERD resolution, foreign-USERD skip). The remaining GL gap
+is delivery of the direct-GL client's own setup push (59,556 bytes at VA
+`0x4024004` — not yet resolvable/readable host-side under the client's
+page-directory churn) and the window/screen present path, which currently
+stays black or wedges X.
 
 ## 6. Debug parameters
 
@@ -174,8 +178,8 @@ The physical-backend path adds a default-off set of backend controls
 | Push decoding + semaphore completion [wip] | demonstrated live, being productized |
 | Emulation-mode CUDA end-to-end [live] | repeatable 1M-element `vectorAdd`, `bad=0` |
 | Guest-RAM physical path + server-owned page-table population [gated] | default-off; GPA→HPA via shared-file page cache verified live on the CE |
-| GPU work forwarding: CE copy, release and fault relay [gated] | default-off, verified live; GR open [wall] |
-| Execution backend (module-owned GPU, direct real-GSP session) [wall] | boot, static configuration and CE copies proven; GR execution open (failed mutating attempts park the device in a locked fail-safe, never auto-retried) |
+| GPU work forwarding: CE copy, release and fault relay [gated] | default-off, verified live; GR execution live for forwarded CUDA launches |
+| Execution backend (module-owned GPU, direct real-GSP session) [live] | boot, static configuration, CE copies and GR execution proven; failed mutating attempts park the device in a locked fail-safe, never auto-retried |
 | Real VRAM backing [target]; Windows, Xen, aarch64 [planned] | designed, not implemented |
 
 ## 9. Related documentation