Development record
2026-09-30 — The person's ruling CM1 of 2026-09-29 ("'step' in implement check: RENAME it to 'stage' too, in the same breaking v0.12.0"; kept verbatim in the local-tier file `.abcd/.work.local/scratch/reports/rulings-answered-2609-29-b.md` and restated here because that file is not committed) is applied by autonomous run A's integration lane integ24b1, answering iss-2609292359485570: `implement check` calls what a session asks about a stage, so its verdict's JSON field and its refusal line's field are `stage` (were `step`), its text says `may take the <stage> stage`, an operand outside lane, release, review, audit and land is refused as an unknown stage, and its help, sentence, command page and brief chapter say stage. The operands keep their spellings. The upgrade guide `docs/how-to/upgrade-to-v0.12.0.md` lists both renamed fields. The 'point' spelling the capture's remedy offered was not chosen: CM1 names 'stage'.
2026-09-30 — The person's ruling CM1 of 2026-09-29 ("'step' in implement check: RENAME it to 'stage' too, in the same breaking v0.12.0"; kept verbatim in the local-tier file .abcd/.work.local/scratch/reports/rulings-answered-2609-29-b.md and restated here because that file is not committed) is applied by autonomous run A's integration lane integ24b1, answering iss-2609292359485570: implement check calls what a session asks about a stage, so its verdict's JSON field and its refusal line's field are stage (were step), its text says may take the <stage> stage, an operand outside lane, release, review, audit and land is refused as an unknown stage, and its help, sentence, command page and brief chapter say stage. The operands keep their spellings. The upgrade guide docs/how-to/upgrade-to-v0.12.0.md lists both renamed fields. The 'point' spelling the capture's remedy offered was not chosen: CM1 names 'stage'.
Frontmatter
| id | dcn-2609300000000007 |
|---|---|
| type | decision |
| date | 2026-09-30 |
.abcd/work/decisions/dcn-2609300000000007-the-person-s-ruling-cm1-of-2026-09-29.md
open on GitHub ↗ · commit history ↗
mentions1
- iss-2609292359485570The shared run's bounds use 'step' for a third thing: abcd implement check <lane|release|review|audit|land> asks whether a session 'may take a step', its verdict carries the point under a JSON 'step' field (internal/core/implement/bounds.go, Step/StepLane/StepRelease/StepReview/StepAudit/StepLand), and commands/implement.md and brief 27-implement.md speak of 'the release step' and 'a step that is not a claim'. BU1 (2026-09-29) settled that in the build loop 'step' names a spec's piece and a lane's are stages; the check vocabulary, a point in a shared run where the second session's bounds are checked, was not in that ruling and still says step.