debug: risc-v-gsp-rm-debugger final pass - remove in-development notices, complete rename, adversarial-review fixes

Remove the '# TOOL IN DEVELOPMENT - NOT READY YET!' notices from the tool docs/README/scripts and the project docs; record the removal (2026-10-02) against the tool audit (debug/risc-v-gsp-rm-vm/docs/27-TOOL-AUDIT.md), the 194-test suite and the value-validation demos (docs/25-VALUE-VALIDATION.md).

Complete the cosmetic rename to risc-v-gsp-rm-debugger in user-facing prose and commands (launcher, roadmap, docs); internal greeneye package and code identifiers unchanged.

Adversarial-review fixes: deterministic control-discovery sweep (flaky test root-caused), UUID session dirs + atomic JSON writes for concurrent runs, Ghidra bridge loopback enforcement and clean shutdown, fp register restore in Session.call, version_diff --dry-run, 30 s interrupt budget, dry-run non-destructiveness verified.

Docs: flag-removal records, link fixes, command/flag corrections (fdematch arity, port_new_device --out, trace filename), F2 orchestration note in future-eng-ops; STATE-CURRENT status refreshed.

1 files changed, 7 insertions, 4 deletions

diff --git a/STATE-CURRENT.md b/STATE-CURRENT.md
index 9078550..69f5574 100644
--- a/STATE-CURRENT.md
+++ b/STATE-CURRENT.md
@@ -133,8 +133,8 @@ chain succeeds.
   with a GDB stub and adds Frida-like runtime inspection, a scripting/plugin
   API and a Ghidra bridge for GSP-RM runtime-memory analysis and
   emulation-accuracy measurement. It is debug tooling only (no product code
-  changes) and is explicitly marked `# TOOL IN DEVELOPMENT - NOT READY YET!`;
-  see
+  changes); the in-development notices were removed 2026-10-02 after the tool
+  audit and value validation; see
   [`docs/05-operations/03-risc-v-gsp-rm-vm.md`](docs/05-operations/03-risc-v-gsp-rm-vm.md).
 - **P6a trigger-path fix landed (2026-10-02 07:10).** The debug copy
   triggers now resolve the guest page host-physical address at trigger time
@@ -808,7 +808,10 @@ Experimental developer tooling (not part of the product path): **risc-v-gsp-rm-d
 (`debug/risc-v-gsp-rm-vm/`) boots GSP/uproc firmware in a RISC-V QEMU VM with
 a GDB stub and adds Frida-like runtime inspection, a scripting/plugin API and
 a Ghidra bridge for GSP-RM runtime-memory analysis and emulation-accuracy
-measurement. It is marked `# TOOL IN DEVELOPMENT - NOT READY YET!`; see
+measurement. Status is tracked by the tool audit
+(`debug/risc-v-gsp-rm-vm/docs/27-TOOL-AUDIT.md`); the in-development notices
+were removed 2026-10-02 after the 194-test suite and end-to-end value
+demonstrations (`debug/risc-v-gsp-rm-vm/docs/25-VALUE-VALIDATION.md`); see
 [`docs/05-operations/03-risc-v-gsp-rm-vm.md`](docs/05-operations/03-risc-v-gsp-rm-vm.md).
 
 | Wall | Fix |
@@ -897,7 +900,7 @@ device.
 - [`docs/03-architecture/08-physical-gpu-integration.md`](docs/03-architecture/08-physical-gpu-integration.md) - chosen execution backend (module-owned GPU + real GSP session)
 - [`docs/03-architecture/09-full-system-picture.md`](docs/03-architecture/09-full-system-picture.md) - visual end-to-end system map with status tags
 - [`docs/03-architecture/10-interaction-and-scheduling.md`](docs/03-architecture/10-interaction-and-scheduling.md) - cross-component interaction, queues, interrupts, scheduling detail
-- [`docs/05-operations/03-risc-v-gsp-rm-vm.md`](docs/05-operations/03-risc-v-gsp-rm-vm.md) - risc-v-gsp-rm-debugger GSP RISC-V VM runtime analysis (`# TOOL IN DEVELOPMENT - NOT READY YET!`)
+- [`docs/05-operations/03-risc-v-gsp-rm-vm.md`](docs/05-operations/03-risc-v-gsp-rm-vm.md) - risc-v-gsp-rm-debugger GSP RISC-V VM runtime analysis (status: docs/27 tool audit, docs/25 value validation)
 
 ---