Development record
the refusal tells an issue author the record is skipped by every issue surface while the changelog derivation reads resolved records leniently
the refusal tells an issue author the record is skipped by every issue surface while the changelog derivation reads resolved records leniently
Found by the itd-189 fix-delta ruthless review. PRE-EXISTING text; the delta rewrote this line's tail and re-blessed the clause, which is why it is captured now.
The refusal branch tells an issue author the file "is skipped by every issue
surface". capture's scanLedger does route it to Skipped -- but the
changelog derivation does not. changelog/shipped.go's newRecord reads the
same file with frontmatter.Fields, first-wins, and folds its title, summary,
shipped_in and impact into the release cut.
So an author told the record is invisible everywhere finds it in the generated CHANGELOG section. Same class as the record this delta was closing, one surface further out, and it is the reason the remedy on iss-2608301901264848 is to make such claims executable rather than to keep narrowing them by hand.
Frontmatter
| id | iss-2608301901260678 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | minor |
.abcd/work/issues/resolved/iss-2608301901260678-the-refusal-tells-an-issue-author-the.md
open on GitHub ↗ · commit history ↗
mentions2
- iss-2608301901264848the nine store enumeration checked one reader per store so rdi and dsp are assigned an answer their second reader contradicts
- itd-189What the widening reading proposes is admitted or declined on the record — grounds on admission, dispositions on declines, and surprises as their own entries