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

diff --git a/debug/risc-v-gsp-rm-vm/docs/20-MCP-SERVER.md b/debug/risc-v-gsp-rm-vm/docs/20-MCP-SERVER.md
index a3b6111..dbfbb36 100644
--- a/debug/risc-v-gsp-rm-vm/docs/20-MCP-SERVER.md
+++ b/debug/risc-v-gsp-rm-vm/docs/20-MCP-SERVER.md
@@ -1,12 +1,12 @@
-# 20 — MCP server (green-eye agent interface)
+# 20 — MCP server (risc-v-gsp-rm-debugger agent interface)
 
 > **# TOOL IN DEVELOPMENT - NOT READY YET!** See 00 for status.
 
 ## 1. What it is
 
-`plugins/mcp_server.py` is the green-eye **MCP (Model Context Protocol)
+`plugins/mcp_server.py` is the risc-v-gsp-rm-debugger **MCP (Model Context Protocol)
 server** — roadmap [`R3`](08-ROADMAP.md#r3-mcp-server-plugin) and
-[`H7`](../GREEN-EYE-ROADMAP.md). It exposes the *active* `Session` as MCP
+[`H7`](../RISC-V-GSP-RM-DEBUGGER-ROADMAP.md). It exposes the *active* `Session` as MCP
 tools so an AI agent (Claude Code, opencode, any MCP client) can inspect
 symbols, set breakpoints/watchpoints, run the target, read memory, snapshot,
 analyse/compare recordings, inject services, and drive the harnesses.
@@ -14,7 +14,7 @@ analyse/compare recordings, inject services, and drive the harnesses.
 * **Stdlib-only**: JSON-RPC 2.0 over newline-delimited stdin/stdout, no MCP
   library, no network listener unless explicitly asked.
 * **Plugin first**: `register(ge)` adds an `mcp-serve` REPL/CLI command that
-  serves the session already loaded by green-eye.
+  serves the session already loaded by risc-v-gsp-rm-debugger.
 * **Standalone too**: the same file runs as a script that launches its own
   session (`--kernel`, `--backend`, `--record`) and then serves MCP.
 * **Read-only by default**: memory writes, remote calls and injection require
@@ -24,7 +24,7 @@ analyse/compare recordings, inject services, and drive the harnesses.
   `not_available` tool error when the module/file is absent instead of
   crashing. The tool list always advertises every capability.
 
-The core green-eye package is untouched; everything lives in the plugin.
+The core risc-v-gsp-rm-debugger package is untouched; everything lives in the plugin.
 
 ## 2. Running it
 
@@ -54,11 +54,11 @@ Logs go to stderr; **stdout carries protocol frames only**.
 ### 2.2 Plugin mode (serve a live session)
 
 ```bash
-./greeneye.sh attach --kernel firmware/uproc_demo/build/uproc_demo.elf \
+./risc-v-gsp-rm-debugger.sh attach --kernel firmware/uproc_demo/build/uproc_demo.elf \
     --plugin plugins/mcp_server.py
-greeneye> mcp-serve                      # read/observe
-greeneye> mcp-serve --allow-write        # + memory writes / remote calls
-greeneye> mcp-serve --allow-inject       # + service injection
+risc-v-gsp-rm-debugger> mcp-serve                      # read/observe
+risc-v-gsp-rm-debugger> mcp-serve --allow-write        # + memory writes / remote calls
+risc-v-gsp-rm-debugger> mcp-serve --allow-inject       # + service injection
 ```
 
 `mcp-serve` blocks until the MCP client disconnects or calls the `close`
@@ -80,7 +80,7 @@ client configs use standalone mode. Use absolute paths.
 ```json
 {
   "mcpServers": {
-    "green-eye": {
+    "risc-v-gsp-rm-debugger": {
       "command": "python3",
       "args": [
         "/home/rmcore/Git/integdev_gpu_drv/open-iov/debug/risc-v-gsp-rm-vm/plugins/mcp_server.py",
@@ -94,7 +94,7 @@ client configs use standalone mode. Use absolute paths.
 }
 ```
 
-Or, one line: `claude mcp add green-eye -- python3
+Or, one line: `claude mcp add risc-v-gsp-rm-debugger -- python3
 <tool-root>/plugins/mcp_server.py --stdio --record`.
 
 ### 3.2 opencode (`opencode.json`)
@@ -103,7 +103,7 @@ Or, one line: `claude mcp add green-eye -- python3
 {
   "$schema": "https://opencode.ai/config.json",
   "mcp": {
-    "green-eye": {
+    "risc-v-gsp-rm-debugger": {
       "type": "local",
       "command": [
         "python3",
@@ -227,7 +227,7 @@ recorded, and the session can be compared like any other run.
 2. **No guest, no hardware.** The server drives the simulator/QEMU session
    only. It does not touch `/dev`, a kernel module, an mdev, a guest or a
    physical GPU; the agent runs against the simulator by default
-   ([H7](../GREEN-EYE-ROADMAP.md), [15-AGENTIC-GSP-IDE](15-AGENTIC-GSP-IDE.md) §5).
+   ([H7](../RISC-V-GSP-RM-DEBUGGER-ROADMAP.md), [15-AGENTIC-GSP-IDE](15-AGENTIC-GSP-IDE.md) §5).
 3. **Read-only by default.** `--allow-write` enables `write_mem` and
    `call_function`; `--allow-inject` enables `inject_service`. The agent's
    client config decides which manifest class it gets; a read/observe agent is