Development record
Two pre-existing gate-versus-reader divergences reproduced on main, not introduced by the lapsed_at work: the record-lint issueScalar strips quotes with strings.Trim and never unescapes, so a double-quoted value carrying a backslash escape is lint-red while the reader decodes it (severity: "min\or" reproduces it); and a key line led by a Unicode space is ignored by frontmatter keyRe but read by capture after TrimSpace, so a Unicode-space-led bogus key is lint-green while the reader refuses and skips the record. The first shares its root with iss-2608300205044566 and should fold into it; the second applies to every key.
Two pre-existing gate-versus-reader divergences reproduced on main, not introduced by the lapsed_at work: the record-lint issueScalar strips quotes with strings.Trim and never unescapes, so a double-quoted value carrying a backslash escape is lint-red while the reader decodes it (severity: "min\or" reproduces it); and a key line led by a Unicode space is ignored by frontmatter keyRe but read by capture after TrimSpace, so a Unicode-space-led bogus key is lint-green while the reader refuses and skips the record. The first shares its root with iss-2608300205044566 and should fold into it; the second applies to every key.
Grounds
- pursued: record_schema and capture's ledger reader give one verdict on every committed issue record; a record capture list skips that record-lint passes, or the reverse, would show it wrong
Frontmatter
| id | iss-2608300234598982 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | minor |
.abcd/work/issues/resolved/iss-2608300234598982-frontmatter-scanner-and-reader-disagree.md
open on GitHub ↗ · commit history ↗
mentions2
- iss-2608300205044566The committed-ledger gate and the ledger reader disagree on single-quoted scalars: issueScalar in the record-lint issue-shape check strips single quotes, capture's decodeScalar does not, so a hand-authored single-quoted value (severity: 'minor', lapsed_at: '2026-08-28T00:00:00Z') is lint-green while the reader refuses and skips the record invisibly. Pre-existing on unmodified code; every issue-shape check that reads a scalar inherits it, so the fix belongs in issueScalar and moves four checks at once.
- iss-2608301206074955an indented continuation under a valued frontmatter key skips the record in every reader while record_schema reports nothing