chore: stale agentic-os pre-commit pin (v0.11.1) still ships 2 retired commit-msg hook(s) #31
Labels
No labels
burndown-2026-06
coherence-core
consult
headless
interactive
P0
P1
P2
P3
P4
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
coilyco-flight-deck/galaxy-gen#31
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?
The managed
agentic-osblock in this repo's.pre-commit-config.yamlis pinned atv0.11.1; current suite isv0.65.0.Actively blocking commits. The block still lists retired
commit-msg-stage hook(s) (conventional-commitand/orcloses-issue) that were deleted from the suite. They fire a phantom check on every commit.Fix
From the
agentic-oscheckout:That regenerates the managed block (dropping retired hooks, picking up renames) and re-runs
pre-commit install. Commit the resulting.pre-commit-config.yamlchange.Context
Found during a fleet sweep kicked off when
conventional-commitblocked a commit incli-guard(since fixed tov0.65.0). Every repo exceptcli-guardis behind on the pin.ward agent goose headlessfunctionality #141🔒 Reserved by
ward agent --driver claude— containerengineer-claude-galaxy-gen-31on hostKAI-DESKTOP-TOWERis carrying this issue (reserved 2026-07-04T17:49:43Z). Concurrentward agentruns are blocked until it finishes or the reservation goes stale (2h0m0s TTL);--forceoverrides.Do not comment on or edit this issue to steer the run while it is reserved. The engineer seeded the body once at launch and never re-reads it, so a comment or edit reaches only human readers, never the running engineer. A correction goes to a new issue, dispatched fresh — that is the only channel that reaches a run in flight. Where the forge supports it, ward locks this conversation to make that a road-block rather than a convention (ward#494).
— Claude (she/her), via
ward agentWARD-OUTCOME: done - bumped the managed agentic-os pre-commit pin to the current suite (v0.166.0 -> v0.193.0), landed on main.
This one turned out to be mostly already-fixed. The issue's premise (pinned at v0.11.1, still shipping the retired
conventional-commit/closes-issuecommit-msg hooks) was stale - commitf570869had already regenerated the block to v0.166.0 and dropped those hooks, so no phantom checks were firing anymore. What was left was genuine drift: the pin trailing the current suite release.The one wrinkle was the fleet script (
apply-agentic-os-hooks.py) discovers repos under~/projects/<org>/*, which doesn't match this container's/workspace/galaxy-genlayout. PointingPROJECTS_ROOT=/workspaceat it made discovery work cleanly, and the generated diff was a single-line rev bump - the hook id set is identical between the two revs, so nothing else moved. All v0.193.0 hooks passed on commit.Confident in the result: it's a one-line pin bump verified by a clean pre-commit run. No follow-ups worth filing.