Development record
During abcd ahoy install, each category approval (Setup Q1 to Q5 in a managed repository, e.g. 'Apply conventions-file changes?') is asked with nothing but that one line: apply.go composes the question as "Apply " + category + " changes?" and the setup question carries no material, while its Yes option says it 'Writes what the text above describes.' There is no text above, so the person approves file writes without seeing which files change or how; the category name itself (conventions-file, git-hooks, ...) is an internal word. Seen 2026-10-07 by the product thinker in a downstream repository on v0.13.2 (screenshot: five approvals answered 'Yes, make the change' with no list shown).
During abcd ahoy install, each category approval (Setup Q1 to Q5 in a managed repository, e.g. 'Apply conventions-file changes?') is asked with nothing but that one line: apply.go composes the question as "Apply " + category + " changes?" and the setup question carries no material, while its Yes option says it 'Writes what the text above describes.' There is no text above, so the person approves file writes without seeing which files change or how; the category name itself (conventions-file, git-hooks, ...) is an internal word. Seen 2026-10-07 by the product thinker in a downstream repository on v0.13.2 (screenshot: five approvals answered 'Yes, make the change' with no list shown).
Frontmatter
| id | iss-2610071528375981 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | major |
.abcd/work/issues/resolved/iss-2610071528375981-during-abcd-ahoy-install-each-category.md
open on GitHub ↗ · commit history ↗