Development record
The 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).
issueresolvedminoriss-2610111759346608
The 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).
Grounds
- pursued: we expect abcd itd-N and abcd intent ready to agree on every planned intent; a planned intent with an open question whose itd-N page still says implement, or a ready intent whose page withholds implement, would show it wrong
Frontmatter
| id | iss-2610111759346608 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | minor |
.abcd/work/issues/resolved/iss-2610111759346608-the-abcd-itd-n-dispatcher-computes-a.md
open on GitHub ↗ · commit history ↗
mentions2
- iss-2610101610446956abcd intent ready reported itd-82 READY while abcd build itd-82 refused it at check (open_questions) for two open questions in its record: the readiness verb does not run the check the build makes, so READY does not mean the build will start.
- iss-2610112214150230The 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.