wiki: 2026-11-10 morning refresh - X reliable, GR timeouts fixed; beef-ring/CB/RT walls

Refresh STATE-CURRENT, the Main Page and the status/frontier pages:
ebf3130f fixes the X DMA-init path and flips the GR pair-close/pair-safe
replay fixes default ON (X green on attempt 1 in three consecutive cycles,
backend_timeout=0, draws retire in 3-2400 ms); bb802909 is committed. The
replayed draw still writes 0 pages; the beef GR ring resolution, the
fixed-CB image's zero 0x80 MVP block and the render-target bind are the
named walls. Published to open-iov.org.

12 files changed, 184 insertions, 176 deletions

diff --git a/wiki/.publish-manifest.json b/wiki/.publish-manifest.json
index 239ab66..7d7d30c 100644
--- a/wiki/.publish-manifest.json
+++ b/wiki/.publish-manifest.json
@@ -64,11 +64,11 @@
  },
  "FAQ": {
   "file": "FAQ.wiki",
-  "new_revid": 24073,
-  "old_revid": 24061,
-  "source_sha": "993f4e23553d2842",
-  "summary": "2026-11-10 status refresh: guest GL draws forward and execute on the physical GPU; the 0-pixel wall is the constant-buffer (MVP) content",
-  "timestamp": "2026-11-10T10:23:37Z",
+  "new_revid": 24085,
+  "old_revid": 24073,
+  "source_sha": "a3695d0713019777",
+  "summary": "2026-11-10 morning refresh: X reliable on attempt 1, GR backend timeout=0; beef-ring resolution, fixed-CB MVP and render-target bind are the 0-pixel walls",
+  "timestamp": "2026-11-10T11:03:38Z",
   "title": "FAQ"
  },
  "GMMU Multi-Tenant Protection": {
@@ -127,11 +127,11 @@
  },
  "Graphics Execution": {
   "file": "Graphics-Execution.wiki",
-  "new_revid": 24074,
-  "old_revid": 24062,
-  "source_sha": "bbc2783864468dab",
-  "summary": "2026-11-10 status refresh: guest GL draws forward and execute on the physical GPU; the 0-pixel wall is the constant-buffer (MVP) content",
-  "timestamp": "2026-11-10T10:23:37Z",
+  "new_revid": 24086,
+  "old_revid": 24074,
+  "source_sha": "d10808a904df291e",
+  "summary": "2026-11-10 morning refresh: X reliable on attempt 1, GR backend timeout=0; beef-ring resolution, fixed-CB MVP and render-target bind are the 0-pixel walls",
+  "timestamp": "2026-11-10T11:03:38Z",
   "title": "Graphics Execution"
  },
  "Guest Driver Lifecycle: A Field Guide": {
@@ -190,11 +190,11 @@
  },
  "Main Page": {
   "file": "Main-Page.wiki",
-  "new_revid": 24082,
-  "old_revid": 24070,
-  "source_sha": "fb770eaffa1533f3",
-  "summary": "2026-11-10 status refresh: guest GL draws execute on the physical GPU; constant-buffer (MVP) content is the 0-pixel wall",
-  "timestamp": "2026-11-10T10:23:50Z",
+  "new_revid": 24094,
+  "old_revid": 24082,
+  "source_sha": "da191925550b19fa",
+  "summary": "2026-11-10 morning refresh: X reliable, GL draws execute on the physical GPU; beef-ring/CB/render-target are the 0-pixel walls",
+  "timestamp": "2026-11-10T11:03:46Z",
   "title": "Main Page"
  },
  "MediaWiki:Sidebar": {
@@ -226,11 +226,11 @@
  },
  "OpenGL": {
   "file": "OpenGL.wiki",
-  "new_revid": 24076,
-  "old_revid": 24064,
-  "source_sha": "144f1627a14c54a3",
-  "summary": "2026-11-10 status refresh: guest GL draws forward and execute on the physical GPU; the 0-pixel wall is the constant-buffer (MVP) content",
-  "timestamp": "2026-11-10T10:23:38Z",
+  "new_revid": 24088,
+  "old_revid": 24076,
+  "source_sha": "1439d7e61bb4afde",
+  "summary": "2026-11-10 morning refresh: X reliable on attempt 1, GR backend timeout=0; beef-ring resolution, fixed-CB MVP and render-target bind are the 0-pixel walls",
+  "timestamp": "2026-11-10T11:03:39Z",
   "title": "OpenGL"
  },
  "Performance": {
@@ -244,38 +244,38 @@
  },
  "Physical GPU Backend and Guest Wiring": {
   "file": "Physical-GPU-Backend.wiki",
-  "new_revid": 24077,
-  "old_revid": 24065,
-  "source_sha": "5a0b0fab129d042c",
-  "summary": "2026-11-10 status refresh: guest GL draws forward and execute on the physical GPU; the 0-pixel wall is the constant-buffer (MVP) content",
-  "timestamp": "2026-11-10T10:23:39Z",
+  "new_revid": 24089,
+  "old_revid": 24077,
+  "source_sha": "104da451cf4a4654",
+  "summary": "2026-11-10 morning refresh: X reliable on attempt 1, GR backend timeout=0; beef-ring resolution, fixed-CB MVP and render-target bind are the 0-pixel walls",
+  "timestamp": "2026-11-10T11:03:40Z",
   "title": "Physical GPU Backend and Guest Wiring"
  },
  "Project Goals": {
   "file": "Project-Goals.wiki",
-  "new_revid": 24078,
-  "old_revid": 24066,
-  "source_sha": "1a1a231fa6da0d5a",
-  "summary": "2026-11-10 status refresh: guest GL draws forward and execute on the physical GPU; the 0-pixel wall is the constant-buffer (MVP) content",
-  "timestamp": "2026-11-10T10:23:39Z",
+  "new_revid": 24090,
+  "old_revid": 24078,
+  "source_sha": "245994b5a1df60aa",
+  "summary": "2026-11-10 morning refresh: X reliable on attempt 1, GR backend timeout=0; beef-ring resolution, fixed-CB MVP and render-target bind are the 0-pixel walls",
+  "timestamp": "2026-11-10T11:03:41Z",
   "title": "Project Goals"
  },
  "Project Plan": {
   "file": "Project-Plan.wiki",
-  "new_revid": 24079,
-  "old_revid": 24067,
-  "source_sha": "dba7840c299c0751",
-  "summary": "2026-11-10 status refresh: guest GL draws forward and execute on the physical GPU; the 0-pixel wall is the constant-buffer (MVP) content",
-  "timestamp": "2026-11-10T10:23:40Z",
+  "new_revid": 24091,
+  "old_revid": 24079,
+  "source_sha": "4a9d126b6cb4e391",
+  "summary": "2026-11-10 morning refresh: X reliable on attempt 1, GR backend timeout=0; beef-ring resolution, fixed-CB MVP and render-target bind are the 0-pixel walls",
+  "timestamp": "2026-11-10T11:03:41Z",
   "title": "Project Plan"
  },
  "Project Status": {
   "file": "Project-Status.wiki",
-  "new_revid": 24080,
-  "old_revid": 24068,
-  "source_sha": "1fe9bb91cd4cef31",
-  "summary": "2026-11-10 status refresh: guest GL draws forward and execute on the physical GPU; the 0-pixel wall is the constant-buffer (MVP) content",
-  "timestamp": "2026-11-10T10:23:40Z",
+  "new_revid": 24092,
+  "old_revid": 24080,
+  "source_sha": "098085f72e17533f",
+  "summary": "2026-11-10 morning refresh: X reliable on attempt 1, GR backend timeout=0; beef-ring resolution, fixed-CB MVP and render-target bind are the 0-pixel walls",
+  "timestamp": "2026-11-10T11:03:42Z",
   "title": "Project Status"
  },
  "RPC Message Format": {
@@ -289,11 +289,11 @@
  },
  "System Overview": {
   "file": "System-Overview.wiki",
-  "new_revid": 24081,
-  "old_revid": 24069,
-  "source_sha": "5d3502ef3e24189d",
-  "summary": "2026-11-10 status refresh: guest GL draws forward and execute on the physical GPU; the 0-pixel wall is the constant-buffer (MVP) content",
-  "timestamp": "2026-11-10T10:23:41Z",
+  "new_revid": 24093,
+  "old_revid": 24081,
+  "source_sha": "e0e0596d01be29f2",
+  "summary": "2026-11-10 morning refresh: X reliable on attempt 1, GR backend timeout=0; beef-ring resolution, fixed-CB MVP and render-target bind are the 0-pixel walls",
+  "timestamp": "2026-11-10T11:03:42Z",
   "title": "System Overview"
  },
  "Template:About message": {
@@ -325,11 +325,11 @@
  },
  "The Execution Frontier": {
   "file": "Execution-Frontier.wiki",
-  "new_revid": 24071,
-  "old_revid": 24059,
-  "source_sha": "e6debfdea2d1a520",
-  "summary": "2026-11-10 status refresh: guest GL draws forward and execute on the physical GPU; the 0-pixel wall is the constant-buffer (MVP) content",
-  "timestamp": "2026-11-10T10:23:36Z",
+  "new_revid": 24083,
+  "old_revid": 24071,
+  "source_sha": "0c7c530a98d2500a",
+  "summary": "2026-11-10 morning refresh: X reliable on attempt 1, GR backend timeout=0; beef-ring resolution, fixed-CB MVP and render-target bind are the 0-pixel walls",
+  "timestamp": "2026-11-10T11:03:37Z",
   "title": "The Execution Frontier"
  },
  "The Guest Stack and CUDASW": {
@@ -343,20 +343,20 @@
  },
  "The Host Module (vgsp.ko)": {
   "file": "Host-Module.wiki",
-  "new_revid": 24075,
-  "old_revid": 24063,
-  "source_sha": "278deddb70a2098d",
-  "summary": "2026-11-10 status refresh: guest GL draws forward and execute on the physical GPU; the 0-pixel wall is the constant-buffer (MVP) content",
-  "timestamp": "2026-11-10T10:23:38Z",
+  "new_revid": 24087,
+  "old_revid": 24075,
+  "source_sha": "4fd9d5ce2f854c52",
+  "summary": "2026-11-10 morning refresh: X reliable on attempt 1, GR backend timeout=0; beef-ring resolution, fixed-CB MVP and render-target bind are the 0-pixel walls",
+  "timestamp": "2026-11-10T11:03:39Z",
   "title": "The Host Module (vgsp.ko)"
  },
  "The vGSP Execution Plane (vEP)": {
   "file": "Execution-Plane.wiki",
-  "new_revid": 24072,
-  "old_revid": 24060,
-  "source_sha": "4124b0721387025d",
-  "summary": "2026-11-10 status refresh: guest GL draws forward and execute on the physical GPU; the 0-pixel wall is the constant-buffer (MVP) content",
-  "timestamp": "2026-11-10T10:23:36Z",
+  "new_revid": 24084,
+  "old_revid": 24072,
+  "source_sha": "3a5417132a0616d9",
+  "summary": "2026-11-10 morning refresh: X reliable on attempt 1, GR backend timeout=0; beef-ring resolution, fixed-CB MVP and render-target bind are the 0-pixel walls",
+  "timestamp": "2026-11-10T11:03:37Z",
   "title": "The vGSP Execution Plane (vEP)"
  },
  "UVM in the Guest": {
diff --git a/wiki/Execution-Frontier.md b/wiki/Execution-Frontier.md
index 18f150c..d90fdd7 100644
--- a/wiki/Execution-Frontier.md
+++ b/wiki/Execution-Frontier.md
@@ -14,7 +14,7 @@
 > [`../docs/04-implementation/03-execution-frontier.md`](../docs/04-implementation/03-execution-frontier.md);
 > the docs tree wins on disagreement.
 
-Status: 2026-11-09, tree `master @ cb8e822b`.
+Status: 2026-11-09, tree `master @ bb802909`.
 Tags: `[live]` observed; `[wip]` partial; `[wall]` current blocker; theories
 are labelled as such.
 
@@ -104,12 +104,11 @@ release applied); the direct GL client's GR and CE channels submit and retire,
 and the X DDX kick channel is decoded. GZDoom reached `MAP01` once the DDX
 push-buffer loop was unblocked, but on Mesa llvmpipe — not the emulated vGPU.
 What is missing is **rendered pixels through the NVIDIA path**: the GSP
