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

diff --git a/docs/06-portability/hardware-software-matrix.md b/docs/06-portability/hardware-software-matrix.md
index 8fca9e9..857d752 100644
--- a/docs/06-portability/hardware-software-matrix.md
+++ b/docs/06-portability/hardware-software-matrix.md
@@ -70,21 +70,21 @@ so new transports are a small, isolated implementation.
 3. Record the differences; prefer configuration over code.
 4. Publish the profile, the evidence, and any workarounds.
 
-**Green-eye portability pipeline (experimental).**
+**Risc-V GSP-RM debugger portability pipeline (experimental).**
 
-<!-- change (2026-10-02): add the green-eye portability pipeline to the new-GPU
+<!-- change (2026-10-02): add the risc-v-gsp-rm-debugger portability pipeline to the new-GPU
 procedure and point at the RUNBOOK/user guide; additive only. -->
 
 Before the profile change lands, run the firmware-side pipeline from
 `debug/risc-v-gsp-rm-vm/` and attach its output:
-`./greeneye.sh probe <image> --symbols <db> --record` for the first-touch map;
-`./greeneye.sh symbols export ...` for a provenance-carrying symbol DB;
+`./risc-v-gsp-rm-debugger.sh probe <image> --symbols <db> --record` for the first-touch map;
+`./risc-v-gsp-rm-debugger.sh symbols export ...` for a provenance-carrying symbol DB;
 `python3 harness/portability_matrix.py --target <reference> --target <candidate>
 --out dumps/matrix-<candidate>` for per-pair sessions and `compare` reports;
 then classify profile-versus-logic deltas with the decision table in
 `debug/risc-v-gsp-rm-vm/docs/14-ADVERSARIAL-INTEROP-GUIDE.md` §4.1. The
 command-level walkthrough is in the
-[green-eye user guide](../05-operations/04-green-eye-user-guide.md); the
+[risc-v-gsp-rm-debugger user guide](../05-operations/04-risc-v-gsp-rm-debugger-user-guide.md); the
 incident procedure, evidence expectations and rollback rules are in the
 [Open-IOV Defensive Operations Runbook](../RUNBOOK.md) S5.
 
@@ -144,7 +144,7 @@ the profile files, not the profile schema.
 **Evidence expectations for adding support.**
 
 <!-- change (2026-10-02): state the evidence required before a combination is
-entered in the matrix, and link the RUNBOOK bundle checklist and green-eye
+entered in the matrix, and link the RUNBOOK bundle checklist and risc-v-gsp-rm-debugger
 portability pipeline; additive only. -->
 
 A combination is entered in the matrix only with: the profile fields recorded;
@@ -158,7 +158,7 @@ combination stays **Target** or **Experimental**. The full bundle checklist
 and fault tree are in the
 [Open-IOV Defensive Operations Runbook](../RUNBOOK.md) §6–§7; the pipeline
 commands are in the
-[green-eye user guide](../05-operations/04-green-eye-user-guide.md).
+[risc-v-gsp-rm-debugger user guide](../05-operations/04-risc-v-gsp-rm-debugger-user-guide.md).
 
 ### 6.1 Userspace driver facts