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, 7 deletions

diff --git a/docs/eng-ops.md b/docs/eng-ops.md
index 4dd450e..218b8cd 100644
--- a/docs/eng-ops.md
+++ b/docs/eng-ops.md
@@ -16,7 +16,7 @@ binds both: evidence or it did not happen ([`onboarding-and-standards.md`](07-de
 | Admission, extension, redesign, trialing and retirement of tools | Architecture ([`03-architecture/01-system-overview.md`](03-architecture/01-system-overview.md)); tool manuals: CUDA ([`../userspace/cuda/READ-ME-FIRST.md`](../userspace/cuda/READ-ME-FIRST.md)), risc-v-gsp-rm-debugger ([`26-ARCHITECTURE.md`](../debug/risc-v-gsp-rm-vm/docs/26-ARCHITECTURE.md), [user guide](../debug/risc-v-gsp-rm-vm/docs/02-USAGE.md), [scripting](../debug/risc-v-gsp-rm-vm/docs/03-SCRIPTING.md)), rmharness ([`README`](../debug/risc-v-gsp-rm-vm/rmharness/README.md)) |
 | Which tool applies in which loop; automation and packaging | Accuracy M1–M6 ([`06-ACCURACY.md`](../debug/risc-v-gsp-rm-vm/docs/06-ACCURACY.md)); performance method ([`05-operations/01`](05-operations/01-performance-correctness-security.md) §3); version discipline ([`05-operations/02`](05-operations/02-debugging-and-maintenance-workflows.md) §4) |
 | Evidence bundles, version-span gates, frontier admission | Per-tool docs and the periodic [`27-TOOL-AUDIT.md`](../debug/risc-v-gsp-rm-vm/docs/27-TOOL-AUDIT.md) |
-| Live physical-backend engineering operations: supervised-cycle mechanics, parameter gates, debugfs controls and the hazard register (**Part II** below) | Physical-backend architecture ([`03-architecture/08`](03-architecture/08-physical-gpu-integration.md), [`03-architecture/11`](03-architecture/11-physical-backend-guest-wiring.md)); defensive/incident scenarios ([`RUNBOOK.md`](RUNBOOK.md)); current frontier ([`STATE-CURRENT.md`](STATE-CURRENT.md)) |
+| Live physical-backend engineering operations: supervised-cycle mechanics, parameter gates, debugfs controls and the hazard register (**Part II** below) | Physical-backend architecture ([`03-architecture/08`](03-architecture/08-physical-gpu-integration.md), [`03-architecture/11`](03-architecture/11-physical-backend-guest-wiring.md)); defensive/incident scenarios ([`RUNBOOK.md`](RUNBOOK.md)); current frontier ([`STATE-CURRENT.md`](../STATE-CURRENT.md)) |
 
 **Explicitly out of scope.** (1) Security claims: the simulator and its device
 maps are study environments, never a confidentiality or isolation boundary
@@ -175,7 +175,7 @@ the audit is the periodic reconciliation.
 | Admitted family | Loop | Value evidence (current) | Review / retire trigger |
 |---|---|---|---|
 | Ghidra corpora + scripts (`tools/ghidra`, `userspace/cuda/tools`) | RE, portability | docs 05/07; `diff_corpus`, name map | corpus diff no longer changes port class |
-| risc-v-gsp-rm-debugger core + session format | dynamic-RE | `docs/25` s01–s10; 155-test suite | format unused by any loop |
+| risc-v-gsp-rm-debugger core + session format | dynamic-RE | `docs/25` s01–s10; 194-test suite | format unused by any loop |
 | Harness (`version_diff`, matrix, mutation, discovery, reach, `ci_release`) | portability, adversarial | docs 18/19/21; deterministic replay tests | a report is never attached to a change |
 | Injection SDK + demo uproc | dynamic-RE | docs 11/12; s06 | prototypes stop using it |
 | Ghidra bridges (in/out) | RE | docs 05/13 | static/dynamic join replaced |
@@ -227,7 +227,7 @@ flowchart LR
   IMP --> IDX["names.tsv, decompiled_index.tsv, callgraph.tsv"]
   IDX --> DIFF["corpus diff / fdematch / RPC dispatch diff"]
   DIFF --> HYP["Hypothesis: functions, tables, layouts"]
-  HYP --> SYM["greeneye symbols export (bias recorded)"]
+  HYP --> SYM["./risc-v-gsp-rm-debugger.sh symbols export (bias recorded)"]
   SYM --> DYN["dynamic loop"]
   DYN -->|"hits, watch PCs, fault PCs"| HYP
 ```
@@ -502,7 +502,7 @@ that cannot state a benefit is rejected as overhead.
 | Date | Revision | Purpose / scope | Benefit | Evidence |
 |---|---|---|---|---|
 | 2026-10-02 | v1 | Establish the admission rule, value axes, decision framework, workflow maps, automation, packaging, frontier gates and review discipline | Tooling decisions become auditable, measurable and reversible; no tool without an evaluation | This document plus linked tool docs and the [`docs/25`](../debug/risc-v-gsp-rm-vm/docs/25-VALUE-VALIDATION.md) baselines |
-| 2026-10-02 | v2 (Part II) | Add the live physical-backend operations: hard rules and scope, build/load order and the full `gsp_phys_*` parameter matrix, the routine supervised cycle with its clean-release checklist, the debugfs inventory and `gsp-phys-state` reference, the physical-backend scenario catalogue and hazard register, the OODA loop and the work-context/porting map | Physical-backend execution becomes auditable and fail-safe: one checklist, a named signal per failure, and no retry of a wedged path | Kernel sources cited per parameter and debugfs file; the current frontier in this document and [`STATE-CURRENT.md`](STATE-CURRENT.md) |
+| 2026-10-02 | v2 (Part II) | Add the live physical-backend operations: hard rules and scope, build/load order and the full `gsp_phys_*` parameter matrix, the routine supervised cycle with its clean-release checklist, the debugfs inventory and `gsp-phys-state` reference, the physical-backend scenario catalogue and hazard register, the OODA loop and the work-context/porting map | Physical-backend execution becomes auditable and fail-safe: one checklist, a named signal per failure, and no retry of a wedged path | Kernel sources cited per parameter and debugfs file; the current frontier in this document and [`STATE-CURRENT.md`](../STATE-CURRENT.md) |
 
 ```bash
 python3 scripts/check-docs-links.py                       # repo root
@@ -523,7 +523,7 @@ cd debug/risc-v-gsp-rm-vm && make demo sdk && make test   # tool claims
 > Part I (§§1–9) governs tooling admission, value measurement and retirement.
 > Defensive/incident scenarios are owned by [`RUNBOOK.md`](RUNBOOK.md) and are
 > cross-linked, not duplicated, here; the current frontier is
-> [`STATE-CURRENT.md`](STATE-CURRENT.md); the known unknowns are
+> [`STATE-CURRENT.md`](../STATE-CURRENT.md); the known unknowns are
 > [`04-implementation/01`](04-implementation/01-known-knowns-and-unknowns.md).
 > Everything in this part is supervised, bounded and fail-safe-first; nothing
 > here authorises unattended hardware work.
@@ -809,7 +809,7 @@ bump, device/ISA/ROM change, protected state, matrix/CI) are owned by
 | Portability (firmware, hardware, driver version, userspace version) | [`06-portability/*`](06-portability/hardware-software-matrix.md) and [`RUNBOOK.md`](RUNBOOK.md) S1–S10. |
 | Performance and correctness validation | [`05-operations/01`](05-operations/01-performance-correctness-security.md) (evaluation ladder, metrics, A/B method). |
 | Architecture of the backend and the guest wiring | [`03-architecture/08`](03-architecture/08-physical-gpu-integration.md), [`03-architecture/11`](03-architecture/11-physical-backend-guest-wiring.md). |
-| Current frontier and dated status | [`STATE-CURRENT.md`](STATE-CURRENT.md). |
+| Current frontier and dated status | [`STATE-CURRENT.md`](../STATE-CURRENT.md). |
 
 ### 14.2 Triage flow for a CUDA/userspace symptom
 
@@ -840,7 +840,7 @@ region up. The device is therefore parked in the **designed locked
 fail-safe** (module unloaded, GPU unbound, D0 locks held, WPR2 up) awaiting a
 supervised reboot; the promote path stays gated behind
 `gsp_phys_rmcall_gr_promote=0` until a bisected variant is proven. Live detail
-and evidence pointers: [`STATE-CURRENT.md`](STATE-CURRENT.md).
+and evidence pointers: [`STATE-CURRENT.md`](../STATE-CURRENT.md).
 
 <!-- change (2026-10-02): correct the porting/packaging tool section from
 planned interfaces that no longer match the landed scaffolds (docs 28/29) to