4c - the scanning rule's remaining sites #99

2026-09-18T19:42:54+02:00

lilleman commented

2026-09-18 19:42:54 +02:00

Five scan sites that re-walked their input. The label trim, the inline segment's trailing trim, the list-item walk's thematic-break question and the nested directive scan all became linear; the document guard's spread became a loop, so a wide document returns a Result instead of throwing.

The sixth site 4c filed - the parser asking commonMarkSpelling at every directive-spelled block - is now item 18, its measurements and the depth disagreement behind it recorded there.

Five scan sites that re-walked their input. The label trim, the inline segment's trailing trim, the list-item walk's thematic-break question and the nested directive scan all became linear; the document guard's spread became a loop, so a wide document returns a Result instead of throwing. The sixth site 4c filed - the parser asking commonMarkSpelling at every directive-spelled block - is now item 18, its measurements and the depth disagreement behind it recorded there.

lilleman marked the pull request as ready for review 2026-09-18 20:03:36 +02:00

lilleman added 7 commits 2026-09-18 20:05:09 +02:00

4c - the label trim, the segment tail, the break run and the guard's spread stop re-walking 503efa4f82

4c - the directive scan keeps the spans it read, so the slot parse never scans them again 7b726ef6ec

Tick 4c, moving its text to todo-history.md and filing its last site as 18 a774be59f4

One release for everything known: 0.2.1 and 0.3.0 fold into 0.2.0 047ce3bc42

4c - the guard's spread was a class: the code block's held lines and a mark run's segments too 0361646e1a

Restore the list-item walk's three re-scans in 4c's record, and what became of each dfc91a651b

Point the next session at 14, and at a fetch before branching

CI / gate (push) Successful in 36s

Details

CI / publish (push) Successful in 5s