mirror of
https://github.com/EveryInc/compound-engineering-plugin.git
synced 2026-10-01 18:58:38 +02:00
Trevin Chow
f848177b8f
Per the validator's own docstring its scope is silent corruption — values that strict YAML parsers misread without raising — but the leading reserved-indicator check (`*`, `&`, `!`, `|`, `>`, `%`, `@`, `` ` ``) was catching the loud-error class instead. Those characters either parse with a different intent than the author meant (anchor declaration, alias reference, tag) or trigger explicit parser failures, which downstream parsers already surface. The validator's job is the bug class downstream parsers DON'T surface (silent truncation, silent restructuring), not lint. Background: this check was added speculatively, by extrapolating from the YAML 1.2 reserved-indicator list rather than from observed bugs. Subsequent review rounds had to walk back the `-` and `?` cases (Codex flagged them as YAML-spec-incorrect — both only act as markers when followed by whitespace). The exercise shows the check was reaching beyond the evidence-based scope. What's gone: - The unconditional first-character-against-tuple check - Its dedicated test case - Mention of reserved indicators in the docstring What stays (the actual evidence-based bug class): - Frontmatter delimiter line matching (catches `----` / `---extra` / missing closer / missing opener) - ` #` substring → silent comment truncation (the original Codex bug) - `: ` substring → silent mapping confusion (the plan-doc title bug) Tests: 939/939 pass. release:validate clean.