This repository's committed pre-commit guard refreshes the sources corpus's generated banlist block with an INSTALLED abcd (the pinned PATH, then ~/.local/bin), which in this source checkout is the last release and stale by construction, against the dogfooding rule and against the commit-msg hook, which builds ./cmd/abcd from the checkout. The guard should build the checkout's own abcd the way commit-msg does, print one warning line and proceed when the build fails, and never resolve an installed binary.

This repository's committed pre-commit guard refreshes the sources corpus's generated banlist block with an INSTALLED abcd (the pinned PATH, then ~/.local/bin), which in this source checkout is the last release and stale by construction, against the dogfooding rule and against the commit-msg hook, which builds ./cmd/abcd from the checkout. The guard should build the checkout's own abcd the way commit-msg does, print one warning line and proceed when the build fails, and never resolve an installed binary.

Grounds

• pursued: a commit in this checkout refreshes the block with the checkout's own verb; an installed abcd being run, or a build failure blocking or going unsaid, would show it wrong