Development record
Uppercase YAML null spellings unrecognised by the null predicates (reported as GitHub #290)
Uppercase YAML null spellings unrecognised by the null predicates (reported as GitHub #290)
Retroactive capture of the bug reported as GitHub #290 so the ledger holds
the handle the CHANGELOG entry should cite: frontmatter.IsNull and lint's
isNull recognised null and ~ but not the YAML 1.2 core-schema
spellings Null/NULL, so records using an uppercase null were misread
(e.g. a superseded ADR's superseded_by: treated as a live handle). Fixed
in flight by PR #294, which widens both predicates with regression tests;
resolve this issue when that PR merges, citing its commit. Evidence:
.abcd/work/reviews/2026-08-19-pr-294-null-predicate/ (F10).
Forge mirror: #374
Frontmatter
| id | iss-287 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | major |
.abcd/work/issues/resolved/iss-287-uppercase-yaml-null-spellings.md
open on GitHub ↗ · commit history ↗
mentions1
- itd-128One canonical YAML scalar resolver: frontmatter exports the single null/bool/quote resolution helper and the capture, lint, lifeboat, and memory decoders all delegate to it, so a cross-package verdict split on any scalar axis becomes unrepresentable