-event-IRQ fix completes swaps, the 2D path is green end-to-end, and the
-guest's real GL draws now forward and execute on the physical GPU, but the
-draw writes 0 pages because its constant-buffer (MVP) page is unresolved and
-forced to the seed page; the MME front-end defer, the GR stale-wedge and the
-DDX push-buffer get-word/notifier completion remain. The guest Vulkan
-pipeline's inline-to-memory upload arm is its gap. The full
+event-IRQ fix completes swaps, the 2D path is green end-to-end, X is reliable,
+and the guest's real GL draws forward and execute on the physical GPU, but the
+draw writes 0 pages. The beef GR ring resolution race, the fixed-CB image's
+zero `0x80` MVP block and the render-target bind are the named walls. The
+guest Vulkan pipeline's inline-to-memory upload arm is its gap. The full
 picture lives on [`Graphics-Execution.md`](Graphics-Execution.md).
 
 No breadth beyond these is claimed: Windows guests, migration and performance
@@ -168,12 +167,11 @@ CUDA guests is in progress.
 
 **Issue D — the graphics pixel frontier.** The display/KMS stack and the GL
 client now run end to end (NvKms registers, X settles, GL 4.6, direct-GL
-channels submit and retire, the X DDX waits are fixed), and the guest's real
-GL draws forward and execute on the physical GPU; but the draw writes 0 pages
-because its constant-buffer (MVP) page is unresolved and forced to the seed
-page, and no rendered (non-black) frame has been produced yet. The constant
-buffer, the MME front-end/stale-wedge stability and the DDX get-word/notifier
-completion are the named blockers
+channels submit and retire, the X DDX waits are fixed, X is reliable, and the
+guest's real GL draws forward and execute on the physical GPU); but the draw
+writes 0 pages and no rendered (non-black) frame has been produced yet. The
+beef GR ring resolution, the fixed-CB image's zero MVP block and the
+render-target bind are the named blockers
 ([`Graphics-Execution.md`](Graphics-Execution.md)).
 
 ## 6. Lines of investigation (live)
