1 files changed, 11 insertions, 7 deletions
diff --git a/wiki/FAQ.md b/wiki/FAQ.md
index 5aa4fa3..e357649 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-12, tree `master @ 800c108f`.
+Status: 2026-11-13, tree `master @ 436cbf9d`.
 
 ## Project and positioning
 
@@ -46,12 +46,16 @@ renders ~520 FPS), the 2D path is green and the DDX 3D replay executes. The
 `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
+context on an even modeNum. The X DDX idle-DMA/ScreenInit, USERD-latch,
+re-probe, kernel-mode-spin and flip-event walls were closed (X green >10
+minutes), captured GL sections now execute on the engine, and the client's
+push bodies decode as real GR method streams above 10 GiB. Window and screen
+pixels are still the wall: the direct-GL payload VAs (the `0x4001004` setup
+push and the `0x4250000`/`0x4250110` draws) resolve to zero/implausible PAs
+because their user/UVM VAS is never registered, so its draws never reach the
+engine; glxgears' window is black, and X screen-init keeps a per-boot
+first-generation 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).