STATE-CURRENT: runtime bring-up started; runtime buffer translations are the wall

- harness runs nvidia-smi and a static-runtime vectorAdd-style client
- page-table walk succeeds at scale; larger runtime buffers still fail
  translation (host copies report missing entries)
- frontier/active-work notes updated

1 files changed, 10 insertions, 7 deletions

diff --git a/STATE-CURRENT.md b/STATE-CURRENT.md
index 5481313..7fe0291 100644
--- a/STATE-CURRENT.md
+++ b/STATE-CURRENT.md
@@ -1,6 +1,6 @@
 # Open-IOV Current State
 
-> **Snapshot: 2026-09-30 08:58.** This is a dated public status page, not live
+> **Snapshot: 2026-09-30 10:01.** 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:
@@ -53,10 +53,12 @@ chain succeeds.
   class transfer bound on a compute channel whose work was denied by the
   engine-type gate; trusted host-injected pushes may now execute copy-engine
   work as well).
-- **Next: run a real CUDA workload in the guest** (`nvidia-smi`, a
-  `vectorAdd`-style kernel launch) and iterate on whatever the runtime path
-  asks for - this moves the frontier toward kernel execution, which still
-  requires the execution backend.
+- **Runtime bring-up has started**: the harness now runs `nvidia-smi` and a
+  static-runtime `vectorAdd`-style client. The page-table walk resolves at
+  scale (thousands of successful walks per run), but the runtime's larger
+  buffers currently fail translation - host-side copies of 1 MB and smaller
+  report a missing-entry error on those virtual addresses. That translation
+  class is the new wall.
 - Recap of the fixes behind this point: all 20/20 compute-channel releases
   land (three decode paths routed to the exact counter slot); registration
   delivers the incrementing tracking release for every consumed submission;
@@ -64,8 +66,9 @@ chain succeeds.
   the copy-engine decoder consults pinned translations before the scanned
   map, so every push-data operation executes (`memset=19473`, `ringops=10551`
   live).
-- Active work: run a real CUDA workload in the guest (`nvidia-smi`, a kernel
-  launch) and iterate on the runtime path; iterate with a fresh boot per run.
+- Active work: chase the runtime buffers' translations (the kernel-VA class),
+  with a CPU monitor now flagging kernel-VA translation failures; iterate on
+  the runtime path with one fresh boot per run.
 - Observability: a size-keyed copy watch, a VRAM shadow dump/search, and an
   operation log are now module parameters, and the test's output survives
   guest-agent stalls via the serial console.