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

diff --git a/debug/risc-v-gsp-rm-vm/docs/01-DESIGN.md b/debug/risc-v-gsp-rm-vm/docs/01-DESIGN.md
index c5de2da..034f87c 100644
--- a/debug/risc-v-gsp-rm-vm/docs/01-DESIGN.md
+++ b/debug/risc-v-gsp-rm-vm/docs/01-DESIGN.md
@@ -1,4 +1,4 @@
-# 01 — green-eye design
+# 01 — risc-v-gsp-rm-debugger design
 
 > **# TOOL IN DEVELOPMENT - NOT READY YET!** See 00 for status.
 
@@ -73,7 +73,7 @@ the plugin layer, not the transport.
   same return address are queued (LIFO). Tail calls and asynchronous
   interrupts are not tracked — documented limitation.
 * **Watchpoints**: `Z2/Z3/Z4` (write/read/access). QEMU stops *at* the
-  accessing instruction, so green-eye temporarily clears the watch, steps one
+  accessing instruction, so risc-v-gsp-rm-debugger temporarily clears the watch, steps one
   instruction, and re-arms it. Without this the target livelocks on the same
   store.
 * **Stop dispatch**: every stop reads the register file, resolves the PC to a
@@ -144,7 +144,7 @@ declarative so they can come from a Ghidra type export or a plugin later.
 * The **kernel fast path** passes `-kernel <elf>`; QEMU loads segments and
   sets PC.
 * The **probe path** passes each PT_LOAD segment as a raw loader device and
-  green-eye sets PC through the gdbstub — this lets a firmware linked for GPU
+  risc-v-gsp-rm-debugger sets PC through the gdbstub — this lets a firmware linked for GPU
   physical addresses be relocated into RAM for observation.
 * A **custom simulator** can be added as a session backend later (roadmap,
   not v0.1) because `Session` only assumes the RSP-like operations.