rename (cosmetic): green-eye -> risc-v-gsp-rm-debugger in user-facing names, docs, CLI, launcher and CI workflow; internal greeneye package/module identifiers unchanged (includes in-flight greeneye module edits present in the tree)

1 files changed, 12 insertions, 12 deletions

diff --git a/docs/05-operations/03-risc-v-gsp-rm-vm.md b/docs/05-operations/03-risc-v-gsp-rm-vm.md
index c21124b..773006d 100644
--- a/docs/05-operations/03-risc-v-gsp-rm-vm.md
+++ b/docs/05-operations/03-risc-v-gsp-rm-vm.md
@@ -1,4 +1,4 @@
-# GSP in a RISC-V VM — green-eye (experimental)
+# GSP in a RISC-V VM — risc-v-gsp-rm-debugger (experimental)
 
 > **# TOOL IN DEVELOPMENT - NOT READY YET!**
 > This is experimental developer tooling. It is not part of the shipped
@@ -10,7 +10,7 @@
 
 ## 1. What it is
 
-**green-eye** runs GSP/uproc firmware in a `qemu-system-riscv64` VM and makes
+**risc-v-gsp-rm-debugger** runs GSP/uproc firmware in a `qemu-system-riscv64` VM and makes
 its runtime behaviour inspectable with Frida-like primitives:
 
 * breakpoints and enter/leave hooks (RV64 ABI aware),
@@ -48,7 +48,7 @@ accuracy, portability playbooks, roadmap) is under
 * **Not a timing model.** Do not infer latency or concurrency behaviour from
   it; its in-scope conclusions are execution flow and memory side effects.
 * **Not a replacement for Ghidra or the guest diagnostics.** Ghidra answers
-  *what is the code*; green-eye answers *what did it do*. The guest driver
+  *what is the code*; risc-v-gsp-rm-debugger answers *what did it do*. The guest driver
   remains the oracle for guest-side behaviour.
 
 ## 3. Where it fits
@@ -58,10 +58,10 @@ accuracy, portability playbooks, roadmap) is under
 | Static | Ghidra corpus (`userspace/cuda`, `tools/ghidra`) | what is the code? |
 | Guest driver | `tools/guest-diag/`, ptrace tracer | what did the driver request? |
 | Physical backend | supervised physical cycles, module logs | what did real silicon/the real GSP-RM do? |
-| **Firmware runtime (this)** | **green-eye** | **what does the firmware server do, repeatably and safely?** |
+| **Firmware runtime (this)** | **risc-v-gsp-rm-debugger** | **what does the firmware server do, repeatably and safely?** |
 
 The intended measurement loop is: capture the real backend's RPC behaviour,
-run the same stimulus in green-eye, and compare the recorded sessions
+run the same stimulus in risc-v-gsp-rm-debugger, and compare the recorded sessions
 (`greeneye compare`) with the accuracy metrics defined in the tool's
 `docs/06-ACCURACY.md`. Portability runs (new GSP, new device, GB10-class
 architecture) are described in `docs/07-PORTABILITY-PLAYBOOKS.md`.
@@ -72,13 +72,13 @@ From the repository root:
 
 ```bash
 cd debug/risc-v-gsp-rm-vm
-./greeneye.sh info                 # environment check (QEMU, toolchain)
+./risc-v-gsp-rm-debugger.sh info                 # environment check (QEMU, toolchain)
 make demo sdk                      # build the demo uproc and the injection SDK
-./greeneye.sh demo                 # canned instrumentation pass; records a session
-./greeneye.sh analyze dumps/<session>
-./greeneye.sh probe                # real GSP image: report the first divergence
-./greeneye.sh inject               # load and invoke an injected service
-./greeneye.sh ghidra               # serve the session to GhidraScripts
+./risc-v-gsp-rm-debugger.sh demo                 # canned instrumentation pass; records a session
+./risc-v-gsp-rm-debugger.sh analyze dumps/<session>
+./risc-v-gsp-rm-debugger.sh probe                # real GSP image: report the first divergence
+./risc-v-gsp-rm-debugger.sh inject               # load and invoke an injected service
+./risc-v-gsp-rm-debugger.sh ghidra               # serve the session to GhidraScripts
 ```
 
 Requirements: `qemu-system-riscv64` (Ubuntu `qemu-system-misc`), Python 3.10+
@@ -96,7 +96,7 @@ real-firmware first-fault probe, and the TCG full-memory trace plugin. Not
 implemented: device model (R1), custom simulator (R2), MCP plugin (R3) — all
 roadmap. The long-term program (adversarial navigation, adjacent
 microcontrollers, custom simulator, Verilog soft-core, agentic platform) is
-documented in `debug/risc-v-gsp-rm-vm/GREEN-EYE-ROADMAP.md`.
+documented in `debug/risc-v-gsp-rm-vm/RISC-V-GSP-RM-DEBUGGER-ROADMAP.md`.
 
 ## 6. When the development flag can be removed