STATE-CURRENT: reliability wave m160-m162 + harness fixes snapshot (verified greens, retry recovery, cascade root fixed, remaining classes)

1 files changed, 17 insertions, 0 deletions

diff --git a/STATE-CURRENT.md b/STATE-CURRENT.md
index 9bfbff5..15e23f3 100644
--- a/STATE-CURRENT.md
+++ b/STATE-CURRENT.md
@@ -253,6 +253,23 @@ isolation, performance, portability).
        contamination demonstrated live) and needs the per-guest ownership rework
        (owner-tagged pin/map/pending lookups) before any dual-CUDA claim. No reboot;
        host GPU green; both guests left running.
+      **Update 2026-10-16 ~18:40 (reliability wave m160-m162 + harness fixes; verified battery, no reboots):**
+       five cycles (r163-r167) landed and verified the bounds of the earlier "STATUS FAIL /
+       freeze" repro. Fixed and live-verified across boots: `victory_mail` and
+       `victory_matmul` (repeats), `smiley`, `vector_add`, `victory_math`, `victory_strided`
+       and `vecadd_loop` (100 launches) all green on the physical engine; the acked-no-execute
+       class is recovered by outcome retries (fresh release-word ack, fresh inline-QMD bank +
+       rebuilt method block: a launch with zero engine writes recovered on retry 2 with its
+       full 1024-page output). A hardware fetch witness (QMD sentinel) now distinguishes
+       fetched-vs-not in every retry log. The post-teardown DEVICE-freeze cascade was rooted in
+       the pin-feeder tooling: blocked guest-trace reads over the guest agent stopped the
+       pool/tracker pin flow after ~5 client cycles and every later client froze in
+       `uvm_tracker_wait`; the trace reads are now remotely timed and SSH-preferred, and the
+       demand-pin content resolver searches a learned per-allocation offset. Remaining
+       characterized gaps (evidence in the private handoff): a fetched-but-not-executed launch
+       class, a no-ack front-end stall class, the multi-buffer streams2 reloc/copy-out
+       mismatch, and the 8 MB CE roundtrip demand-resolution crawl (scanner fix landed,
+       retest pending).
 - **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