Development record
setup-question-budget
Summary
What spc-2610241007434505 did not deliver for itd-2610240823055889: criterion 5, the question budget. On a fresh account with the assistant's settings file present, setup asks the download, shell settings, commit checks, status line and identity questions plus one per missing tool. That is more than the four-plus-tools the criterion allows, because criterion 3 keeps the status line its own approved question and the commit-checks question was added after review (iss-2610241134315056). This spec holds until the product thinker rules on dcn-2610241228598485: count these in the budget, fold the status line into the download question, or move them onto the plan screen. It then brings the run within the ruled budget, with a test counting the questions a fresh account is asked.
Footprint
- packages: internal/core/ahoy, internal/surface/cli
- tests: internal/core/ahoy/question_budget_test.go
Steps
No steps listed: the spec is built as one step. To split it, list the steps in order as 1. <title>, each with - packages: and - tests: indented beneath it; - landed: <pull request or commit> marks a step that has landed.
Frontmatter
| id | spc-2610242112593216 |
|---|---|
| type | spec |
| lifecycle | open |
.abcd/development/specs/open/spc-2610242112593216-setup-question-budget.md
open on GitHub ↗ · commit history ↗
References1
- itd-2610240823055889Setting abcd up is short, plain, and finishesimplements
mentions4
- dcn-26102412285984852026-10-24 — Held for the product thinker: criteria 3 and 5 of itd-2610240823055889 conflict when the assistant's settings file exists. Criterion 3 makes the status line (the assistant's settings) its own person-approved question, and criterion 5 allows four questions (download, shell settings, plan, identity) plus one per tool, so a fresh account can be asked five. The build keeps the status-line question separate, the side on which nothing changes without a yes, and the spec close records criterion 5 as not met in that case until the product thinker rules: count the status line in the budget, fold it into the download question, or move it onto the plan screen.
- iss-2610241134315056ahoy install reports 'clean' in a clone whose committed hooks are not armed: in abcd's own checkout on 2026-10-24 the detection pass read banlist.hooks_path as 'unarmed' (core.hooksPath unset, so .githooks/pre-commit and pre-merge-commit never run) both before and after setup, yet no gap was listed and the install summary said 'abcd is set up in this repository'.
- iss-2611030744340532The board lists itd-2610240823055889 as next and ready ('implement against the spec body'), though its only open spec, spc-2610242112593216, says in its summary that it holds until the product thinker rules on dcn-2610241228598485; the hold is prose, so neither the board nor abcd build can see it, and a build would run against an unruled spec.
- spc-2610241007434505a-person-sets-abcd-up-in-a-repository-in