Answer product-owner round 1: 0 🔴, 4 🟡 (0 misread); keep unreleased calls out of the Breaking entries and sharpen the feature page's intro

docs/decisions.md

@@ -463,8 +463,7 @@ and `<span … data-data>` 2. The maintainer took the leading spelling of each,
 - a mention is `<span class="adf-mention" data-access-level="CONTAINER" data-id="5b10a2" data-user-type="DEFAULT">@Mikael</span>`, its `text` the content;
 - a card holding `data` and no URL is `<a class="adf-inline-card" href="https://example.com/plan" data-data="{…}">Release plan</a>`, `href` the URL its `data` holds and the text its name, else that URL. A card holding both `data` and a `url` rides the carry: its `href`, read back, could not say which of the two URLs it spells.
 
-A sixth panel (2026-11-05, three readers in the same roles) picked each of these 3 of 3 for a table,
-which until then rode the carry:
+A sixth panel (2026-11-05, three readers in the same roles) picked each of these 3 of 3 for a table:
 
 - a first row of header cells alone in `<thead>` and the rest in `<tbody>`, a row to a line, over a
   bare `<table>` of `<tr>` rows and over a line per cell;
@@ -472,9 +471,6 @@ which until then rode the carry:
 - a cell's attributes as `<td colspan="2" rowspan="2" style="background-color:#fffae6" data-colwidth="120,80">`,
   over `data-*` for all four.
 
-A `background` holding anything but letters and digits after an optional `#` rides the carry, so no
-value can end the `style` declaration.
-
 ## `htmlToAdf` also reads the dialect as a browser serializes it
 
 2026-10-28, the maintainer. Goal 6. Valid while a viewer/editor app may show `adfToHtml`'s HTML in a
@@ -773,8 +769,9 @@ writer refuses alike, with one code, message and path, wherever the shape stands
 too, and a carry reader refuses it with the same code and the writers' message after its holder's
 name. The first step refuses an `inlineCard` with a `link` mark as `unsupported-node-shape`: the
 schema gives a card the `annotation` mark alone (§The node tables answer to Atlassian's schema),
-and HTML nests no `<a>` in an `<a>`. It also refuses a block or non-text inline node holding `text`,
-and a leaf block or non-text inline node holding a non-empty `content`.
+and HTML nests no `<a>` in an `<a>`. The first step also refuses a known block holding `text`, a
+known non-text inline node holding `text` or non-empty `content`, and a known block that takes no
+content holding non-empty `content`.
 
 Nothing else joins the first step. Nothing refuses a node type, mark or attribute the schema does
 not name (§Unknown nodes ride the carry), a known node where no section spells it, or a mark a node

docs/feature-table.md

@@ -1,8 +1,10 @@
 # What each call writes
 
-`feature-table/build.mjs` writes this page from the corpus and the built package, and `./ci.sh` fails where the page differs.
+Each section sets a sample ADF document beside what each call writes for it, then reads that output back: `adfToLosslessMarkdown` with `losslessMarkdownToAdf`, `adfToPortableMarkdown` with `portableMarkdownToAdf`, `adfToHtml` with `htmlToAdf`. `holds` means the reader gives the same document, `loses` a different one, and `refused` that the writer or reader returned an error, whose code the section names.
 
-Each output is read back by its format's reader. `holds` means that gives the same document, `loses` a different one, and `refused` an error whose code the example names.
+A result covers that example alone, and the examples are plain. Portable markdown drops every attribute, so a document holding one loses it even where its row says `holds`: to edit and save back, use `adfToLosslessMarkdown` and `losslessMarkdownToAdf`. An image holding an attribute, as editor-written ones do, rides the carry element in HTML, where this page shows `<img>`.
+
+`./feature-table/write.sh` writes this page. Don't edit it by hand.
 
 | Example | Lossless | Portable | HTML |
 | --- | --- | --- | --- |