Redo .pre-commit-config.yaml Forgejo agentic-os migration (rev/hook-list mismatch broke the tree) #57

New issue

Closed

opened 2026-06-04 10:40:58 +00:00 by coilysiren · 0 comments

coilysiren commented

2026-06-04 10:40:58 +00:00

Owner

Summary

While landing coilysiren/website#1 (regenerate .claude/ lockdown), the canonical checkout (~/projects/coilysiren/website) carried an uncommitted, broken migration of .pre-commit-config.yaml's managed agentic-os block. I discarded it to unblock the fast-forward merge and am filing this so the migration is redone correctly. The discarded WIP is saved at /tmp/website-precommit-forgejo-wip.yaml on kais-macbook-pro (ephemeral).

What the WIP tried to do

Migrate the managed block from the GitHub mirror to canonical Forgejo:

repo: https://github.com/coilysiren/agentic-os -> https://forgejo.coilysiren.me/coilyco-flight-deck/agentic-os
rev: v0.6.0 -> rev: v0.13.1
Added hooks: context-load-points, repo-pointer-skills, misplaced-skills, agent-compose-size, agent-compose-dedup, trufflehog

Why it was broken

pre-commit run fails:

[ERROR] `agent-compose-size` is not present in repository https://forgejo.coilysiren.me/coilyco-flight-deck/agentic-os. Typo? Perhaps it is introduced in a newer version?

The hook list belongs to a newer Forgejo agentic-os tag than v0.13.1. Cached manifests confirm agent-compose-size, agent-compose-dedup, and agent-compose-drift exist only at a tag above v0.13.1 (the v0.13.1 manifest stops at misplaced-skills). So the rev and the hook list are mismatched - either the rev needs bumping to the tag that actually ships those hooks, or the unavailable hooks dropped.

Looks like automated repoint drift (cf. 77b3664 chore(repoint): rewrite coilysiren/<moved-repo> refs to new orgs) that bumped the URL + rev + hook list inconsistently.

What landed instead (#1)

The merged commit keeps the working managed block (github.com/coilysiren/agentic-os v0.6.0) and only removes the stale local coily-trailer hook (see below). The Forgejo migration is intentionally not part of #1.

Bonus finding: stale `coily-trailer` hook

The repo's local coily-trailer prepare-commit-msg hook called coily git trailer-hook, which coily v2.53.0 removed (the auto Audit-log: trailer feature is replaced by the manual coily git audit-show query). It errored on every commit, blocking the tree. #1 removed it. When the managed-block migration is redone, confirm no managed coily-trailer hook is re-introduced against a coily that no longer provides trailer-hook.

Action

Redo the managed-block Forgejo migration with a consistent (rev, hook-list) pair: pick the Forgejo agentic-os tag that actually ships agent-compose-* and pin the rev to it, or trim the hook list to what v0.13.1 provides. Then pre-commit run --all-files must pass before committing.

## Summary While landing coilysiren/website#1 (regenerate `.claude/` lockdown), the canonical checkout (`~/projects/coilysiren/website`) carried an **uncommitted, broken** migration of `.pre-commit-config.yaml`'s managed agentic-os block. I discarded it to unblock the fast-forward merge and am filing this so the migration is redone correctly. The discarded WIP is saved at `/tmp/website-precommit-forgejo-wip.yaml` on kais-macbook-pro (ephemeral). ## What the WIP tried to do Migrate the managed block from the GitHub mirror to canonical Forgejo: - `repo: https://github.com/coilysiren/agentic-os` -> `https://forgejo.coilysiren.me/coilyco-flight-deck/agentic-os` - `rev: v0.6.0` -> `rev: v0.13.1` - Added hooks: `context-load-points`, `repo-pointer-skills`, `misplaced-skills`, `agent-compose-size`, `agent-compose-dedup`, `trufflehog` ## Why it was broken `pre-commit run` fails: ``` [ERROR] `agent-compose-size` is not present in repository https://forgejo.coilysiren.me/coilyco-flight-deck/agentic-os. Typo? Perhaps it is introduced in a newer version? ``` The hook list belongs to a **newer** Forgejo agentic-os tag than `v0.13.1`. Cached manifests confirm `agent-compose-size`, `agent-compose-dedup`, and `agent-compose-drift` exist only at a tag above `v0.13.1` (the `v0.13.1` manifest stops at `misplaced-skills`). So the rev and the hook list are mismatched - either the rev needs bumping to the tag that actually ships those hooks, or the unavailable hooks dropped. Looks like automated repoint drift (cf. `77b3664 chore(repoint): rewrite coilysiren/<moved-repo> refs to new orgs`) that bumped the URL + rev + hook list inconsistently. ## What landed instead (#1) The merged commit keeps the **working** managed block (`github.com/coilysiren/agentic-os` `v0.6.0`) and only removes the stale local `coily-trailer` hook (see below). The Forgejo migration is intentionally **not** part of #1. ## Bonus finding: stale `coily-trailer` hook The repo's local `coily-trailer` `prepare-commit-msg` hook called `coily git trailer-hook`, which **coily v2.53.0 removed** (the auto `Audit-log:` trailer feature is replaced by the manual `coily git audit-show` query). It errored on every commit, blocking the tree. #1 removed it. When the managed-block migration is redone, confirm no managed `coily-trailer` hook is re-introduced against a coily that no longer provides `trailer-hook`. ## Action Redo the managed-block Forgejo migration with a consistent (rev, hook-list) pair: pick the Forgejo agentic-os tag that actually ships `agent-compose-*` and pin the rev to it, or trim the hook list to what `v0.13.1` provides. Then `pre-commit run --all-files` must pass before committing.

coilysiren added the

priority

label

2026-06-17 08:39:56 +00:00