rename to cc-ci-orchestrator: update all repo name references

Gitea repos renamed:
  cc-ci-autonomous-orchestrator → cc-ci-orchestrator
  cc-ci-orchestrator            → archived-cc-ci-orchestrator

Updated in this workspace:
- README.md, AGENTS.md: repo title
- cc-ci-plan/plan-orchestrator-migration.md: cc-ci-autonomous-orchestrator refs
- cc-ci-plan/plan-repo-consolidation.md: marked complete + Pi remote-update notice
- cc-ci-plan/launch-orchestrator.sh, launch.sh: session naming comment cleanup

NOTE: Pi clone still has the old origin URL. On the Pi, run:
  git remote set-url origin https://git.autonomic.zone/recipe-maintainers/cc-ci-orchestrator.git

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

cc-ci-plan/plan-orchestrator-migration.md

@@ -33,7 +33,7 @@ service + claude CLI + sops secrets). Then C (stage workspace), claude auth (ope
 ## 0. Current footprint (what has to move)
 
 On the Pi (`raspberrypi`, aarch64), workspace `/srv/cc-ci` (itself the
-`cc-ci-autonomous-orchestrator` git repo):
+`cc-ci-orchestrator` git repo — formerly `cc-ci-autonomous-orchestrator`):
 
 | Item | What | Move strategy |
 |---|---|---|
@@ -103,7 +103,7 @@ test server. Contents:
    supervisor **not yet started** — or started in a dry mode).
 
 ### Phase C — stage the workspace (no cutover yet)
-6. On the VM: clone `cc-ci-autonomous-orchestrator` (the loop code), clone the Builder/Adversary
+6. On the VM: clone `cc-ci-orchestrator` (the loop code), clone the Builder/Adversary
    working repos fresh from git.autonomic.zone, clone `cc-ci-secrets`, rsync `references/`.
 7. Copy `.phase-idx` (resume point = phase 2) so the VM watchdog resumes the right phase.
 8. **Operator step:** `claude auth login` on the VM (device code) so the loops can run