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

diff --git a/debug/risc-v-gsp-rm-vm/docs/11-GSP-RM-SERVICE-DEVELOPER-GUIDE.md b/debug/risc-v-gsp-rm-vm/docs/11-GSP-RM-SERVICE-DEVELOPER-GUIDE.md
index 6ba8d69..db5109c 100644
--- a/debug/risc-v-gsp-rm-vm/docs/11-GSP-RM-SERVICE-DEVELOPER-GUIDE.md
+++ b/debug/risc-v-gsp-rm-vm/docs/11-GSP-RM-SERVICE-DEVELOPER-GUIDE.md
@@ -9,13 +9,13 @@
 The GSP runs a resource manager (RM) as **services**: message handlers, state
 machines and engines that own objects (devices, address spaces, channels,
 memory, notifiers) and answer controls. Open-IOV emulates those services; the
-long-term goal of green-eye is to let a developer **write, inject, run and
+long-term goal of risc-v-gsp-rm-debugger is to let a developer **write, inject, run and
 debug their own versions of these services** before (or instead of) changing
 the product emulation.
 
 This guide teaches the loop on the demo uproc — which implements the same
 shape as a GSP service — and maps each step to the future GSP-RM work in
-[`GREEN-EYE-ROADMAP.md`](../GREEN-EYE-ROADMAP.md) H1.3.
+[`RISC-V-GSP-RM-DEBUGGER-ROADMAP.md`](../RISC-V-GSP-RM-DEBUGGER-ROADMAP.md) H1.3.
 
 ## 2. Service anatomy
 
@@ -62,7 +62,7 @@ entry points, which is also the interception point).
 ## 4. Injecting and invoking
 
 ```bash
-./greeneye.sh inject --service sdk/build/injected_demo.elf \
+./risc-v-gsp-rm-debugger.sh inject --service sdk/build/injected_demo.elf \
     --cmd 1 --arg0 0x41 --arg1 0x42
 ```
 
@@ -107,10 +107,9 @@ behaviour before the product emulation implements it.
 
 ## 6. Resource surfaces an engine can use
 
-Category map (details are RM-version-specific and tracked privately where
-provenance requires it):
+Category map (details are RM-version-specific):
 
-| Surface | Purpose | How green-eye helps today |
+| Surface | Purpose | How risc-v-gsp-rm-debugger helps today |
 |---|---|---|
 | Memory / descriptors | allocate, map, free, register host or vidmem ranges | watchpoints on allocation state; snapshot/diff; schema decode |
 | Address spaces / page tables | GPU VA translation, mapping updates | hooks on map/unmap routines; memory diffs; TCG trace of accesses |
@@ -165,10 +164,10 @@ case 7:
 
 ```bash
 make -C sdk
-./greeneye.sh inject --cmd 7 --arg0 0xab --arg1 0xcd
+./risc-v-gsp-rm-debugger.sh inject --cmd 7 --arg0 0xab --arg1 0xcd
 #   direct call   -> 0xcdab
 #   firmware call -> 0xcdab
-./greeneye.sh analyze <printed session dir>     # event/hit report
+./risc-v-gsp-rm-debugger.sh analyze <printed session dir>     # event/hit report
 ```
 
 ## 10. What comes next (roadmap)