Development record
abcd guard question's text render can contradict its own findings list. Take any draft whose only findings are non-refusing structure findings, for example an --ask draft with a valid chip but no id, or a duplicate id or option value. The input composed for the hook is clean. If the mode store or the away record cannot be read as well, the text prints 'this question was checked and has no finding, but …' and, a few lines later, 'findings: 1, 0 of them refusing'. The JSON and the exit code (2) are correct, so this is the text render's wording alone. The line comes from step 2 of spc-2610301950037469 (PR #1333), in internal/surface/cli/guard_question_verb.go. It was found by that lane's delta review on 2026-11-01.
abcd guard question's text render can contradict its own findings list. Take any draft whose only findings are non-refusing structure findings, for example an --ask draft with a valid chip but no id, or a duplicate id or option value. The input composed for the hook is clean. If the mode store or the away record cannot be read as well, the text prints 'this question was checked and has no finding, but …' and, a few lines later, 'findings: 1, 0 of them refusing'. The JSON and the exit code (2) are correct, so this is the text render's wording alone. The line comes from step 2 of spc-2610301950037469 (PR #1333), in internal/surface/cli/guard_question_verb.go. It was found by that lane's delta review on 2026-11-01.
Frontmatter
| id | iss-2611011943547454 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | nitpick |
.abcd/work/issues/open/iss-2611011943547454-abcd-guard-question-s-text-render-can.md
open on GitHub ↗ · commit history ↗
mentions2
- dcn-26110119440396012026-11-01 — Land PR #1333 (step 2 of spc-2610301950037469) with iss-2611011943547454 open rather than fixing it first. The finding is one sentence in abcd guard question's text render; the JSON and the exit code are correct. It shows only when a draft's only findings are non-refusing structure findings while a store cannot be read. A fix now would cost another full preflight and review round, at one to two hours each, on a machine whose load the product thinker has made the first priority. The fix goes to a drain lane: the issue is a nitpick inconsistency with found_at internal/surface/cli/guard_question_verb.go, which the drain can reserve and fix.
- spc-2610301950037469A repository sets the layout limits of abcd's questions