diff --git a/wiki/Execution-Plane.md b/wiki/Execution-Plane.md
index ef285a3..a48af30 100644
--- a/wiki/Execution-Plane.md
+++ b/wiki/Execution-Plane.md
@@ -8,7 +8,7 @@
 > when the two disagree, the docs tree wins. Front door:
 > [`../docs/README.md`](../docs/README.md).
 
-Status: 2026-11-09, tree `master @ cb8e822b`. Tags: `[live]` proven with the
+Status: 2026-11-09, tree `master @ bb802909`. Tags: `[live]` proven with the
 stock guest driver; `[gated]` implemented, default-off or parameter-gated;
 `[wip]` partial; `[wall]` current blocker; `[target]` named success latch;
 `[planned]` designed, not built.
@@ -149,11 +149,11 @@ guest: push + QMD + GPFIFO entry + doorbell (BAR0 0x88704)
   buffers plus the notifier/`UPDATE` completion, class-aware arm), so NvKms
   registers, X settles and GL 4.6 is live, the X DDX waits are fixed, and
   the guest's real GL draws now forward and execute on the physical GPU
-  (`backend_ok=9`); the 2D path is green. No rendered (non-black) frame has
-  been produced through the NVIDIA path yet: the constant-buffer (MVP) content
-  (the draw writes 0 pages), the MME front-end/stale-wedge stability and the
-  DDX push-buffer get-word/notifier completion are the named blockers. The
-  lanes and the ladder are on [`Graphics-Execution.md`](Graphics-Execution.md).
+  (`backend_ok=5-7`, `backend_timeout=0`); X is reliable and the 2D path is
+  green. No rendered (non-black) frame has been produced through the NVIDIA
+  path yet: the beef GR ring resolution race, the fixed-CB image's zero MVP
+  block and the render-target bind are the named blockers. The lanes and the
+  ladder are on [`Graphics-Execution.md`](Graphics-Execution.md).
 
 ## 6. Portability
 
