Release: bump plugin version 0.2.0 → 0.2.1 — ship the post-0.2.0 loop fixes to downstream installs

[robercano-ghbot]

Why

0.2.0 (#109 / PR #110) was cut mid-day 2026-07-10, hours before several important loop fixes landed on main. Downstream installs on 0.2.0 are missing:

• d37e951 — driver one-shot contract: foreground-only orchestration, no turn-end before the PR exists, debris cleanup on failure (the phantom-success fix; enforcement tracked in Loop: driver one-shot contract needs enforcement + tests — background orchestration produced phantom-success drivers and wedged the queue #111).
• PR feat(loop): auto-cleanup worker worktree + branch after merge (#91) #112 (Worktree hygiene: auto-remove worker worktrees (and branches) after their PR merges #91) — worker worktree + branch auto-cleanup after merge (incl. follow-up 933f202, origin-ancestry merged-ness check).
• fd81eeb — claude-rc-service/arm-loop v5: explicit --spawn (new validated --spawn flag, default same-dir) so remote-control never blocks on its interactive first-run question inside detached tmux.
• Whatever lands from Cockpit: group Live worker progress by task, link issue/PR, and make columns sortable #92 (in flight at filing time) and, if planned before this, Orchestrator: workers must never mutate the MAIN checkout's git state — guard hook + dirty-main census signal #106/Loop daemon: harden runtime-env resolution — bake resolved PATH into installed units, don't depend on nvm sourcing at runtime #107/Loop: driver one-shot contract needs enforcement + tests — background orchestration produced phantom-success drivers and wedged the queue #111.

Scope

• Bump version in .claude/.claude-plugin/plugin.json (0.2.0 → 0.2.1 per owner; note: feat(loop): auto-cleanup worker worktree + branch after merge (#91) #112's auto-cleanup is arguably a feature, so 0.3.0 is defensible if the owner prefers strict semver — owner's call, default 0.2.1).
• Changelog entry: driver contract fix, worktree auto-cleanup, arm-loop/claude-rc v5, plus anything merged between filing and pickup.
• Verify marketplace/manifest metadata agrees with the new version.
• Sanity: downstream /orchestrator:sync on the new release re-stamps arm-loop.sh + claude-rc.service to v5 cleanly, and re-arm instructions (re-run arm-loop, restart claude-rc) are stated in the changelog.

Sequencing

Owner intent: AFTER the currently planned queue (at filing: #92 in flight) and any of #106/#107/#111 the owner plans before this — the release should carry them. Filed backlog; the owner labels planned when the queue is ready.