Consolidate setup commands: drop legacy /setup-orchestrator + /sync-orchestrator pointer stubs

.claude/.claude-plugin/README.md

@@ -6,7 +6,7 @@ that ship to downstream installs are what runs the live self-hosted PR loop here
 
 ## Dual command invocation
 - **In-repo (dogfooding):** commands run as project-level slash commands, e.g. `/pr-loop`,
-  `/harden`, `/setup-orchestrator`, `/sync-orchestrator`, `/test-pr`.
+  `/harden`, `/test-pr`.
 - **Installed as a plugin:** Claude Code auto-namespaces commands under the plugin `name`
   (`orchestrator`), so the same commands become `/orchestrator:pr-loop`,
   `/orchestrator:harden`, etc. No file renames are needed for this — the namespace comes

.claude/.claude-plugin/plugin.json

@@ -6,8 +6,6 @@
   "commands": [
     "./commands/harden.md",
     "./commands/pr-loop.md",
-    "./commands/setup-orchestrator.md",
-    "./commands/sync-orchestrator.md",
     "./commands/test-pr.md"
   ]
 }

docs/MIGRATION.md

@@ -12,7 +12,7 @@ If you haven't installed the plugin yet, do that first — see [`GETTING_STARTED
 Remove the copied harness that the plugin now carries — it's generic, not project-specific, and staying on a
 frozen copy means you never get fixes/improvements:
 - `.claude/agents/` — orchestrator, implementer, reviewer, test-runner.
-- `.claude/commands/` — `pr-loop.md`, `harden.md`, `setup-orchestrator.md`, `test-pr.md`, etc. (they resolve
+- `.claude/commands/` — `pr-loop.md`, `harden.md`, `test-pr.md`, etc. (they resolve
   as namespaced `/orchestrator:*` commands once the plugin is enabled). Note: `pr-loop-self.md` is **not**
   among these — it lives under `.claude/self/` (not `.claude/commands/`) and is not plugin-distributed; see
   `.claude/self/README.md` if your repo has a self-hosting setup of its own.

docs/PROMPTS.md

@@ -2,13 +2,13 @@
 
 Copy-paste these into Claude Code. The first two populate the files you must fill; the rest drive day-to-day work.
 
-> **Shortcut:** the **`/setup-orchestrator`** command runs an interactive interview that covers prompts 1–2
+> **Shortcut:** the **`/orchestrator:setup`** command runs an interactive interview that covers prompts 1–2
 > (draft `CLAUDE.md`, fill `gates.json`) *and* the rest of onboarding (labels, bot check, CI, arming the loop,
 > hardening). Use it for a fresh project; reach for the individual prompts below when you want to redo one piece.
 >
 > **Brand-new project?** Read the **[new-project configuration
 > checklist](GETTING_STARTED.md#new-project-configuration-checklist)** and **[USAGE.md → "Autonomous loop &
-> the issue queue"](USAGE.md#autonomous-loop--the-issue-queue)** first — they explain what `/setup-orchestrator`
+> the issue queue"](USAGE.md#autonomous-loop--the-issue-queue)** first — they explain what `/orchestrator:setup`
 > (and prompts 1–2 below) are actually wiring up, and the one convention that trips people up: only issues
 > labelled `module:*` are ever picked up automatically.