diff --git a/wiki/FAQ.md b/wiki/FAQ.md
index f9d5251..57782e7 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 @ cb8e822b`.
+Status: 2026-11-09, tree `master @ bb802909`.
 
 ## Project and positioning
 
@@ -41,16 +41,15 @@ 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 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
+event-IRQ fix completes swaps. X is green on attempt 1, the guest's **real GL
+draws forward and execute on the physical GPU** (`work_gr backend_ok=5-7`,
+`backend_timeout=0`), and the 2D path is green end-to-end, but the frames are
+black: the replayed draw writes 0 pages because the beef GR ring does not
+resolve deterministically, the fixed-CB image's `0x80` MVP block is zero, and
+the render-target bind is unconfirmed. The guest Vulkan pipeline runs end to
+end (device → command buffer → fence → readback, frames black). These three
+plus 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?**
diff --git a/wiki/Graphics-Execution.md b/wiki/Graphics-Execution.md
index 7771d6a..ca04b8f 100644
--- a/wiki/Graphics-Execution.md
+++ b/wiki/Graphics-Execution.md
@@ -12,7 +12,7 @@
 > [`../docs/04-implementation/04-real-render-walls.md`](../docs/04-implementation/04-real-render-walls.md)
 > (the measured walls); the docs tree wins on disagreement.
 
-Status: 2026-11-09, tree `master @ cb8e822b`. Tags: `[live]` observed end to
+Status: 2026-11-09, tree `master @ bb802909`. Tags: `[live]` observed end to
 end; `[wip]` partially built; `[wall]` current blocker; `[target]` defined
 success state; `[planned]` designed, not built.
 
@@ -92,9 +92,10 @@ fidelity:
    applied), forcing GLX selects `libnvidia-glcore`, and the event-IRQ fix
    (`a478f0b4`) lets the guest service the completion, so glxgears completes
    swaps and the guest's real GL draws now forward and execute on the
-   physical GPU (`work_gr backend_ok=9`). What remains is the constant-buffer
-   (MVP) content, the MME front-end defer and GR stale-wedge, and the DDX
-   get-word/notifier completion (§6).
+   physical GPU (`work_gr backend_ok=5-7`, `backend_timeout=0`) and X is
+   reliable, but the draw still writes 0 pages. What remains is the beef GR
+   ring resolution race, the fixed-CB image's zero MVP block, and the
+   render-target bind (§6).
 
 ## 4. The channel and object picture
 
@@ -144,9 +145,11 @@ host-side levers now, and a diagnostic write of the get word released the
 DDX's reserve loop. For a windowed GL client the present is a kick; the GSP
 event-IRQ fix now sets the RISC-V SWGEN0 IRQSTAT/IRQMASK/IRQDEST and latches
 the CPU-tree leaf, so the guest services the event and glxgears completes
-swaps. The next completion step is the constant buffer: the draw's CB page
-must be resolved and copied into the seed page so the engine produces
-fragments.
+swaps, and the GR backend no longer times out (the pair-close/pair-safe
+replay fixes are default ON; draws retire in 3-2400 ms). The next completion
+step is the beef GR ring (so the fixed-CB scan runs on every cycle) and the
+CB image (its `0x80` MVP block is zero even when the scan runs), then the
+render-target bind.
 
 During bring-up the module also carries a **diagnostics-only mirror** for apps
 that spin on a shared progress word; it exists so a run can proceed while the
@@ -155,35 +158,33 @@ requires it switched off, along with any external poke.
 
 ## 6. Where the frontier is (ranked walls)
 
-1. **The constant buffer (MVP) content** `[wall]`. The guest's GL draws now
-   execute on the physical GPU, but the engine writes 0 pages. The draw's
-   constant-buffer source is forced to the seed page because
-   `cb-copy src=0x0cd70000 ... first8=00000000 ... src=synthetic-id` reads all
-   zeros; a guest-RAM scan found no MVP matrix and the `0x3f800000` vidmem
-   hits are shader microcode immediates. With a zero MVP every vertex
-   collapses to the origin, so there are no fragments. Decode the CB-bind
-   method on the beef channel, resolve that VA through the channel VAS, and
-   copy the real page into the seed page.
-2. **Execution stability** `[wall]`. The MME front-end is busy/deferred
-   (`MME-FE-DEFER` then forced loads) and the GR channel stale-wedges
-   (`GR-STALL-stale-wedge`, recovered), so the pipeline restarts mid-frame.
-   Fixing the CB page may unstick the MME; the wedge recovery needs a durable
-   fix.
-3. **The X DDX push-buffer completion** `[wall]`. The DDX's 2D reserve loop
-   exits only when the GPU-written engine get word advances (`get <= put`) and
-   the kick requires the notifier to be recycled to `0xffff` after completion.
-   `sema_vas_cand_ms=1` makes X green on attempt 1, but X can still die after a
-   few forward frames into the RM-degraded state.
+1. **Beef GR ring resolution** `[wall]`. `0xbeef0100` (the GL client GR
+   channel) registers with `vas=0` before its CE siblings publish
+   `0xbeef0300`; the shared VAS is then registered UNVERIFIED by the 1 ms
+   age-out, so the ring at `0x4020000` stays `ring_pa=0` and the fixed-CB scan
+   (gated to the `0xbeef0000` family) never runs. The next fix is to gate the
+   candidate promote on *verified* rather than *known* and retry every pump
+   turn.
+2. **The fixed-CB image MVP block** `[wall]`. Even on a cycle where the scan
+   runs (`r1687`), it decodes 1492 `0x3800` offsets plus 1497 `0x39c8` data
+   runs (1092 words) but the image's `0x80` MVP block is zero. Identified
+   parser bugs (subchannel bits 15:13, `0x238c` ONE_INC inline data, selector
+   B/C swap) are not yet applied; the MVP may live at an offset >= `0x1000` or
+   a selector B/C binding. With a zero MVP every vertex collapses to the
+   origin, so there are no fragments.
+3. **The render-target bind** `[wall]`. Confirm that the replayed draw's
+   render target is the page `bounce copy-out` compares
+   (`svc_surf_prelude_capture` currently picks the last trusted bind
+   globally).
 4. **The X DDX footprint** `[wall]`. The DDX allocates 4 GB of system pages at
    startup; an 8 GB guest has no headroom once GZDoom's own footprint lands
    and both are OOM-killed. Current runs use a 12 GB guest; the allocation is
    a suspected emulation gap (a 512 MiB emulated VRAM falling back to a 4 GB
    sysmem allocation) to fix.
-5. **Non-black frames and sustained rate** `[wall]`/`[target]`. Once the
-   constant buffer, the MME/wedge stability and the DDX get-word/notifier
-   completion land, the capture must show motion, then 60 fps in one VM with
-   no forcing, then two VMs on two mediated devices with non-black frames in
-   both.
+5. **Non-black frames and sustained rate** `[wall]`/`[target]`. Once the beef
+   ring, the CB image and the render-target bind land, the capture must show
+   motion, then 60 fps in one VM with no forcing, then two VMs on two mediated
+   devices with non-black frames in both.
 
 ## 7. What is proven today
 
@@ -193,18 +194,20 @@ requires it switched off, along with any external poke.
 | Display engine serves the modeset push buffers; notifier plus `UPDATE -> FINISHED` | `[live]` (campaign configuration) |
 | nvidia-modeset/NvKms registers (`/dev/dri/card0`, `renderD128`, `fb0`); `nvidia-smi -L` enumerates | `[live]` |
 | `glxinfo` reports the emulated GPU with the NVIDIA renderer (OpenGL 4.6.0, direct rendering) | `[live]` |
-| X server green with `sema_vas_cand_ms=1`; glxinfo 4.6.0 direct | `[live]` |
+| X green on attempt 1 in three consecutive cycles (`ebf3130f`) | `[live]` |
 | GSP event-IRQ fix wakes the guest poll; glxgears completes swaps | `[live]` |
 | 2D path end-to-end: accelerated X fills read back via `xwd` | `[live]` |
-| Guest's real GL draws forward and execute on the physical GPU (`work_gr backend_ok=9`) | `[live]` |
+| Guest's real GL draws forward and execute on the physical GPU (`work_gr backend_ok=5-7`) | `[live]` |
+| GR backend timeouts fixed (`backend_timeout=0`; draws retire in 3-2400 ms) | `[live]` |
+| CB-DIAG decodes the draw's fixed-CB stream (1492 `0x3800` offsets, 1092 words) | `[live]` |
 | Beef GR channel `0xbeef0100` captures real GL draw sections | `[live]` |
 | GL section capture: the X channel's `0xC597` stream decoded | `[live]` |
 | Verbatim 3D method-stream replay retired by the engine (no MMU fault) | `[live]` |
 | Synthesized launch executes real `sm_75` SASS; Turing `V3` program header accepted | `[live]` |
 | X server survives the run on a 12 GB guest (the DDX's 4 GB sysmem allocation forces the size) | `[live]` |
-| Constant-buffer (MVP) page resolves and the draw writes render-target pixels | `[wall]` |
-| MME front-end defer / GR stale-wedge stability | `[wall]` |
-| DDX push-buffer get-word publish and notifier recycle | `[wall]` |
+| Beef GR ring resolves deterministically; fixed-CB scan runs every cycle | `[wall]` |
+| Fixed-CB image's `0x80` MVP block becomes non-zero | `[wall]` |
+| Render-target bind matches the copy-out page | `[wall]` |
 | NVIDIA Vulkan ICD creates a device | `[wall]` |
 | Non-black pixels from the emulated vGPU's 3D pipeline | `[wall]` |
 | Windows/DirectX guests | `[planned]` |
@@ -213,10 +216,10 @@ requires it switched off, along with any external poke.
 
 * No non-black pixel has been produced by the emulated vGPU's 3D pipeline yet.
 * Display/KMS bring-up (NvKms, `/dev/dri`, X, a real GL context) is not a
-  rendered-frame claim; the guest's GL draws now execute on the physical GPU
-  and glxgears completes swaps, but the frames are black. The constant-buffer
-  (MVP) content, the MME/wedge stability and the DDX get-word/notifier
-  completion are the current walls.
+  rendered-frame claim; the guest's GL draws now execute on the physical GPU,
+  X is reliable and glxgears completes swaps, but the frames are black. The
+  beef GR ring resolution, the fixed-CB image's zero MVP block and the
+  render-target bind are the current walls.
 * No frame-rate or latency numbers: the scheduled measurement is defined
   (60 fps over 60 s, no forcing) but not yet met.
 * The `virgl`-based demo videos are a different, labelled path — not this one.
diff --git a/wiki/Host-Module.md b/wiki/Host-Module.md
index 6405874..7099beb 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-09, tree `master @ cb8e822b`. Tags: `[live]` observed with
+> Status: 2026-11-09, tree `master @ bb802909`. 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.
@@ -109,7 +109,8 @@ plane. CE copies, release and fault relay are implemented default-off and
 verified live [gated]; forwarded guest CUDA launches execute on the engine
 with engine-authored completions relayed to the guest; the guest's real GL
 draws now forward and execute on the physical GR engine (`work_gr
