From 2578e342cfed24df1bd5c800470358efad73637b Mon Sep 17 00:00:00 2001 From: Lilleman auf Larv Date: Thu, 3 Sep 2026 17:52:31 +0200 Subject: [PATCH] 5b2: tick the item and move its text to the history --- todo-history.md | 15 +++++++++++++++ todo.md | 10 +--------- 2 files changed, 16 insertions(+), 9 deletions(-) diff --git a/todo-history.md b/todo-history.md index 9e94390..bee35af 100644 --- a/todo-history.md +++ b/todo-history.md @@ -412,3 +412,18 @@ Under **3 — `markdownToAdf` (`0.1.0`)**: `unsupported-node-shape` stays one code across the two directions, `unmappable-html` names the version rather than the element, and a direction that reads a source returns the narrowed error type. + - [x] **5b2 — The error messages.** Most state the rule and leave the violation to be inferred — + `a text node holds text` for a node holding none — so `rule: violation` becomes house style + across the sites that do. `not-an-adf-document` gives one sentence of eight words to `null`, + a string, a missing `version`, a `type` that is not `doc` and a REST envelope around the + document; naming the check that failed makes the highest-frequency integrator mistake + self-diagnosing without the library naming a REST shape (§7). The three carve-out claim + messages name the escape that unclaims the line — `\|`, `\~~`, `\:::` — which today only + `spec/flavour.md` holds. `unmappable-html` reads as §8 now frames it: this version converts + no raw HTML, never a permanent judgment on the element. + Thirty-odd sites gained the violation clause and §8 gained the house style. `isAdfDocument` + parts into `adfDocumentFault`, the guard reading it, so the first failing check is the + message — the wrapper mistake names the key it found. Two carve-outs claim a line, not + three: a matched `~~` pair spells `strike` silently, so nothing refuses it and no message + names `\~~`; the escape lands on the directive-line and pipe-table refusals a prose line + hits. `a pipe table row holds 1 cells` gained its plural. diff --git a/todo.md b/todo.md index 0171392..60e23b0 100644 --- a/todo.md +++ b/todo.md @@ -146,15 +146,7 @@ The numbering is the order the work was planned in, not the order it ships. 5 because §8 freezes the code list at `0.1.0` and 5b3's table is what reads the list before the freeze closes it. - [x] **5b1 — The error's source position.** - - [ ] **5b2 — The error messages.** Most state the rule and leave the violation to be inferred — - `a text node holds text` for a node holding none — so `rule: violation` becomes house style - across the sites that do. `not-an-adf-document` gives one sentence of eight words to `null`, - a string, a missing `version`, a `type` that is not `doc` and a REST envelope around the - document; naming the check that failed makes the highest-frequency integrator mistake - self-diagnosing without the library naming a REST shape (§7). The three carve-out claim - messages name the escape that unclaims the line — `\|`, `\~~`, `\:::` — which today only - `spec/flavour.md` holds. `unmappable-html` reads as §8 now frames it: this version converts - no raw HTML, never a permanent judgment on the element. + - [x] **5b2 — The error messages.** - [ ] **5b3 — The README's consumer surface.** §8 invites an exhaustive switch on `code` and no code name appears in the README, so it gains a table — code, when it fires, what the consumer does — grouped by direction; drafting it is the audit that reads the fifteen names