STATE-CURRENT: refresh snapshot - r632 mail hang root-caused+fixed (r633: held GR launches park their push-level release records and the eventual forward delivers them; mail green on two fresh boots), release-target question answered (rel_mod=1 default redirect, resolver works), synthetic shadow caps gated (anchor + per-episode; peak 2048/8192), best-ever battery r633b pass=9 fail=0 hang=1, r631 math red draw green; remaining top blocker = operand-resolution shortfall behind the wrongness class

1 files changed, 27 insertions, 21 deletions

diff --git a/STATE-CURRENT.md b/STATE-CURRENT.md
index 954d1d9..0289f77 100644
--- a/STATE-CURRENT.md
+++ b/STATE-CURRENT.md
@@ -1,26 +1,32 @@
 # Open-IOV Current State
 
-> **Snapshot: 2026-10-28 ~23:30 (the guest-corruption panic class is
-> root-caused and fixed — an r254-era ledger parity store clobbered the
-> per-page copy landings and wrote client result data into reused guest
-> pages, killing the guest kernel in the nvidia channel teardown; r627
-> guards it, five consecutive boots clean, and the best battery yet is
-> 11/15 with zero hangs (mail, matmul, saxpy, strided, math, reduce,
-> atomics, multikernel, vector_add, smiley, inplace_scale green). Launch
-> p50 ~650 ms (below the 684 ms baseline); the held-chain stall class
-> fixed; a refused launch now surfaces a CUDA error instead of spinning
-> forever. r632 serves unresolved operand pages from the VA shadow lane to
-> close the red-draw chain (walk=none -> H2D shadow -> fill fail-close ->
-> degenerate refusal -> synthetic fault); the remaining top blockers are
-> the release-target resolver (`release0 could not target the guest page`
-> with pins present) and the deterministic wrongness class (streams2 /
-> streams_events / memset2d / roundtrip). GL runs on the guest GPU (next
-> wall = the FBO class); the Looking Glass frame path is proven end-to-end
-> (guest CUDA render -> KVMFR ivshmem -> host PNG frame); two guests with
-> 512M + 1GiB emulated VRAM coexist at boot level; the 0.9.9 release-preview
-> demo video v1 is recorded and synced to files.vgpu.io. Frontier =
-> release-target + wrongness + repeat-run degradation, then two-guest
-> concurrent CUDA, GZDOOM (GL/Vulkan), Windows guests).**
+> **Snapshot: 2026-10-24 ~18:45 (the r632 first-client hang is
+> root-caused and fixed — a held GR launch's push-level release records are
+> per-decode state and the two hold paths dropped them at the pass
+> boundary, so the eventual forward engaged the release hold empty and the
+> client's tracking word never advanced; r633 parks the records with the
+> launch and delivers them on the forward. Mail is green on two consecutive
+> fresh boots (`VADD bad=0 checksum=12204516.000000`), and the first
+> zero-failure battery landed (r633b: 9 pass, 0 fail, 1 hang — streams2
+> mid-battery). The release-target question is answered: the
+> `release0 could not target the guest page` redirect is the deliberate
+> `gsp_phys_rmcall_gr_rel_mod=1` default, and the release page resolves
+> (`rel_hpa=0x2fc495000`, `map_ret=0`); a live probe module confirms the
+> GPA->HPA path. The r632 synthetic shadow caps are gated (anchor + 
+> per-episode budgets; shadow-table peak 2048/8192 vs 8192/8192 full) and
+> the r631 math red draw is green (`badf=0 badd=0 badi=0`). The remaining
+> top blocker is the deterministic wrongness class (streams2 / 
+> streams_events / memset2d / roundtrip) — traced to the per-client operand
+> resolution shortfall: when the guest scanner's kcore walks miss a
+> client's device VAs (`sems=1/7`), the fill drops its argument bases and
+> the engine runs with zero operands. The mid-battery hangs (reduce,
+> streams2) share that same resolution variable. GL runs on the guest GPU
+> (next wall = the FBO class); the Looking Glass frame path is proven
+> end-to-end (guest CUDA render -> KVMFR ivshmem -> host PNG frame); two
+> guests with 512M + 1GiB emulated VRAM coexist at boot level; the 0.9.9
+> release-preview demo video v1 is recorded and synced to files.vgpu.io.
+> Frontier = operand resolution + wrongness, then 15/15 + soak, events A/B,
+> GZDOOM (GL/Vulkan), two-guest concurrent CUDA, Windows guests).**
 > This is a dated public
 > status page, not live state; it is refreshed on every progress check. Live
 > working notes are maintained outside this repository; the public