apply-agentic-os-hooks: DEFAULT_HOOK_IDS drifted ahead of DEFAULT_REV (merge-conflicts) #187
Labels
No labels
burndown-2026-06
coherence-core
consult
headless
interactive
P0
P1
P2
P3
P4
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#187
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
DEFAULT_HOOK_IDSin scripts/apply-agentic-os-hooks.py listsmerge-conflicts, butDEFAULT_REV = v0.14.0and the v0.14.0 tag of.pre-commit-hooks.yamldoes not ship that hook id (it was added after the tag, present only on HEAD / +21 commits).Effect: running the apply script against any consumer writes a managed block that pre-commit then rejects:
Hit while bumping cli-guard from v0.11.1 to current. Worked around in cli-guard by dropping the
merge-conflictsline from its managed block (it already runs the stock pre-commit-hookscheck-merge-conflict).Fix options: (a) cut v0.15.0 containing
merge-conflictsand setDEFAULT_REV=v0.15.0; or (b) gate per-hook availability by rev.Invariant to add: every id in
DEFAULT_HOOK_IDSmust exist in.pre-commit-hooks.yamlatDEFAULT_REV- a cheap CI assert would have caught this before rollout.