coilyco-flight-deck/ward

Fork 0

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

New issue

Closed

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

coilysiren commented

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

Owner

The managed agentic-os block in this repo's .pre-commit-config.yaml is pinned at v0.19.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 ward --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.19.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 ward --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.

coilysiren referenced this issue

2026-06-18 04:10:24 +00:00

ward-kdl: list-all (auto-paginating) action for forgejo issue list #131

coilysiren added the

headless

labels

2026-06-18 06:20:45 +00:00

coilyco-ops commented

2026-06-18 07:41:37 +00:00

Member

🛫 ward pre-flight: NO-GO

ward agent goose headless ran a pre-flight feasibility read on this issue before detaching a fire-and-forget run, and the agent judged it NO-GO - it should not be carried unattended until a human weighs in.

Cannot confirm whether the required agentic-os tools/scripts will be available to execute the update procedure in a fresh environment.

No container was launched. Review the issue (clarify the scope, resolve the unknown, or split it), then re-dispatch - ward agent goose headless <ref> --no-preflight skips this gate once you've decided it's good to go.

full pre-flight read

( O)> ● new session · ollama qwen3-coder:30b
__) 20260618_1108 · /private/var/folders/gt/p630435j2y3dmk7f_twxqqr40000gp/T/ward-preflight-2805740881
L L goose is ready

────────────────────────────────────────
▸ tree
path: .

────────────────────────────────────────
▸ shell
command: ls -la

────────────────────────────────────────
▸ analyze
path: .pre-commit-config.yaml

────────────────────────────────────────
▸ search_available_extensions extensionmanager

(empty directory)total 0
drwx------ 2 kai staff 64 Jun 18 00:41 .
drwx------@ 817 kai staff 26144 Jun 18 00:41 ..Error: path not found: /private/var/folders/gt/p630435j2y3dmk7f_twxqqr40000gp/T/ward-preflight-2805740881/.pre-commit-config.yamlThe issue is about updating a pre-commit hook version pin from v0.19.0 to v0.65.0 in the .pre-commit-config.yaml file, which involves running a script from the agentic-os repository. The main risk is that this script or its dependencies may not be available or compatible in the fresh clone environment, potentially breaking the automated update process. I cannot verify if the necessary tools (like the apply-agentic-os-hooks.py script) are present in the fresh clone since no files exist yet.

NO-GO: Cannot confirm whether the required agentic-os tools/scripts will be available to execute the update procedure in a fresh environment.

Posted automatically by ward agent goose headless pre-flight (ward#147, ward#149).

— Goose, via ward agent

### 🛫 ward pre-flight: NO-GO `ward agent goose headless` ran a pre-flight feasibility read on this issue before detaching a fire-and-forget run, and the agent judged it **NO-GO** - it should not be carried unattended until a human weighs in. > Cannot confirm whether the required `agentic-os` tools/scripts will be available to execute the update procedure in a fresh environment. No container was launched. Review the issue (clarify the scope, resolve the unknown, or split it), then re-dispatch - `ward agent goose headless <ref> --no-preflight` skips this gate once you've decided it's good to go. <details><summary>full pre-flight read</summary> __( O)> ● new session · ollama qwen3-coder:30b \____) 20260618_1108 · /private/var/folders/gt/p630435j2y3dmk7f_twxqqr40000gp/T/ward-preflight-2805740881 L L goose is ready ──────────────────────────────────────── ▸ tree path: . ──────────────────────────────────────── ▸ shell command: ls -la ──────────────────────────────────────── ▸ analyze path: .pre-commit-config.yaml ──────────────────────────────────────── ▸ search_available_extensions extensionmanager (empty directory)total 0 drwx------ 2 kai staff 64 Jun 18 00:41 . drwx------@ 817 kai staff 26144 Jun 18 00:41 ..Error: path not found: /private/var/folders/gt/p630435j2y3dmk7f_twxqqr40000gp/T/ward-preflight-2805740881/.pre-commit-config.yamlThe issue is about updating a pre-commit hook version pin from v0.19.0 to v0.65.0 in the `.pre-commit-config.yaml` file, which involves running a script from the `agentic-os` repository. The main risk is that this script or its dependencies may not be available or compatible in the fresh clone environment, potentially breaking the automated update process. I cannot verify if the necessary tools (like the `apply-agentic-os-hooks.py` script) are present in the fresh clone since no files exist yet. NO-GO: Cannot confirm whether the required `agentic-os` tools/scripts will be available to execute the update procedure in a fresh environment. </details> --- Posted automatically by `ward agent goose headless` pre-flight (ward#147, ward#149).   — Goose, via `ward agent`

coilyco-ops added

and removed

labels

2026-06-24 04:11:56 +00:00

coilyco-ops commented

2026-06-24 04:35:49 +00:00

Member

🔒 Reserved by ward agent claude — container ward-ward-issue-136-claude-a1ca94ae on host kais-macbook-pro-2.local is carrying this issue (reserved 2026-06-24T04:35:48Z). 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 claude` — container `ward-ward-issue-136-claude-a1ca94ae` on host `kais-macbook-pro-2.local` is carrying this issue (reserved 2026-06-24T04:35:48Z). 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-06-24 04:44:35 +00:00

chore(pre-commit): refresh agentic-os hook pin to v0.65.0

coilysiren closed this issue

2026-06-24 04:44:35 +00:00

coilyco-ops referenced this issue

2026-06-24 05:29:52 +00:00

Hold ward-kdl guardfiles to the 2-contiguous-comment rule (drop the code-comments exclusion, migrate rationale to describe/message) #242

coilysiren referenced this issue

2026-07-01 06:43:51 +00:00

Fix the actual host-broker write failure: commentIssue passes --body-file to an ops verb that rejects it #404