Development record
body-prose record-id references resolve against nothing: the context_citation_currency rule's record_stores mapping covers one file, and the site record export extracts only the eight typed frontmatter edges, so adr-N/itd-N/spc-N/iss-N tokens in body prose across the durable record are checked by no gate (the mechanism behind this review's dangling-id findings). Widen the existing gate rather than adding a second: extend the export's reference extraction to body-prose tokens, flow them into the same Unresolved set and site-baseline ratchet, and seed the baseline with the first run's backlog.
body-prose record-id references resolve against nothing: the context_citation_currency rule's record_stores mapping covers one file, and the site record export extracts only the eight typed frontmatter edges, so adr-N/itd-N/spc-N/iss-N tokens in body prose across the durable record are checked by no gate (the mechanism behind this review's dangling-id findings). Widen the existing gate rather than adding a second: extend the export's reference extraction to body-prose tokens, flow them into the same Unresolved set and site-baseline ratchet, and seed the baseline with the first run's backlog.
Grounds
- pursued: every markdown file under .abcd/development is read for prose citations; an invented id in a brief chapter or principle that record-lint does not report would show it wrong
Frontmatter
| id | iss-2608271804497247 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | minor |
.abcd/work/issues/resolved/iss-2608271804497247-body-prose-record-id-references-resolve.md
open on GitHub ↗ · commit history ↗