Development record
The ahoy install question that sets what a repository releases (artefact kind, .abcd/config/artefact.json) gives too little context and too few answers. Its whole explanation is 'What this repository releases; abcd's release commands refuse to guess it.', it offers only plugin, binary and application, and the default is explained as 'as binary today', which tells a person nothing about their own project. A website, a native desktop app, a mobile app or a library has no answer that fits, and nothing says what each choice changes in the release flow. Seen by the product thinker during abcd ahoy install in a downstream repository on v0.13.2, 2026-10-07 (Setup Q11).
The ahoy install question that sets what a repository releases (artefact kind, .abcd/config/artefact.json) gives too little context and too few answers. Its whole explanation is 'What this repository releases; abcd's release commands refuse to guess it.', it offers only plugin, binary and application, and the default is explained as 'as binary today', which tells a person nothing about their own project. A website, a native desktop app, a mobile app or a library has no answer that fits, and nothing says what each choice changes in the release flow. Seen by the product thinker during abcd ahoy install in a downstream repository on v0.13.2, 2026-10-07 (Setup Q11).
Frontmatter
| id | iss-2610071529246095 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | minor |
.abcd/work/issues/open/iss-2610071529246095-the-ahoy-install-question-that-sets-what.md
open on GitHub ↗ · commit history ↗