/orchestrator:sync v2 — one sanctioned migration path to bring consumer repos current

[robercano-ghbot]

Blocked by #134, #136

Problem

Consumer repos drift and today's remedy was an ad-hoc refresh script (reDeploy, commit cc6772a in that repo; script deliberately deleted afterward — not a pattern to repeat). Current consumer debt: reDeFi runs an ACTIVE loop on 12 vendored scripts predating #111/#119 with no hooks file at all; website sits on plugin 0.1.4; every consumer lacks the needs-human label.

Do

Extend /orchestrator:sync into the one sanctioned migration command, executing the #134 strategy decision (refresh full script set OR de-vendor to plugin-cache-by-reference):

1. sync scripts per Consumer repos carry stale vendored .claude/scripts that shadow the fresh plugin cache — manage them or stop vendoring #134; re-stamp managed files (units, arm-loop)
2. verify environment: .env/GH_BOT_TOKEN, bot identity, plugin version ≥ the Release 0.2.2 — published plugin cache lacks the #131 driver working-directory fix #136 release
3. create missing repo plumbing: needs-human + module:* labels
4. verify observability plumbing (worker-tools + events land in consumer state — cf. Ship the worker tool-mirror hook in hooks/hooks.json — cockpit live-workers panel is reCode-only #137)
5. print the deploy-lag step: re-arm/restart ONLY between drivers (check the consumer's loop-runs.log), ideally verified by the Loop: post-arm canary driver — verify the spawn environment before advancing real issues #132 canary

Related (not blocking): #132, #133, #137, #139.

Acceptance

Running sync v2 in reDeploy and reDeFi leaves both loops on current code with green post-sync verification, no manual file copying.

🤖 Generated with Claude Code

[robercano-ghbot]

Related: #142 (loop-managed cockpit lifecycle) — no blocking edge in either direction; sync v2 is re-runnable, so consumers get #142 at whichever sync follows it. See #142's comment for the arm-loop.sh graceful-degrade requirement that keeps a partial re-stamp from breaking stale consumers.

[robercano-ghbot]

Issue #141's feat/issue-141-* branch has stalled and already been resumed 2 times without landing a PR. The loop will not retry it automatically -- labeling needs-human. Address it by hand, then either close it out or clear its entry in .claude/state/loop-resume-attempts.json to let the loop resume.