feat(hooks): add git-workflow to the fleet hook set #1262
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/agentic-os!1262
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?
Last piece of coilyco-flight-deck/infrastructure#937.
agentic-os wires
git-workflowas a local hook, and the managed hook set this script writes into consumer repos never carried it. So the authoring repo was gated against git-workflow block drift and no consumer repo ever was. That asymmetry is the whole of the issue: one repo stayed current and 18 drifted, silently, because nothing downstream could notice.Safe to land now
Inert until each repo's managed block is refreshed, so this is not a flag day. The hook ships in the release the applier already tracks, and
test_default_hook_ids_exist_at_the_pinned_revcovers exactly that, passing with the addition.Ordering matters and it is already satisfied: the blocks landed first, in coilyco-flight-deck/infrastructure#943. Adding this gate to a repo whose block is still stale would turn it red on the next commit. sirens-echo is the one repo still without its block, blocked on unrelated drift at coilyco-gaming/sirens-echo#1157, so its config refresh should wait for that.
Full suite at 723 passed.
Co-Authored-By: Claude Opus 5 (1M context) noreply@anthropic.com