Rebrand to reCode: plugin identity, docs, README (repo already renamed)

[robercano]

Context

The GitHub repo was renamed to robercano/reCode on 2026-07-08 (old URLs redirect). The product name reCode is decided. Everything inside the repo still says "ai-project-orchestrator".

Change

Cross-module — the orchestrator should scope this into a harness sub-task and a docs sub-task:

Harness (.claude/)

• plugin.json: plugin name/description → reCode (check downstream impact: does the plugin name change break installed consumers or the sync skill's version markers? If so, document the migration in docs/MIGRATION.md).
• Any script/skill text that names the old repo or "AI Project Orchestrator" (grep for ai-project-orchestrator and the long-form name across .claude/).

Docs (docs/, README.md)

• README title/intro → reCode, with the old name mentioned once for continuity.
• docs/*.md: sweep references to the repo URL and product name.
• MIGRATION.md entry: what a downstream repo that installed the plugin under the old name needs to do (expected: nothing — GitHub redirects — but verify the marketplace/install path).

Out of scope here (owner-side, not loop work): registering the recode-dev / recodehq GitHub org, recode.sh domain, and the npm scope decision.

Done when

• grep -ri "ai-project-orchestrator" --exclude-dir=.git returns only intentional historical mentions (MIGRATION.md, changelog-style notes).
• Plugin installs/syncs cleanly under the new identity; sync skill re-stamps managed files without churn.