Development record
commands/prepare-this-repo.md tells every prepared repository to run git config core.hooksPath .githooks with no condition, which shadows a global hooks dispatcher: the exact advice ahoy's status now refuses to give when hooks_path is foreign.
issueresolvedminoriss-2610080546210831
commands/prepare-this-repo.md tells every prepared repository to run git config core.hooksPath .githooks with no condition, which shadows a global hooks dispatcher: the exact advice ahoy's status now refuses to give when hooks_path is foreign.
Grounds
- pursued: prepare-this-repo never advises a local core.hooksPath unless ahoy reports hooks_path unarmed; shown wrong if the arming command appears outside the unarmed branch, the foreign branch stops pointing at the dispatcher, or banlist.hooks_path stops being the field ahoy emits, any of which fails TestPrepareThisRepoArmsHooksOnlyWhenUnarmed or TestPrepareHooksPathFieldIsWhatAhoyEmits
Frontmatter
| id | iss-2610080546210831 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | minor |
.abcd/work/issues/resolved/iss-2610080546210831-commands-prepare-this-repo-md-tells.md
open on GitHub ↗ · commit history ↗
mentions1
- iss-2610101900387053A drain opens a full lane on an issue whose fix has already landed under another issue's id. On 2026-10-10 the drain took iss-2610080546210831 (prepare-this-repo's unconditional core.hooksPath step); commit afa6e7b16 had already made that step conditional while citing iss-2610081312364884, so the record stayed open. The lane spent about 35 minutes and 92k tokens to find nothing to fix, then added a guard test so the landing could resolve it. Neither the dry run nor abcd capture mentions sees this, because the fixing commit names a different issue.