chore: stale agentic-os pre-commit pin (v0.16.0) still ships 2 retired commit-msg hook(s) #20

New issue

Closed

opened 2026-06-18 02:42:30 +00:00 by coilysiren · 2 comments

coilysiren commented

2026-06-18 02:42:30 +00:00

Owner

The managed agentic-os block in this repo's .pre-commit-config.yaml is pinned at v0.16.0; current suite is v0.65.0.

Actively blocking commits. The block still lists retired commit-msg-stage hook(s) (conventional-commit and/or closes-issue) that were deleted from the suite. They fire a phantom check on every commit.

Fix

From the agentic-os checkout:

python3 scripts/apply-agentic-os-hooks.py --repo lunch-money-k8s --rev v0.65.0

That regenerates the managed block (dropping retired hooks, picking up renames) and re-runs pre-commit install. Commit the resulting .pre-commit-config.yaml change.

Context

Found during a fleet sweep kicked off when conventional-commit blocked a commit in cli-guard (since fixed to v0.65.0). Every repo except cli-guard is behind on the pin.

The managed `agentic-os` block in this repo's `.pre-commit-config.yaml` is pinned at `v0.16.0`; current suite is `v0.65.0`. **Actively blocking commits.** The block still lists retired `commit-msg`-stage hook(s) (`conventional-commit` and/or `closes-issue`) that were deleted from the suite. They fire a phantom check on every commit. ### Fix From the `agentic-os` checkout: ``` python3 scripts/apply-agentic-os-hooks.py --repo lunch-money-k8s --rev v0.65.0 ``` That regenerates the managed block (dropping retired hooks, picking up renames) and re-runs `pre-commit install`. Commit the resulting `.pre-commit-config.yaml` change. ### Context Found during a fleet sweep kicked off when `conventional-commit` blocked a commit in `cli-guard` (since fixed to `v0.65.0`). Every repo except `cli-guard` is behind on the pin.

coilyco-ops commented

2026-07-02 02:24:41 +00:00

Member

🔒 Reserved by ward agent --driver claude — container engineer-claude-lunch-money-k8s-20 on host kais-macbook-pro-2.local is carrying this issue (reserved 2026-07-02T02:24:39Z). Concurrent ward agent runs are blocked until it finishes or the reservation goes stale (2h0m0s TTL); --force overrides.

— Claude (she/her), via ward agent

🔒 Reserved by `ward agent --driver claude` — container `engineer-claude-lunch-money-k8s-20` on host `kais-macbook-pro-2.local` is carrying this issue (reserved 2026-07-02T02:24:39Z). Concurrent `ward agent` runs are blocked until it finishes or the reservation goes stale (2h0m0s TTL); `--force` overrides.  — Claude (she/her), via `ward agent`

coilysiren referenced this issue from a commit

2026-07-02 02:27:10 +00:00

chore: bump agentic-os pre-commit pin to v0.65.0

coilysiren closed this issue

2026-07-02 02:27:10 +00:00

coilysiren commented

2026-07-02 02:27:46 +00:00

Author

Owner

WARD-OUTCOME: done - bumped agentic-os pre-commit pin v0.16.0 -> v0.65.0, dropped the retired commit-msg hooks, landed on main.

The pin bump itself was a one-liner-feeling change, but it wasn't quite one. The rollout script drives off ~/projects/<org>/*, so in a /workspace container I had to point PROJECTS_ROOT=/workspace at it before --repo lunch-money-k8s matched. Small snag, no drama.

What fought back a little: the regenerated block is only half the story. Jumping 49 minor versions dragged in a stricter catalog-trifecta check that then blocked the very commit carrying the fix, because README and docs/FEATURES still pointed their "See also" at the old .coily/coily.yaml. Repointing both at .ward/ward.yaml (the coily -> ward migration already half-done in AGENTS.md) cleared it. Worth noting for the rest of the fleet sweep: the pin bump alone may not commit cleanly on repos that never finished the ward rename.

Confidence is high. pre-commit run --all-files is fully green, the retired hooks are gone so commits flow, and local/remote main match at 67c99a7. No follow-ups I'd file beyond the heads-up above.

WARD-OUTCOME: done - bumped agentic-os pre-commit pin v0.16.0 -> v0.65.0, dropped the retired commit-msg hooks, landed on main. The pin bump itself was a one-liner-feeling change, but it wasn't quite one. The rollout script drives off `~/projects/<org>/*`, so in a `/workspace` container I had to point `PROJECTS_ROOT=/workspace` at it before `--repo lunch-money-k8s` matched. Small snag, no drama. What fought back a little: the regenerated block is only half the story. Jumping 49 minor versions dragged in a stricter `catalog-trifecta` check that then blocked the very commit carrying the fix, because README and docs/FEATURES still pointed their "See also" at the old `.coily/coily.yaml`. Repointing both at `.ward/ward.yaml` (the coily -> ward migration already half-done in AGENTS.md) cleared it. Worth noting for the rest of the fleet sweep: the pin bump alone may not commit cleanly on repos that never finished the ward rename. Confidence is high. `pre-commit run --all-files` is fully green, the retired hooks are gone so commits flow, and local/remote `main` match at 67c99a7. No follow-ups I'd file beyond the heads-up above.