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

diff --git a/debug/risc-v-gsp-rm-vm/docs/26-ARCHITECTURE.md b/debug/risc-v-gsp-rm-vm/docs/26-ARCHITECTURE.md
index ab8414a..d8c30dd 100644
--- a/debug/risc-v-gsp-rm-vm/docs/26-ARCHITECTURE.md
+++ b/debug/risc-v-gsp-rm-vm/docs/26-ARCHITECTURE.md
@@ -1,14 +1,14 @@
-# 26 — green-eye architecture: full picture, workflow and API surfaces
+# 26 — risc-v-gsp-rm-debugger architecture: full picture, workflow and API surfaces
 
 > **# TOOL IN DEVELOPMENT - NOT READY YET!**
-> The architecture map for the green-eye suite: how the pieces fit, which
+> The architecture map for the risc-v-gsp-rm-debugger suite: how the pieces fit, which
 > surface to call, and which document specifies each part. Every claim here is
 > implemented in the tree or explicitly marked as a gated roadmap design.
 > Development-only: never shipped, never a driver dependency, never in a guest.
 
-## 1. What green-eye is (and is not)
+## 1. What risc-v-gsp-rm-debugger is (and is not)
 
-green-eye runs GSP/uproc firmware in a controllable machine, observes it with
+risc-v-gsp-rm-debugger runs GSP/uproc firmware in a controllable machine, observes it with
 Frida-like primitives, records a durable session, changes the machine's inputs
 (including injected code), and compares runs as evidence for `open-iov-vfio`
 emulation changes.
@@ -224,7 +224,7 @@ sequenceDiagram
 | `greeneye.ghidra.export_hits` | session hits → `addr<TAB>hits<TAB>symbol<TAB>annotation` | 05 |
 | `ExportForGreenEye.java` | Ghidra → `addr<TAB>name<TAB>size` TSV | 05 |
 | `MarkGreenEyeHits.java` | annotate functions with runtime hits + bookmarks | 05 |
-| `GreenEyeControl.java` + `greeneye.sh ghidra` | drive a live session from GhidraScripts over localhost JSON-lines | [13](13-GHIDRA-CONTROL.md) |
+| `GreenEyeControl.java` + `risc-v-gsp-rm-debugger.sh ghidra` | drive a live session from GhidraScripts over localhost JSON-lines | [13](13-GHIDRA-CONTROL.md) |
 
 Bridge commands: `ping`, `info`, `resolve`, `bp_set`, `bp_clear`, `bp_list`,
 `watch_set`, `run_until`, `run`, `step`, `read_mem`, `write_mem`, `read_reg`,
@@ -343,7 +343,7 @@ The canonical loop (H4.5, 06 §5, 07 P4, 25 §7). Each stage names its gate.
 | 5. Compare | `compare` against a reference (old firmware, hardware/VFIO capture, self-diff) | deltas explained symbolically; self-diff is zero | unexplained hit/watch/write delta → investigate first |
 | 6. Decide | fill M1–M6 with the reference method (06 §5); mutation/triage for error paths | metric table improves or stays equal | metric claimed without a reference capture |
 | 7. Implement | change `open-iov-vfio` (never the simulator for a product fix); keep the stimulus | physical confirmation for behaviour changes (06 §6, 14 §7) | product change from a simulator-only observation |
-| 8. Regression | re-run step 3 with an unchanged stimulus; golden sessions/CI (`make test`, `greeneye.yml`) | profile improves or stays equal; CI green | regression → revert and re-derive |
+| 8. Regression | re-run step 3 with an unchanged stimulus; golden sessions/CI (`make test`, `risc-v-gsp-rm-debugger.yml`) | profile improves or stays equal; CI green | regression → revert and re-derive |
 
 ```mermaid
 flowchart LR
@@ -358,12 +358,12 @@ flowchart LR
 ```
 
 OODA compression evidence (analog, measured) is in 25 §7: hardware cycles are
-minutes and campaigns hours/days; the green-eye path for the same question
+minutes and campaigns hours/days; the risc-v-gsp-rm-debugger path for the same question
 class is sub-second to seconds plus scripting.
 
 ## 12. API surfaces by tool
 
-### 12.1 CLI (`greeneye.sh`, `greeneye/cli.py`; usage in [02](02-USAGE.md))
+### 12.1 CLI (`risc-v-gsp-rm-debugger.sh`, `greeneye/cli.py`; usage in [02](02-USAGE.md))
 
 | Command | Purpose | Not for |
 |---|---|---|
@@ -447,7 +447,7 @@ dispatch (01, 03); §4 backends (01 §8, 16 §4–5); §5 recording (01 §6, 09,
 §6, 16 §10, 17 §5); §6 injection (11, 12); §7 Ghidra (05, 13); §8 MCP (20);
 §9 harness (18, 19, 21, 28, 29); §10 device map (24, 16 §7); §11 OODA (06, 07 P4, 25
 §7). Roadmap keys: R3 = MCP (08), R5 = mutation (18), R6 = multi-version (18,
-21), H1.3 = RM service injection (GREEN-EYE-ROADMAP), H2.2 = QEMU device
+21), H1.3 = RM service injection (RISC-V-GSP-RM-DEBUGGER-ROADMAP), H2.2 = QEMU device
 model, H3/M1–M6 = native simulator (16), H4 = adversarial navigation (14),
 H7 = agentic platform (15, 20).