wiki: 2026-11-11 status refresh - first non-black GPU frames + 45.4 s video; direct-GL GR ring resolves; CE-ring/window walls (STATE-CURRENT too)

1 files changed, 14 insertions, 12 deletions

diff --git a/wiki/FAQ.md b/wiki/FAQ.md
index e4361a6..d3e42db 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-09, tree `master @ df6e71bb`.
+Status: 2026-11-11, tree `master @ 4acac093`.
 
 ## Project and positioning
 
@@ -38,18 +38,20 @@ 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 now run on the emulated vGPU with the stock driver: nvidia-modeset/NvKms
+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 real GPU
-readback** landed (a pbuffer `glClear(red)+glReadPixels` probe returns
-`pixel=ff0000ff`). The RM write-lock holder (Xorg in the DDX vidheap scrub
-wait) was identified and fixed (`df6e71bb`). The guest Vulkan pipeline runs
-end to end (device → command buffer → fence → readback, frames black). Screen
-pixels are still the wall: the direct-GL client channel `0xbfef0002` emits
-only setup/notify kicks (`ops_runs=0`), a synchronous window draw wedges X,
-and X startup/RM degradation (`0x51`) plus the DDX's 4 GB sysmem allocation
-(12 GB guest workaround) remain — see [`OpenGL.md`](OpenGL.md),
-[`Vulkan.md`](Vulkan.md) and [`Graphics-Execution.md`](Graphics-Execution.md).
+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
+[`OpenGL.md`](OpenGL.md), [`Vulkan.md`](Vulkan.md) and
+[`Graphics-Execution.md`](Graphics-Execution.md).
 
 **How fast is it?**
 No published numbers yet. Kernel launches execute on the physical engine;