AGENTS.md: document resume-by-name + /remote-control for the orchestrator session

Clarify the two distinct names (--resume <conversation> vs --remote-control display
label), the in-session /remote-control shortcut, and the persist-vs-reconnect model.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

AGENTS.md

@@ -20,11 +20,20 @@ watches from outside.
 
 Run this session as a long-lived **interactive** session with `--remote-control` so the operator can
 check in on the loops and steer/restart things from **claude.ai/code** (or the Claude mobile app)
-without being at the terminal:
+without being at the terminal.
 
-```bash
-claude --remote-control 'cc-ci-orchestrator' --dangerously-skip-permissions
-```
+- **Already in the session?** Just run `/remote-control` — it attaches claude.ai/code to the live
+  conversation (no exit, no resume needed).
+- **Starting fresh:** `claude --remote-control 'autonomous-orchestrator' --dangerously-skip-permissions`
+- **Resuming this orchestrator later (history preserved):**
+  ```bash
+  claude --resume autonomous-orchestrator --remote-control "autonomous-orchestrator" --dangerously-skip-permissions
+  ```
+  Note the two names are different: `--resume <name|id>` restores *this conversation* (the name set
+  via `-n/--name`, shown in the `/resume` picker); the `--remote-control [name]` value is only the
+  web display label and resumes nothing. The conversation persists on disk across exits; remote
+  control itself only stays "connected" while the local process is alive (resume + re-enable to get
+  it back after a full exit).
 
 Use it to: tail loop logs (`cc-ci-plan/launch.sh logs builder|adversary|watchdog`), inspect
 `STATUS.md`/`REVIEW.md` in the cc-ci repo, edit the plan or prompts, restart a stuck loop, or