Development record
The abcd spc-N page (describeSpec in internal/core/record/record.go) and a bundle's shared-spec page (describeBundleSpec) judge the spec's intent, or each live bundle member, with plain intent.Ready, so for an intent whose ## Open Questions still lists an unanswered item they say 'implement against this spec's body; when done, abcd spec close ...' while abcd itd-N, abcd intent ready and abcd build all say it is not ready. Confirmed for describeSpec by a scratch-repository run in the lane for iss-2610111759346608; describeBundleSpec by reading the code.
issueresolvedminoriss-2610112214150230
The abcd spc-N page (describeSpec in internal/core/record/record.go) and a bundle's shared-spec page (describeBundleSpec) judge the spec's intent, or each live bundle member, with plain intent.Ready, so for an intent whose ## Open Questions still lists an unanswered item they say 'implement against this spec's body; when done, abcd spec close ...' while abcd itd-N, abcd intent ready and abcd build all say it is not ready. Confirmed for describeSpec by a scratch-repository run in the lane for iss-2610111759346608; describeBundleSpec by reading the code.
Grounds
- pursued: abcd spc-N for an open spec whose intent (or any live bundle member) lists an unanswered open question says 'not ready' and names abcd intent ready for that intent; it would be shown wrong by such a page still saying 'implement against this spec's body' (pinned by TestDescribeSpecOpenQuestionsWithholdsImplement and TestDescribeBundleSpecOpenQuestionMemberWithholdsImplement).
Frontmatter
| id | iss-2610112214150230 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | minor |
.abcd/work/issues/resolved/iss-2610112214150230-the-abcd-spc-n-page-describespec-in.md
open on GitHub ↗ · commit history ↗
mentions1
- iss-2610111759346608The abcd itd-N dispatcher computes a planned intent's next move from plain intent.Ready, so for a planned intent whose ## Open Questions still lists an unanswered item it says 'ready — implement against the spec body', while abcd intent ready reports NOT READY (open_questions) and abcd build refuses at check (open_questions). Found by the ruthless review of run-2610111657111142 lane-1 (iss-2610101610446956).