Development record
The reading floor admits a YAML alias used as a key in a frontmatter block, so an excluded key travels past the redaction under a manifest asserting its refusal. `k: &a origin` followed by `*a : X` (or `m: {*a : X}`) is admitted, and a YAML reader resolves it to {origin: X}. The anchor refusal in unresolvableFrontmatterShape fires only at line start or after a block indicator (nestedBlockEntry); an anchor in value or flow position is admitted, and nothing inspects `*` at all. Same class as iss-2608301237450573.
issueresolvedminoriss-2609261900095459
The reading floor admits a YAML alias used as a key in a frontmatter block, so an excluded key travels past the redaction under a manifest asserting its refusal. k: &a origin followed by *a : X (or m: {*a : X}) is admitted, and a YAML reader resolves it to {origin: X}. The anchor refusal in unresolvableFrontmatterShape fires only at line start or after a block indicator (nestedBlockEntry); an anchor in value or flow position is admitted, and nothing inspects * at all. Same class as iss-2608301237450573.
Grounds
- pursued: every alias-as-key shape the review named and its siblings (flow continuation, tag, CRLF, anchors in flow and after a tag) is refused while a value alias and a harmless merge are admitted, and detection/widening/entailment dry-run assemblies keep 394/336/237 items and assembler_version 1.8.0+3c58dd; a YAML reader resolving an admitted frontmatter to an origin key would show it wrong
Frontmatter
| id | iss-2609261900095459 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | minor |
.abcd/work/issues/resolved/iss-2609261900095459-the-reading-floor-admits-a-yaml-alias.md
open on GitHub ↗ · commit history ↗
mentions1
- iss-2608301237450573pre-existing on the itd-183 branch: a compact nested mapping in a block sequence leaks an excluded key, and rawHTMLHeading's fence comment overclaims