wiki: 2026-11-10 status refresh - guest GL draws execute on the physical GPU

Refresh STATE-CURRENT, the Main Page and the status/frontier pages: the GSP
event-IRQ fix completes swaps; the 2D path is green end-to-end; the guest's
real GL draws now forward and execute on the physical GPU (work_gr
backend_ok=9); the draw writes 0 pages because its constant-buffer (MVP)
page is unresolved and forced to the seed page; the MME front-end defer, GR
stale-wedge and the X DDX get-word/notifier completion remain. Published to
open-iov.org.

1 files changed, 12 insertions, 12 deletions

diff --git a/wiki/FAQ.md b/wiki/FAQ.md
index 5025175..f9d5251 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 @ 21e0d611`.
+Status: 2026-11-09, tree `master @ cb8e822b`.
 
 ## Project and positioning
 
@@ -40,17 +40,17 @@ progress). This is the project's known status, not a misconfiguration — see
 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
 registers (`/dev/dri`), `glxinfo` reports OpenGL 4.6.0 with direct rendering,
-the direct GL client's GR and CE channels submit and retire, and forcing GLX
-(`SDL_VIDEO_X11_FORCE_EGL=0`) selects `libnvidia-glcore`. The minimal
-windowed `glxgears` then hangs in the glcore kick wait: the client polls its
-per-slot `/dev/nvidia-modeset` fd and the guest kernel never signals the
-event, even though the host completes the beef notifier memory. The guest
-Vulkan pipeline runs end to end (device → command buffer → fence → readback,
-frames black). Rendered (non-black) frames through the NVIDIA path are the
-remaining wall: kernel-visible present completion, the X DDX
-get-word/notifier completion, the DDX's 4 GB sysmem allocation (12 GB guest
-workaround) and physical dispatch of the GL draws are the current gates —
-see [`OpenGL.md`](OpenGL.md), [`Vulkan.md`](Vulkan.md) and
+the direct GL client's GR and CE channels submit and retire, and the GSP
+event-IRQ fix completes swaps. The guest's **real GL draws now forward and
+execute on the physical GPU** (`work_gr backend_ok=9`) and the 2D path is
+green end-to-end, but the frames are black: the draw's constant-buffer (MVP)
+page does not resolve and is forced to the seed page, so the engine writes 0
+pages. The guest Vulkan pipeline runs end to end (device → command buffer →
+fence → readback, frames black). Rendered (non-black) frames through the
+NVIDIA path are the remaining wall: constant-buffer content, the MME
+front-end/stale-wedge stability, the X DDX get-word/notifier completion and
+the DDX's 4 GB sysmem allocation (12 GB guest workaround) are the current
+gates — see [`OpenGL.md`](OpenGL.md), [`Vulkan.md`](Vulkan.md) and
 [`Graphics-Execution.md`](Graphics-Execution.md).
 
 **How fast is it?**