docs: refresh current-state snapshot (20/20 GR releases land; failure not a UVM wait)

1 files changed, 14 insertions, 11 deletions

diff --git a/STATE-CURRENT.md b/STATE-CURRENT.md
index 67b3d11..0a5e30e 100644
--- a/STATE-CURRENT.md
+++ b/STATE-CURRENT.md
@@ -1,6 +1,6 @@
 # Open-IOV Current State
 
-> **Snapshot: 2026-09-29 23:57.** This is a dated public status page, not live
+> **Snapshot: 2026-09-30 00:40.** 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 known-knowns/unknowns document
 > is authoritative here:
@@ -66,16 +66,19 @@ chain succeeds.
   every consumed engine submission now delivers the incrementing release, and
   the pool value advances within a second (previously it stalled until the
   deadline). Registration no longer dominates the run.
-- **New frontier: the guest's own GSP health check**: a second after the
-  compute-channel phase the guest driver runs a GSP health check while one of
-  its resource-manager replies is pending, then rolls the context back. Two
-  suspects under test: reply-path latency now that releases are applied at a
-  high rate, and a reply whose parameter size is not canonical (the guest
-  logs `NV_ERR_INVALID_PARAMETER` on its reply-cache path).
-- Active work: an extended debug loop on the health-check failure - more
-  one-shot breakpoint tooling and fresh failure-instant guest/host snapshots
-  are being produced, with kernel and tool edits still in the tree awaiting
-  the next build/commit.
+- **A second release-path drop is fixed**: some compute-channel releases were
+  decoded through the generic translation map and silently dropped; routing
+  them through the exact counter slot makes **all 20/20 channel releases
+  land** (verified on live boots). The failure is unchanged by that fix, so
+  the counter path was not the gate.
+- **The remaining wall is a silent post-compute-phase rollback**: about a
+  second after the performance-boost control the guest tears down the 20
+  channels and returns the context error - while every resource-manager
+  control was answered successfully and the guest kernel logs no error. The
+  profile points at the rollback's RPC frees with the GSP health check
+  running inside the RPC poll.
+- Active work: kernel-return probes on the UVM channel lifecycle plus
+  failure-instant trace capture, to name the event the rollback waits on.
 - Guest health note: agent/SSH timeouts during a run are usually guest-agent
   starvation and recover when the client stops; one hard wedge occurred only
   when pushed memsets were re-enabled, so bulk pushed operations stay disabled