AGENTS.md

@@ -174,9 +174,9 @@ The verdict lands in `docs/decisions.md`.
 - A finding inside the chunk's item is fixed in the chunk. Outside it, a new `todo.md` item, always
   in a release, weighed against every item on that release by the personas and `docs/decisions.md`
   §Plain markdown is a flavour of the grammar through §Names stay text — an item it outweighs moves
-  later. A weighing no rule decides is asked as a gap.
+  later. A weighing no entry decides is asked as a gap.
 - A stated number — 500 levels, the branch floor — is kept; a chunk that cannot keep it asks,
-  naming the number it can reach. A number the code needs and no rule states is a gap.
+  naming the number it can reach. A number the code needs and no entry states is a gap.
 - An earliest release with no items left and nothing shipped toward it is planned as the chunk:
   every later item weighed as above, the order written in `todo.md`, and the maintainer's approval
   taken before any code. With work shipped toward it, it is ready to cut: report that and stop.

docs/decisions.md

@@ -51,22 +51,23 @@ a `codeBlock` outside text — the error result names that instead.
 
 ## Foreign HTML sorts three ways
 
-2026-08-23, the sort 2026-09-20, the maintainer. Goals 1 and 6. Valid while ADF holds no node for a
-bare container, a comment or a script.
+2026-08-23, the sort 2026-09-20, the maintainer. Goals 1, 3 and 6. Valid while ADF holds no node
+for a bare container, a comment or a script. Lands with `todo.md` 6.
 
 Every foreign element `htmlToAdf` and `markdownToAdf` read sorts one of three ways, never a silent
-drop of what a reader saw:
+drop of content:
 
 - A container around document content that ADF has no node for unwraps to its children, its own
-  attributes dropped: `<div align="center">text</div>` keeps `text`.
+  attributes dropped: `<div align="center">text</div>` keeps `text`, losing the alignment.
 - Content ADF cannot hold is an error result naming it. A comment is one: a person wrote those
   words, and neither of Atlassian's schemas holds them — `annotation`'s `inlineComment` carries an
   id, `placeholder` is the editor's own hint, `extension` names a vendor app.
 - What is not document content drops whole: `<script>` and `<style>`, their text with them.
 
-`<details><summary>Title</summary>…</details>` is an `expand` titled by its summary, a `nestedExpand`
-inside another; an empty one is refused, since `expand` requires content. A `style` attribute is not
-read at `0.2.0`: the `textColor` and `backgroundColor` it could reach cost more than they buy.
+`<details><summary>Title</summary>…</details>` is an `expand` titled by its summary, a
+`nestedExpand` inside another; an empty one is refused, since `expand` requires content. A `style`
+attribute is not read at `0.2.0`: the `textColor` and `backgroundColor` it could reach cost more
+than they buy.
 `plainMarkdownToAdf` reads through `markdownToAdf`'s parser, so it takes the same set.
 
 ## Names stay text
@@ -123,7 +124,7 @@ accepted.
 ## Plain task ids come from position
 
 2026-09-26, the maintainer. Goals 5 and 7. Valid while a site rejects a task node with no
-`localId`.
+`localId`. Lands with `todo.md` 10f.
 
 `plainMarkdownToAdf` gives each `taskList`, `taskItem` and `blockTaskItem` a `localId` from its
 position in document order, unique within the document and minted with no host API, so a site
@@ -505,8 +506,8 @@ is the markdown flavour's choice, not ADF's.
 
 ## The source parts by ADF and format
 
-2026-08-27, placement 2026-09-18, `adf/`'s bar 2026-09-21, the maintainer. Goal 2. Valid while each format has a reader
-and a writer through ADF.
+2026-08-27, placement 2026-09-18, `adf/`'s bar 2026-09-21, the maintainer. Goal 2. Valid while
+each format has a reader and a writer through ADF.
 
 `src/adf/` holds ADF's own knowledge, imports no format, and is where a construct both formats read
 lives: the question is answered in ADF's vocabulary — a node type, an attribute kind, a content

todo.md

@@ -10,7 +10,8 @@
   - **36e — Move `todo-history.md`'s decisions, re-point its citations and delete it.**
 - **35 — Read and write plain markdown as a flavour of the markdown grammar.** Per Goal 2 and
   `docs/decisions.md` §Plain markdown is a flavour of the grammar, 10's rows are read by
-  `markdownToAdf`'s parser and written by `adfToMarkdown`'s writer, and the lift goes. The exports, their refusals and 10's rows stay as they are.
+  `markdownToAdf`'s parser and written by `adfToMarkdown`'s writer, and the lift goes. The exports,
+  their refusals and 10's rows stay as they are.
   - **35a — Read the plain flavour in the parser and delete the lift.** 10's rows are read while
     parsing, and `plain-lift.ts` is deleted, its tests reading through `plainMarkdownToAdf`. `>
     [!faq]- Why?` with the body on the next `>` line reads to an expand titled `Why?` whose body