Development record
five delimiter-compare variants remain beside the canonical frontmatter.IsDelimiter: gate-side TrimSpace compares in lint and glossary accept an indented delimiter the canonical rule refuses, intent and changelog carry tolerant local copies, memory keeps its own close predicate, and site tests a bare HasPrefix — one consolidation pass onto the canonical predicate closes the family
five delimiter-compare variants remain beside the canonical frontmatter.IsDelimiter: gate-side TrimSpace compares in lint and glossary accept an indented delimiter the canonical rule refuses, intent and changelog carry tolerant local copies, memory keeps its own close predicate, and site tests a bare HasPrefix — one consolidation pass onto the canonical predicate closes the family Re-verification note: a record whose block is closed only by a mid-file ZWNBSP delimiter is capture-refused but frontmatter.Fields-green, and no lint rule runs the strict ledger parser — record-lint passes what capture refuses until the consolidation lands.
Grounds
- pursued: every reader of a record's frontmatter judges its delimiters by one rule, so a gate and its reader read the same block; a committed record whose block closes differently to a gate than to Fields, or a new private three-dash compare that the detector does not name, would show it wrong
Frontmatter
| id | iss-2608270908348042 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | minor |
.abcd/work/issues/resolved/iss-2608270908348042-five-delimiter-compare-variants-remain.md
open on GitHub ↗ · commit history ↗
mentions1
- iss-2608301908288212four nits from the itd-179 fix delta review including a body line offset that is one ahead of the rendered body