Development record
the private name-guard blocks every commit touching ACKNOWLEDGEMENTS.md because a pre-existing citation in HEAD matches an unanchored pattern; two credits (the layout algorithm, the screenshot tooling) are held as local patches until the anchoring fix lands
issuewontfixmajoriss-2608221342509869
the private name-guard blocks every commit touching ACKNOWLEDGEMENTS.md because a pre-existing citation in HEAD matches an unanchored pattern; two credits (the layout algorithm, the screenshot tooling) are held as local patches until the anchoring fix lands
Frontmatter
| id | iss-2608221342509869 |
|---|---|
| type | issue |
| lifecycle | wontfix |
| severity | major |
.abcd/work/issues/wontfix/iss-2608221342509869-the-private-name-guard-blocks-every.md
open on GitHub ↗ · commit history ↗
References1
- iss-2608220150157507The machine-local private name-guard blocked a commit on the entry its hook reports as entry-14: the unanchored pattern matches inside an unrelated academic author's surname in rendered bibliography content (the site prototype), a false positive that keeps the behavioural spec out of the shared tree. The fix site is the generator, not the file: the pattern sits inside the generated abcd-sources block of the private-names store ("do not edit between markers" — a hand-anchored edit is overwritten by the next sources sync), so the sources-sync that emits the block must word-boundary-anchor every short name pattern it writes at emit time. Until that ships the prototype lives in the local scratch tier and the plan documents the detour (decision confirmed 2026-08-22: status quo, no guard weakening, no hand-edits to the generated block; the prototype is committed into research/abcdev-site/ in a follow-up once the anchoring lands). Fix the detector, not the findingblocked by