chore: remove broken coily-trailer prepare-commit-msg hook #246

New issue

Open

opened 2026-06-06 05:57:22 +00:00 by coilysiren · 1 comment

coilysiren commented

2026-06-06 05:57:22 +00:00

Owner

Remove the broken coily-trailer prepare-commit-msg hook (hard-fails on coily v2.53.0, blocks all commits). Fleet decision: coilysiren/inbox#67.

Remove the broken `coily-trailer` prepare-commit-msg hook (hard-fails on coily v2.53.0, blocks all commits). Fleet decision: https://forgejo.coilysiren.me/coilysiren/inbox/issues/67.

coilysiren added the

label

2026-06-17 07:05:29 +00:00

coilysiren commented

2026-06-18 03:51:28 +00:00

Author

Owner

🛫 ward pre-flight: NO-GO

ward agent claude 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.

can't locate the coily-trailer hook definition in any local checkout - it likely lives in the un-cloned coily repo, so the correct merge target is unresolved and a human should confirm whether the fix lands in coily, infrastructure/ansible, or both before an unattended push.

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

full pre-flight read

PRE-FLIGHT read on infrastructure#246:

I went looking for the hook on disk. The installed .git/hooks/prepare-commit-msg in the infrastructure checkout is the stock pre-commit dispatcher, and coily-trailer / prepare-commit-msg appear in zero tracked files across the local infrastructure, agentic-os, and agentic-os-kai checkouts. Per the repo's own authoring-vs-rollout doctrine, the hook is almost certainly authored in the coily repo's .pre-commit-hooks.yaml (not cloned here), while infrastructure would only carry the ansible/baseline rollout that fans it out - and I couldn't find that rollout reference in infra's .pre-commit-config.yaml either.

The main risk is target ambiguity: the issue is filed against infrastructure, but the actual hook definition likely needs to be removed in the coily repo, and the rollout removal may live in an ansible baseline I couldn't locate from the issue text alone. An unattended run could clone coily, guess wrong, and push the removal to the wrong repo's main - a cross-repo fork that's annoying to unwind. That said, the change itself is small and reversible, so a few minutes of human confirmation on which repo owns the fix would de-risk it entirely.

NO-GO: can't locate the coily-trailer hook definition in any local checkout - it likely lives in the un-cloned coily repo, so the correct merge target is unresolved and a human should confirm whether the fix lands in coily, infrastructure/ansible, or both before an unattended push.

Posted automatically by ward agent claude headless pre-flight (ward#147).

### 🛫 ward pre-flight: NO-GO `ward agent claude 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. > can't locate the `coily-trailer` hook definition in any local checkout - it likely lives in the un-cloned `coily` repo, so the correct merge target is unresolved and a human should confirm whether the fix lands in `coily`, `infrastructure/ansible`, or both before an unattended push. No container was launched. Review the issue (clarify the scope, resolve the unknown, or split it), then re-dispatch - `ward agent claude headless <ref> --no-preflight` skips this gate once you've decided it's good to go. <details><summary>full pre-flight read</summary> PRE-FLIGHT read on infrastructure#246: I went looking for the hook on disk. The installed `.git/hooks/prepare-commit-msg` in the infrastructure checkout is the stock pre-commit dispatcher, and `coily-trailer` / `prepare-commit-msg` appear in **zero** tracked files across the local infrastructure, agentic-os, and agentic-os-kai checkouts. Per the repo's own authoring-vs-rollout doctrine, the hook is almost certainly **authored in the `coily` repo's `.pre-commit-hooks.yaml`** (not cloned here), while infrastructure would only carry the ansible/baseline rollout that fans it out - and I couldn't find that rollout reference in infra's `.pre-commit-config.yaml` either. The main risk is target ambiguity: the issue is filed against infrastructure, but the actual hook definition likely needs to be removed in the `coily` repo, and the rollout removal may live in an ansible baseline I couldn't locate from the issue text alone. An unattended run could clone `coily`, guess wrong, and push the removal to the wrong repo's `main` - a cross-repo fork that's annoying to unwind. That said, the change itself is small and reversible, so a few minutes of human confirmation on **which repo owns the fix** would de-risk it entirely. NO-GO: can't locate the `coily-trailer` hook definition in any local checkout - it likely lives in the un-cloned `coily` repo, so the correct merge target is unresolved and a human should confirm whether the fix lands in `coily`, `infrastructure/ansible`, or both before an unattended push. </details> --- Posted automatically by `ward agent claude headless` pre-flight (ward#147).