chore: stale agentic-os pre-commit pin (v0.18.0 → v0.65.0) #36

New issue

Closed

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

coilysiren commented

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

Owner

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

No retired hooks present, but the pin is behind. Refreshing keeps hook IDs and renames (e.g. validate-skills → check-skills) in sync with the suite.

Fix

From the agentic-os checkout:

python3 scripts/apply-agentic-os-hooks.py --repo eco-app --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.18.0`; current suite is `v0.65.0`. No retired hooks present, but the pin is behind. Refreshing keeps hook IDs and renames (e.g. `validate-skills` → `check-skills`) in sync with the suite. ### Fix From the `agentic-os` checkout: ``` python3 scripts/apply-agentic-os-hooks.py --repo eco-app --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 added the

label

2026-07-04 09:50:21 +00:00

coilyco-ops commented

2026-07-04 17:48:48 +00:00

Member

🔒 Reserved by ward agent --driver claude — container engineer-claude-eco-app-36 on host KAI-DESKTOP-TOWER is carrying this issue (reserved 2026-07-04T17:48:43Z). Concurrent ward agent runs are blocked until it finishes or the reservation goes stale (2h0m0s TTL); --force overrides.

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 agent

🔒 Reserved by `ward agent --driver claude` — container `engineer-claude-eco-app-36` on host `KAI-DESKTOP-TOWER` is carrying this issue (reserved 2026-07-04T17:48:43Z). Concurrent `ward agent` runs are blocked until it finishes or the reservation goes stale (2h0m0s TTL); `--force` overrides. **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 agent`

coilysiren referenced this issue from a commit

2026-07-04 17:52:33 +00:00

chore(hooks): agentic-os pre-commit pin already current at v0.193.0

coilysiren closed this issue

2026-07-04 17:52:33 +00:00

coilysiren commented

2026-07-04 17:53:08 +00:00

Author

Owner

WARD-OUTCOME: done - pin was already current at v0.193.0 (landed via #48); recorded the resolution and closed as superseded.

This one turned out to be a stale ticket rather than real work. The issue asked to bump the managed agentic-os block from v0.18.0 to v0.65.0, but by the time it reached me #48 had already rolled the pin all the way to v0.193.0 - the current suite tag - including the validate-skills -> check-skills rename it flagged. Re-running apply-agentic-os-hooks.py --repo eco-app --rev v0.193.0 reported unchanged, and the hook set already matched the eco-* profile (code-comments skipped), so git diff was empty.

The only thing that briefly fought back was deciding how to close an issue with no diff: I recorded an empty commit carrying the closes #36 trailer so the git history explains why nothing changed, rather than silently closing. Confidence is high - the apply script is idempotent and confirmed a no-op, and the pre-commit suite passed clean.

No follow-ups needed here. Worth noting for the fleet sweep though: this repo was already ahead of the sweep's v0.65.0 target, so any remaining tickets from that same audit are probably worth a quick freshness check before dispatch.

WARD-OUTCOME: done - pin was already current at v0.193.0 (landed via #48); recorded the resolution and closed as superseded. This one turned out to be a stale ticket rather than real work. The issue asked to bump the managed agentic-os block from v0.18.0 to v0.65.0, but by the time it reached me #48 had already rolled the pin all the way to v0.193.0 - the current suite tag - including the `validate-skills` -> `check-skills` rename it flagged. Re-running `apply-agentic-os-hooks.py --repo eco-app --rev v0.193.0` reported `unchanged`, and the hook set already matched the eco-* profile (code-comments skipped), so `git diff` was empty. The only thing that briefly fought back was deciding how to *close* an issue with no diff: I recorded an empty commit carrying the `closes #36` trailer so the git history explains why nothing changed, rather than silently closing. Confidence is high - the apply script is idempotent and confirmed a no-op, and the pre-commit suite passed clean. No follow-ups needed here. Worth noting for the fleet sweep though: this repo was already ahead of the sweep's v0.65.0 target, so any remaining tickets from that same audit are probably worth a quick freshness check before dispatch.

coilyco-ops added the

headless

labels

2026-07-10 11:58:08 +00:00