-backend_ok=9`), and graphics method streams execute in three shapes,
+backend_ok=5-7`, `backend_timeout=0`), and graphics method streams execute in
+three shapes,
 including the direct GL client's own GR/CE channels
 ([`Execution-Frontier.md`](Execution-Frontier.md),
 [`Graphics-Execution.md`](Graphics-Execution.md)).
@@ -126,8 +127,9 @@ 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. For a windowed GL client the GSP event-IRQ path raises the
 RISC-V SWGEN0 interrupt and latches the CPU-tree leaf so the guest services
-the event and completes swaps; the remaining GL gap is the constant-buffer
-(MVP) page (the draw writes 0 pages) and the MME/wedge stability.
+the event and completes swaps; the remaining GL gap is the beef GR ring
+resolution (so the fixed-CB scan runs), the fixed-CB image's zero MVP block
+and the render-target bind (the draw writes 0 pages).
 
 ## 6. Debug parameters
 
diff --git a/wiki/OpenGL.md b/wiki/OpenGL.md
index 1219b84..c499967 100644
--- a/wiki/OpenGL.md
+++ b/wiki/OpenGL.md
@@ -12,7 +12,7 @@
 > [`../docs/03-architecture/02-guest-stack-and-cudasw.md`](../docs/03-architecture/02-guest-stack-and-cudasw.md)
 > (the guest stack). The docs tree wins on disagreement.
 
-Status: 2026-11-09, tree `master @ cb8e822b`. Tags: `[live]` observed with the
+Status: 2026-11-09, tree `master @ bb802909`. Tags: `[live]` observed with the
 stock guest driver; `[wip]` partial; `[wall]` current blocker; `[target]`
 defined success state.
 
@@ -75,18 +75,20 @@ Rated honestly, against the milestone ladder in the plan:
 | nvidia-modeset/NvKms registers (`/dev/dri/card0`, `renderD128`, `fb0`); `nvidia-smi -L` enumerates | `[live]` (campaign configuration) |
 | `glxinfo -B` reports the NVIDIA renderer (OpenGL 4.6.0, driver 570.144, direct rendering) | `[live]` |
 | The X driver's RC-watchdog channel registers and its notifier is authored | `[live]` |
-| X server green with `sema_vas_cand_ms=1`; `glxinfo -B` NVIDIA 4.6.0 direct | `[live]` |
+| X green on attempt 1 in three consecutive cycles (`ebf3130f`) | `[live]` |
 | GSP event-IRQ fix wakes the guest poll; glxgears completes swaps | `[live]` |
 | 2D path end-to-end: accelerated X fills read back via `xwd` | `[live]` |
-| Guest's real GL draws forward and execute on the physical GPU (`work_gr backend_ok=9`) | `[live]` |
+| Guest's real GL draws forward and execute on the physical GPU (`work_gr backend_ok=5-7`) | `[live]` |
+| GR backend timeouts fixed (`backend_timeout=0`; draws retire in 3-2400 ms) | `[live]` |
+| CB-DIAG decodes the draw's fixed-CB stream (1492 `0x3800` offsets, 1092 words) | `[live]` |
 | Beef GR channel `0xbeef0100` captures real GL draw sections | `[live]` |
 | Engine executes a launch built from the captured section (real `sm_75` SASS retired) | `[live]` |
 | Verbatim 3D method-stream replay retired by the engine, no MMU fault | `[live]` |
 | Direct GL client submits and retires its per-frame draws (GR `0xbeef0100`, CE `0xbeef0101`/`0xbeef0102`); DDX kick channel decoded | `[live]` |
 | X server survives the run on a 12 GB guest (the DDX's 4 GB sysmem allocation forces the size) | `[live]` |
-| Constant-buffer (MVP) page resolves and the draw writes render-target pixels | `[wall]` |
-| MME front-end defer / GR stale-wedge stability | `[wall]` |
-| DDX push-buffer get-word publish and notifier recycle | `[wall]` |
+| Beef GR ring resolves deterministically; fixed-CB scan runs every cycle | `[wall]` |
+| Fixed-CB image's `0x80` MVP block becomes non-zero | `[wall]` |
+| Render-target bind matches the copy-out page | `[wall]` |
 | NVIDIA Vulkan ICD creates a device | `[wall]` |
 | Non-black rendered frames through the emulated vGPU | `[wall]` |
 | 60 fps sustained, no forcing (M-GL4) | `[target]` |
@@ -110,17 +112,18 @@ non-black through the mdev), M-GL4 (60 fps, no forcing), M-GL5 (two VMs, two
 mdevs), M-GL6 (split-screen video). The project sits **between M-GL1 and
 M-GL2**: the interface and execution work is done — the display/KMS stack
 registers, X settles, the client submits and retires its GR/CE channels, and
