feat(scripts): add the git-workflow block bulk migration #943
No reviewers
Labels
No labels
burndown-2026-06
burndown-2026-08
autonomy
async-consult
autonomy
epic
autonomy
headless
autonomy
live-collab
coherence-core
priority
P0
priority
P1
priority
P2
priority
P3
priority
P4
qa-fixture
role/advocate
role/director
role/exec
role/frontend
role/gamedev
role/human
role/platform
role/qa
role/science
role/sysadmin
state
ambient
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
coilyco-flight-deck/infrastructure!943
Loading…
Reference in a new issue
No description provided.
Delete branch "aos/claude/sy55"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Rollout half of #937, and a sibling of
agents-pointer-migrate.py: agentic-os authors the renderer and the drift gate, this repo lands the block on each managed repo's canonicalmain.Why it was needed
agentic-os wires the
git-workflowhook as a local hook, and the managed hook set written into consumer repos never included it. So the authoring repo was gated against this drift and no consumer repo ever has been. One repo stayed current and 18 did not.Design notes
Lane-aware, because the block is what states the lane and landing it has to obey the lane it states.
merge-remote-mainpushes tomain, and every other lane including undeclared opens a pull request and stops there.Three guards the precedent does not have, each earned during the run:
mainmay declare a lane the stale worktree did not, which is exactly what routed agent-proxy down the pull-request path on its first pass.cappedrather than force-fitting it. Raising a cap is a per-repo judgement with a written reason.The clean-on-main guard both migrations share moves to
migrate_common.py.Run results
15 repos landed. deploy and infrastructure were skipped for dirty host checkouts, exactly as intended, and landed through worktrees instead. sirens-echo is open at coilyco-gaming/sirens-echo#1156, blocked on unrelated pre-existing drift filed at coilyco-gaming/sirens-echo#1157. The
coilysiren/coilysirenprofile repo is exempt in code, because GitHub is canonical there and a Forgejo main push would land on the downstream side.Co-Authored-By: Claude Opus 5 (1M context) noreply@anthropic.com