Development record
itd-180 review residue: capture.standingDispositions and lint.standingDisposition read the standing disposition with different parsers (strict with a continue before the supersedes edge is read; lenient reading the edge always) and no test holds them to one answer, so a malformed sibling disposition makes the board and the verb disagree; at ingest, manifest and regime are written verbatim without redaction or an enum check (harmless until a door lands); promote accepts a rejected or declined reading item; a mid-batch I/O failure leaves earlier items written with no result list; the lint import grouping in lint.go differs from goimports order; IssueStatus carries a disposition state outside the State enum for reading items.
itd-180 review residue: capture.standingDispositions and lint.standingDisposition read the standing disposition with different parsers (strict with a continue before the supersedes edge is read; lenient reading the edge always) and no test holds them to one answer, so a malformed sibling disposition makes the board and the verb disagree; at ingest, manifest and regime are written verbatim without redaction or an enum check (harmless until a door lands); promote accepts a rejected or declined reading item; a mid-batch I/O failure leaves earlier items written with no result list; the lint import grouping in lint.go differs from goimports order; IssueStatus carries a disposition state outside the State enum for reading items.
Frontmatter
| id | iss-2608300227226804 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | minor |
.abcd/work/issues/resolved/iss-2608300227226804-itd-180-review-residue.md
open on GitHub ↗ · commit history ↗
mentions1
- itd-180A cold reading's findings land as reading records, and the researcher's response is a separate disposition record — two acts, two writes, never collapsed