-the guest's GL draws forward and execute on the physical GPU. The remaining
-gates are the constant-buffer (MVP) page, the MME front-end/stale-wedge
-stability, and the X DDX get-word/notifier completion before the first
-rendered frame.
+the guest's GL draws forward and execute on the physical GPU and X is
+reliable. The remaining gates are the beef GR ring resolution, the fixed-CB
+image's zero MVP block, and the render-target bind before the first rendered
+frame.
 
 ## 6. What is not claimed
 
 * No OpenGL frame from the emulated vGPU has produced real rendered pixels
   yet; every capture so far is black. glxgears completes swaps and its GL
-  draws execute on the physical GPU, but the constant-buffer (MVP) page does
-  not resolve, so the engine writes 0 pages.
+  draws execute on the physical GPU, but the replayed draw still writes 0
+  pages: the beef ring, the fixed-CB image's zero MVP block and the
+  render-target bind are unresolved.
 * No frame-rate or latency numbers.
 * The published two-VM GZDoom demo videos used the labelled `virtio-gpu`/
   `virgl` path, not the emulated vGPU.
diff --git a/wiki/Physical-GPU-Backend.md b/wiki/Physical-GPU-Backend.md
index 6b64d46..240e8fe 100644
--- a/wiki/Physical-GPU-Backend.md
+++ b/wiki/Physical-GPU-Backend.md
@@ -5,7 +5,7 @@
 > guest-facing emulation. Canonical sources: [`../docs/03-architecture/08-physical-gpu-integration.md`](../docs/03-architecture/08-physical-gpu-integration.md)
 > and [`../docs/03-architecture/11-physical-backend-guest-wiring.md`](../docs/03-architecture/11-physical-backend-guest-wiring.md); the docs tree wins on disagreement.
 
-Status: 2026-11-09, tree `master @ cb8e822b`. Tags: `[live]` proven with the
+Status: 2026-11-09, tree `master @ bb802909`. Tags: `[live]` proven with the
 stock guest driver; `[gated]` implemented default-off; `[wip]` partially
 built; `[wall]` current blocker; `[target]` planned end state.
 
