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

diff --git a/debug/risc-v-gsp-rm-vm/docs/09-GSP-FIRMWARE-NOTES.md b/debug/risc-v-gsp-rm-vm/docs/09-GSP-FIRMWARE-NOTES.md
index 216bf93..b930cb9 100644
--- a/debug/risc-v-gsp-rm-vm/docs/09-GSP-FIRMWARE-NOTES.md
+++ b/debug/risc-v-gsp-rm-vm/docs/09-GSP-FIRMWARE-NOTES.md
@@ -1,4 +1,4 @@
-# 09 — GSP/uproc firmware notes used by green-eye
+# 09 — GSP/uproc firmware notes used by risc-v-gsp-rm-debugger
 
 > **# TOOL IN DEVELOPMENT - NOT READY YET!** See 00 for status.
 > Exact local-source provenance is recorded in the local task record; this
@@ -55,7 +55,7 @@ Two OS layers appear in the vendor snapshots:
   paid for. This is the direction the GSP stack evolves toward.
 
 **Implication for the simulator:** the scheduler is not the interesting part
-for RPC accuracy; the task/dispatcher semantics are. Green-eye's demo mirrors
+for RPC accuracy; the task/dispatcher semantics are. Risc-V GSP-RM debugger's demo mirrors
 that shape (mailbox → dispatcher → handler → counters), and a rehost shim
 should stub the scheduler while keeping task entry points and message
 handling real.
@@ -73,7 +73,7 @@ handling real.
   a live GSP with a debug command (`nvwatch …`) for bring-up.
 
 These models matter for portability: a new architecture may change the
-partition layout or boot order, and green-eye's probe is the quickest way to
+partition layout or boot order, and risc-v-gsp-rm-debugger's probe is the quickest way to
 see the new first-touch sequence before a device model exists.
 
 ## 5. Memory, DMA and registers
@@ -84,14 +84,14 @@ see the new first-touch sequence before a device model exists.
 * The engines exchange data over **CSB/TRANSCOM windows and mailboxes** with
   DMA into host/FB memory; the physical backend work in Open-IOV already
   models the message-queue side (status/command queues, doorbells) — that is
-  the layer green-eye can emulate first when R1 lands.
+  the layer risc-v-gsp-rm-debugger can emulate first when R1 lands.
 * The GSP kernel's start path receives its memory permissions as boot args
   from the bootloader rather than discovering them, which is why a
   re-host should pass the same structure rather than re-derive it.
 
-## 6. How green-eye models this today (and honestly, does not)
+## 6. How risc-v-gsp-rm-debugger models this today (and honestly, does not)
 
-| Firmware aspect | green-eye v0.1 |
+| Firmware aspect | risc-v-gsp-rm-debugger v0.1 |
 |---|---|
 | Task/dispatcher/state-machine logic | modelled faithfully by the demo and by rehosted code |
 | RPC handler input/output behaviour | observable and recordable; schemas decode structures |