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/FAQ.md b/wiki/FAQ.md
index d3e42db..5aa4fa3 100644
--- a/wiki/FAQ.md
+++ b/wiki/FAQ.md
@@ -5,7 +5,7 @@
 > [`../docs/09-reference/glossary-and-faq.md`](../docs/09-reference/glossary-and-faq.md);
 > the docs tree wins on disagreement.
 
-Status: 2026-11-11, tree `master @ 4acac093`.
+Status: 2026-11-12, tree `master @ 800c108f`.
 
 ## Project and positioning
 
@@ -39,17 +39,19 @@ progress). This is the project's known status, not a misconfiguration — see
 **Can I run OpenGL or Vulkan applications in the guest?**
 Partially, and it is an active frontier. The display/KMS stack and the X
 server run on the emulated vGPU with the stock driver: nvidia-modeset/NvKms
-registers (`/dev/dri`), `glxinfo` reports OpenGL 4.6.0 with direct rendering,
-the 2D path is green and the DDX 3D replay executes. The **first non-black
-GPU-rendered output** is proven: a pbuffer probe returns `pixel=ff0000ff`, the
-off-screen path produced 500/500 non-black animated frames, and a 45.4 s video
-was captured. The direct-GL GR channel now submits and its releases advance;
-GZDoom reaches `V_Init: allocate screen` with its GL 4.6.0 context. Window and
-screen pixels are still the wall: glxgears' window is black, the direct-GL CE
-channel does not yet resolve (GZDoom wedges ~90 s after `V_Init`), X window
-creation wedges on some boots, and the DDX's 4 GB sysmem allocation forces a
-12 GB guest. The guest Vulkan pipeline runs end to end (device → command
-buffer → fence → readback) but frames are black. See
+registers (`/dev/dri`), the stock NVIDIA GLX path is fully green
+(`glxinfo -B` returns 0 with OpenGL 4.6.0 direct rendering; `glxgears`
+renders ~520 FPS), the 2D path is green and the DDX 3D replay executes. The
+**first non-black GPU-rendered output** is proven: a pbuffer probe returns
+`pixel=ff0000ff`, the off-screen path produced 500/500 non-black animated
+frames per run, and videos were captured (45.4 s on 2026-11-11, 50 s on
+2026-11-12). GZDoom reaches `V_Init: allocate screen` with its GL 4.6.0
+context on an even modeNum. Window and screen pixels are still the wall: the
+direct-GL client's 59,556-byte setup push does not yet resolve/read host-side
+under its page-directory churn (so its draws never reach the engine),
+glxgears' window is black, and X screen-init is a per-boot lottery. The guest
+Vulkan pipeline runs end to end (device → command buffer → fence → readback)
+but frames are black. See
 [`OpenGL.md`](OpenGL.md), [`Vulkan.md`](Vulkan.md) and
 [`Graphics-Execution.md`](Graphics-Execution.md).