@@ -123,10 +123,10 @@ same machinery in three shapes (a verbatim 3D method-stream replay,
 synthesized launches, and the direct GL client's own GR/CE channels); the
 captured and synthesized streams execute on the engine, and the direct GL
 client's channels submit. The display/KMS stack registers, the X DDX waits are
-fixed, X settles and the guest's real GL draws forward and execute on the
-physical GPU, so the remaining graphics gates are the constant-buffer (MVP)
-content, the MME front-end/stale-wedge stability, and the DDX push-buffer
-get-word/notifier completion before rendered pixels. The remaining compute work is the staged-transfer
+fixed, X is reliable and the guest's real GL draws forward and execute on the
+physical GPU, so the remaining graphics gates are the beef GR ring
+resolution, the fixed-CB image's zero MVP block and the render-target bind
+before rendered pixels. The remaining compute work is the staged-transfer
 class (under repair), the every-boot acceptance campaign, and per-guest
 execution isolation — see
 [`Execution-Frontier.md`](Execution-Frontier.md) and
diff --git a/wiki/Project-Goals.md b/wiki/Project-Goals.md
index 942c0d3..5842046 100644
--- a/wiki/Project-Goals.md
+++ b/wiki/Project-Goals.md
@@ -10,7 +10,7 @@
 > [`Execution-Frontier.md`](Execution-Frontier.md) and
 > [`Graphics-Execution.md`](Graphics-Execution.md).
 
-Status: 2026-11-09, tree `master @ cb8e822b`. Tags: `[live]` working with the
+Status: 2026-11-09, tree `master @ bb802909`. Tags: `[live]` working with the
 stock guest driver; `[wip]` in progress; `[planned]` designed, not built;
 `[target]` bring-up ahead; `[non-goal]` explicitly out of scope.
 
@@ -51,7 +51,7 @@ drivers, no license.**
 | Stock guest driver initialisation | The unmodified driver probes, initialises and enumerates as on bare metal (`nvidia-smi`) | `[live]` — TU104 reference platform |
 | Full CUDA driver-API surface | Context creation, allocation, copies, free, destroy complete with correct results | `[live]` — the driver-API smoke prints `ALL OK`; the 64-byte payload round-trips |
 | CUDA kernel execution on real hardware | Verified guest kernels execute on the physical GPU, with engine-authored completions waking the guest | `[live]` — vector-add, matrix-multiply and transformer clients green on fresh boots; the staged-transfer class, the every-boot acceptance campaign and per-guest isolation are in progress ([`Execution-Frontier.md`](Execution-Frontier.md)) |
-| OpenGL (3D graphics) | Stock guest GL applications render real pixels through the emulated vGPU | `[wip]` — the display/KMS stack and X run (NvKms registers, `glxinfo` OpenGL 4.6.0 direct), the direct GL client's GR/CE channels submit and retire, and the guest's real GL draws now forward and execute on the physical GPU (`backend_ok=9`); the 2D path is green, but the draw writes 0 pixels because its constant-buffer (MVP) page does not resolve. Constant-buffer content, MME/wedge stability and the DDX get-word/notifier completion are the frontier ([`OpenGL.md`](OpenGL.md)) |
+| OpenGL (3D graphics) | Stock guest GL applications render real pixels through the emulated vGPU | `[wip]` — the display/KMS stack and X run (NvKms registers, `glxinfo` OpenGL 4.6.0 direct), the direct GL client's GR/CE channels submit and retire, X is reliable, and the guest's real GL draws now forward and execute on the physical GPU (`backend_ok=5-7`); the 2D path is green, but the draw writes 0 pixels. The beef GR ring resolution, the fixed-CB image's zero MVP block and the render-target bind are the frontier ([`OpenGL.md`](OpenGL.md)) |
 | Vulkan | Stock guest Vulkan applications render real pixels | `[wip]` — the pipeline runs end to end (device → command buffer → fence → readback); frames are black — program delivery and program-VA mapping are the frontier ([`Vulkan.md`](Vulkan.md)) |
 | Windows guests (DirectX, CUDA) | A stock WDDM driver and stock D3D/CUDA applications run in Windows guests | `[target]` — not started; same emulation target ([`DirectX.md`](DirectX.md)) |
 | Video (NVENC/NVDEC) | Encode/decode through the emulated device | `[planned]` |
diff --git a/wiki/Project-Plan.md b/wiki/Project-Plan.md
index 8280697..0361ed6 100644
--- a/wiki/Project-Plan.md
+++ b/wiki/Project-Plan.md
@@ -15,7 +15,7 @@
 > [`../docs/06-portability/03-device-validation-and-porting-sequence.md`](../docs/06-portability/03-device-validation-and-porting-sequence.md);
 > the docs tree wins on disagreement.
 
-Status: 2026-11-09, tree `master @ cb8e822b`. Tags: `[done]`, `[active]`,
+Status: 2026-11-09, tree `master @ bb802909`. Tags: `[done]`, `[active]`,
 `[ahead]` — the plan's own state vocabulary, distinct from the goal tags.
 
 ## 1. How the plan works
@@ -44,7 +44,7 @@ itself:
 |---|---|---|---|
 | **P0 — Platform** | Emulated vGPU device, GSP boot and GSP-RM emulation, stock guest driver initialisation | Driver-API smoke green (`ALL OK`) = evaluation rung 2 | `[done]` |
 | **P1 — First execution (compute)** | Guest CUDA kernels executing on the physical GPU, with engine-authored completions; then hardening | Verified clients + engine-authored completion = rung 3 core; hardening: staged-transfer class, every-boot acceptance, per-guest isolation | `[active]` — execution green; hardening in progress |
-| **P2 — Graphics execution** | OpenGL/Vulkan draw commands executed by the physical 3D pipeline and delivered as readable pixels | The graphics ladder: M-GL1 client context-init executes; M-GL2 `glxgears` non-black; M-GL3 GZDoom GL non-black through the mdev | `[active]` — between M-GL1 and M-GL2; the display/KMS and direct-GL channel work is live and the guest's GL draws execute on the physical GPU; the constant-buffer (MVP) content, the MME/wedge stability and the DDX get-word/notifier completion are the walls |
+| **P2 — Graphics execution** | OpenGL/Vulkan draw commands executed by the physical 3D pipeline and delivered as readable pixels | The graphics ladder: M-GL1 client context-init executes; M-GL2 `glxgears` non-black; M-GL3 GZDoom GL non-black through the mdev | `[active]` — between M-GL1 and M-GL2; the display/KMS and direct-GL channel work is live, X is reliable, and the guest's GL draws execute on the physical GPU; the beef GR ring resolution, the fixed-CB image's zero MVP block and the render-target bind are the walls |
 | **P3 — Sustained and multi-tenant** | Frame rates without assistance; multiple VMs sharing the GPU with measured fairness; soak-stable operation | Graphics M-GL4 (60 fps, no forcing) and M-GL5 (two VMs, two mdevs); CUDA battery + soak; per-guest execution isolation = rungs 4/5 | `[ahead]` |
 | **P4 — Breadth** | Video (NVENC/NVDEC), Windows/DirectX guests, live migration, non-KVM hypervisor transports | Per-case bring-up gates plus the matrix's evidence expectations | `[ahead]` |
 | **P5 — Scale and portability** | New GPU generations and driver families carried forward; published performance programme | A profile + measured delta per version, validated on hardware; A/B numbers published per the measurement contract | `[ahead]` |
@@ -58,10 +58,11 @@ available (P5 runs across the whole plan).
 Ranked, in dependency order:
 
 1. **Graphics pixels (P2).** The client and display stacks execute, the
-   guest's GL draws forward and execute on the physical GPU, and the 2D path
-   is green; the named walls are the constant-buffer (MVP) content (the draw
-   writes 0 pages), the MME front-end/stale-wedge stability, the X DDX
-   push-buffer get-word/notifier completion, and the DDX's 4 GB sysmem
+   guest's GL draws forward and execute on the physical GPU, X is reliable,
+   and the 2D path is green; the named walls are the beef GR ring resolution
+   (the fixed-CB scan only runs when `0xbeef0100`'s ring resolves
+   deterministically), the fixed-CB image's zero `0x80` MVP block (parser
+   bugs identified), the render-target bind, and the DDX's 4 GB sysmem
    allocation (12 GB guest workaround), then non-black frames. Full detail:
    [`Graphics-Execution.md`](Graphics-Execution.md) §6.
 2. **Compute hardening (P1).** The staged-transfer class (failure modes proven,
@@ -80,9 +81,10 @@ bring-up (NvKms registers, X settles, GL 4.6); the UVM channel-pool tracker;
 the direct-GL GR release and CE ring discovery; the X DDX kick-channel decode
 and its three wait fixes (class-aware display arm, `0x8000 -> 0` notification
 completion, decoded GL release applied); the GSP event-IRQ fix that completes
-swaps; the 2D path end-to-end; the guest's real GL draws forwarding and
-executing on the physical GPU (`backend_ok=9`); and the guest Vulkan pipeline
-running end to end.
+swaps; the X DMA-init fix (`ebf3130f`) that makes X green on attempt 1; the
+GR backend timeout fix (`backend_timeout=0`); the 2D path end-to-end; the
+guest's real GL draws forwarding and executing on the physical GPU
+(`backend_ok=5-7`); and the guest Vulkan pipeline running end to end.
 
 ## 4. The gates
 
diff --git a/wiki/Project-Status.md b/wiki/Project-Status.md
index 4ebf765..5115706 100644
--- a/wiki/Project-Status.md
+++ b/wiki/Project-Status.md
@@ -10,7 +10,7 @@
 > (the execution frontier). When this page and the docs disagree, the docs tree
 > wins.
 
-Status: 2026-11-09, tree `master @ cb8e822b`. Tags: `[live]` proven with the
+Status: 2026-11-09, tree `master @ bb802909`. Tags: `[live]` proven with the
 stock guest driver; `[gated]` implemented, default-off or behind supervised
 gates; `[wip]` partially implemented; `[wall]` current blocker; `[target]`
 named success state; `[planned]` designed, not built.
@@ -28,7 +28,7 @@ named success state; `[planned]` designed, not built.
 | Physical backend on real hardware (module-owned GPU running its real GSP-RM) | `[live]` boot, RPC session, object creation, copy-engine work and GR execution proven — the verified guest CUDA kernel clients execute through this backend, and graphics method streams execute on the engine ([`Graphics-Execution.md`](Graphics-Execution.md)) |
 | Display and KMS on the emulated vGPU (nvidia-modeset/NvKms, `/dev/dri`, X) | `[live]` in the campaign configuration — the emulated display engine serves the guest's display push-buffer channels (notifier plus `UPDATE -> FINISHED`), nvidia-modeset/NvKms registers (`/dev/dri/card0`, `renderD128`, `fb0`), `nvidia-smi -L` enumerates and X settles; the display-capability seam is parameterised ([`Graphics-Execution.md`](Graphics-Execution.md)) |
 | Multi-tenant isolation (mdev per VM, per-context page directories) | `[wip]` device-level coexistence works — multiple mediated devices with different emulated VRAM sizes and multiple guests coexist (two guests demonstrated); per-guest execution isolation for simultaneous CUDA guests is in progress |
-| OpenGL (3D graphics) | `[wip]` — the display/KMS stack registers, X settles and `glxinfo` reports OpenGL 4.6.0 with direct rendering; the GSP event-IRQ fix completes swaps, the 2D path is green end-to-end, and the guest's **real GL draws now forward and execute on the physical GPU** (`work_gr backend_ok=9`; glxgears swaps, black). **No rendered pixels through the emulated vGPU yet:** the draw writes 0 pages because its constant-buffer (MVP) page is unresolved/zero and is forced to the seed page; the MME front-end defer, GR stale-wedge, X DDX get-word/notifier completion and the DDX's 4 GB sysmem allocation (12 GB guest) are the remaining walls ([`OpenGL.md`](OpenGL.md)) |
+| OpenGL (3D graphics) | `[wip]` — the display/KMS stack registers, X settles and `glxinfo` reports OpenGL 4.6.0 with direct rendering; the GSP event-IRQ fix completes swaps, the 2D path is green end-to-end, and the guest's **real GL draws forward and execute on the physical GPU** (`work_gr backend_ok=5-7`, `backend_timeout=0`); the X DMA-init path is fixed (`ebf3130f`) so X is green on attempt 1 in three consecutive cycles. **No rendered pixels through the emulated vGPU yet:** the replayed draw writes 0 pages; the walls are the beef GR ring resolution race (the fixed-CB scan only runs on `0xbeef0100`, whose ring at `0x4020000` is unresolved), the fixed-CB image's `0x80` MVP block being zero (1092 words decoded; parser bugs identified), and the render-target bind matching the copy-out; the DDX's 4 GB sysmem allocation (12 GB guest) remains ([`OpenGL.md`](OpenGL.md)) |
 | Vulkan (3D/compute) | `[wip]` — the guest Vulkan pipeline runs end to end on the emulated vGPU (device, allocation, pipeline, command buffer, fence, queue submit, readback) and the engine executes translated launches; frames are still black — program delivery and program-VA mapping are the frontier ([`Vulkan.md`](Vulkan.md)) |
 | DirectX / Windows guests | `[planned]` (target) — no Windows guest booted yet; the architecture is the same emulation target ([`DirectX.md`](DirectX.md)) |
 | Video (NVENC/NVDEC) | `[planned]` |
@@ -66,7 +66,7 @@ The project's definition of done for CUDA requires all of the following
 Until every gate holds, the honest formulation is: **initialization, the
 driver-API path and kernel execution on the physical GPU work and verify;
 the staged-transfer class, per-guest isolation and the graphics
-MVP-content/present/first-frame frontier remain.**
+beef-ring/CB/first-frame frontier remain.**
 
 ## 3. How to see it yourself
 
@@ -76,9 +76,10 @@ outcome is exactly the ladder above — driver probe, `nvidia-smi`, the full
 driver-API smoke, and guest CUDA kernels executing and verifying on the
 physical GPU. On the graphics side the same setup brings up the display/KMS
 stack and the X server on the emulated vGPU (`glxinfo` reports OpenGL 4.6.0
-with direct rendering); the guest's GL draws execute on the physical GPU and
-glxgears completes swaps, but the constant-buffer (MVP) page does not resolve,
-so the frames are black ([`OpenGL.md`](OpenGL.md)). The
+with direct rendering); X is green on attempt 1, the guest's GL draws retire
+and execute on the physical GPU, and the 2D path is green, but the draw still
+writes 0 pages because the beef-ring/CB/render-target chain does not resolve
+([`OpenGL.md`](OpenGL.md)). The
 risc-v-gsp-rm-debugger workbench
 ([`Riscv-GSP-RM-Debugger.md`](Riscv-GSP-RM-Debugger.md)) is the host-side
 tooling used to study the firmware side of that frontier.
