STATE-CURRENT: 2026-10-20 evening snapshot - pin-wins corruption fix (vector_add green), multi-tenant live, battery frontier (multi-pass content + streams2 ordering)

1 files changed, 31 insertions, 4 deletions

diff --git a/STATE-CURRENT.md b/STATE-CURRENT.md
index a335ac9..27295df 100644
--- a/STATE-CURRENT.md
+++ b/STATE-CURRENT.md
@@ -1,9 +1,12 @@
 # Open-IOV Current State
 
-> **Snapshot: 2026-10-20 ~05:30 (boot lottery root-caused and fixed - the
-> status-queue SWAP_RX consumption cursor; guest CUDA kernels green end-to-end
-> on fresh boots: `victory_mail` / `victory_matmul` / transformer; demo VM live
-> on kernel 6.8.0-147).**
+> **Snapshot: 2026-10-20 ~20:00 (two more fixes landed: the SWAP_RX cursor
+> and the pin-wins ledger divergence that cured a guest-kernel-corruption
+> panic; guest CUDA kernels green on fresh boots - `victory_mail`,
+> `victory_matmul` (first-run flake), transformer, `vector_add` (1M,
+> `bad=0`), `vecadd_loop` (100 launches); two guests with two emulated VRAM
+> sizes (512M + 1GiB) coexist live; frontier = the multi-pass content class
+> and the streams2 launch-order wait).**
 > 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
@@ -336,6 +339,30 @@ isolation, performance, portability).
         boot-lottery re-measure over fresh boots, the full battery + soak, two guests,
         multi-mdev and the VRAM sizes. Host clean, GPU green, no reboots; demo VM live
         with the three green kernels.
+       **Update 2026-10-20 ~20:00 (pin-wins corruption fix; multi-tenant live; battery frontier):**
+        a second, independent fix landed after the SWAP_RX cursor: the emulation's
+        write-side ledger could redirect a copy to the page an earlier write landed
+        on even when the guest had already remapped or freed that VA (4448 such
+        divergences in the failing run), so guest-kernel memory could receive client
+        copy data - observed as an RM object's pointer field holding client float
+        data, a free-path traversal faulting, and a guest panic
+        ("Attempted to kill init") on the `vector_add` client. With a pin-backed
+        translation (guest pagemap truth) now winning the divergence and the ledger
+        re-homing after the write (`720d3f5f`): `vector_add` cold AND warm run
+        `bad=0` + `STATUS OK` and the guest survives; the cold-run content gap
+        class is cured with it. Battery on fresh boots: `victory_mail`,
+        `vecadd_loop` (100 launches), `victory_matmul` (a first-run all-bad flake,
+        green on immediate retry), `victory_strided`, `victory_math`,
+        `vector_add`, and a transformer kernel (`dh=256`/`FFN4` `bad=0`) are green;
+        streams2's ordering class is root-caused (core CUDA starts compute-channel
+        pushes with a C56F host-semaphore acquire that the decoder ignored, so a
+        D2H readback ran before the scale launch it waits for) and the multi-pass
+        content class is the remaining frontier (multi-launch/accumulating kernels
+        wrong; `victory_reduce` is exactly 2x - the engine never wrote on five
+        launch-shaped pushes of a one-launch client). Multi-tenant: two mediated
+        devices (512M + 1GiB) and two guests coexist; guest B reports its 1GiB
+        VRAM with `nvidia-smi` green; guest-B CUDA awaits its own pin stream. Host
+        clean, no reboots.
 - **Guest frontier: FIRST GREEN END-TO-END GUEST CUDA, NOW UNDER HARDENING
   (2026-10-04 ~16:20; hardening 2026-10-05 overnight).** The emulation-only
   ("no-claim") campaign runs an unmodified guest CUDA program to completion