Check in the CommonMark spec suite and pin its exception list
CI / gate (push) Successful in 19s
CI / publish (push) Has been skipped

This commit is contained in:
2026-09-05 18:56:28 +02:00
parent 026ea5e1b6
commit e6610d7057
7 changed files with 5847 additions and 5 deletions
+9 -1
View File
@@ -12,5 +12,13 @@ One directory per contract kind, each landing with its milestone:
pins which error.
- `real-payloads/``<name>.json`: sanitized live ADF, round-tripped ADF→markdown→ADF. No
expected markdown.
- `commonmark-spec/``spec.json` (the pinned CommonMark suite, read as corpus data per
AGENTS.md §1) and `exceptions.json` (examples a documented divergence exempts, keyed by
`check` and `example` with a `reason`). Three checks an example must pass: the §2 canonical
fixpoint — a named error, or markdown that parses and emits back to itself; the reference HTML's
text, tags stripped and entities decoded, against the parsed document's concatenated text; and a
count of the CommonMark subset's elements against the nodes and marks they map to.
JSON is editor-normal (AGENTS.md §2), two-space indent, keys sorted.
JSON is editor-normal (AGENTS.md §2), two-space indent, keys sorted. `spec.json` is the vendored,
upstream machine-readable suite (CommonMark 0.31.2, CC-BY-SA-4.0, © John MacFarlane) and is not
re-serialized by the corpus gate.