diff --git a/wiki/System-Overview.md b/wiki/System-Overview.md
index 3531eeb..cf586cc 100644
--- a/wiki/System-Overview.md
+++ b/wiki/System-Overview.md
@@ -7,7 +7,7 @@
 > and [`../docs/03-architecture/10-interaction-and-scheduling.md`](../docs/03-architecture/10-interaction-and-scheduling.md)
 > for the full picture); the docs tree wins on disagreement.
 
-Status: 2026-11-09, tree `master @ cb8e822b`. Tags: `[live]` proven with the
+Status: 2026-11-09, tree `master @ bb802909`. Tags: `[live]` proven with the
 stock guest driver; `[gated]` implemented default-off; `[wip]` partial;
 `[wall]` current blocker; `[target]` designed end state.
 
@@ -142,13 +142,13 @@ RPC from the guest to "firmware":
    buffers and the display notifier/completion (class-aware arm), so
    nvidia-modeset/NvKms registers (`/dev/dri`), X settles and `glxinfo`
    reports OpenGL 4.6.0 with direct rendering; the direct GL client's
-   channels submit, the X DDX waits are fixed, the guest's real GL draws
-   forward and execute on the physical GPU, the 2D path is green, and the
-   guest Vulkan pipeline runs end to end. The draw writes 0 pixels because its
-   constant-buffer (MVP) page does not resolve, so the remaining gate is the
-   constant-buffer content, MME/wedge stability and the DDX get-word/notifier
-   completion before the first rendered (non-black) frame
-   ([`OpenGL.md`](OpenGL.md), [`Vulkan.md`](Vulkan.md)).
+   channels submit, the X DDX waits are fixed, X is reliable, the guest's
+   real GL draws forward and execute on the physical GPU, the 2D path is
+   green, and the guest Vulkan pipeline runs end to end. The draw still
+   writes 0 pixels, so the remaining gate is the beef GR ring resolution, the
+   fixed-CB image's zero MVP block and the render-target bind before the first
+   rendered (non-black) frame ([`OpenGL.md`](OpenGL.md),
+   [`Vulkan.md`](Vulkan.md)).
 
 ## 6. Where the detail lives