Answer product-owner round 1: 0 🔴, 1 🟡 (0 misread); tell a caller who only holds the ADF to keep it read-only, and give the real reason

CHANGELOG.md

@@ -17,8 +17,8 @@
   `localId` as `data-local-id`. Every other node is an element of class `adf-carry` holding the
   node's JSON in `data-adf` and showing its content, links included. Every URL is written as the
   ADF holds it, `javascript:` included: sanitize HTML from an author you do not trust before
-  showing it. It refuses an inline card a link marks, which Atlassian's schema does not allow, as
-  `unsupported-node-shape`.
+  showing it. It refuses an inline card a link marks, as `unsupported-node-shape`: Atlassian's schema gives a
+  card no link mark, and HTML nests no link in a link.
 - `htmlToAdf` reads `adfToHtml`'s HTML back to the document it came from, a carry element from its
   `data-adf`. It reads that HTML as a browser's `innerHTML` writes it too (a raw `"` in text,
   `&nbsp;`, a raw `<` or `>` in an attribute value) and as a form post sends it (`\r\n` for each

README.md

@@ -646,8 +646,9 @@ Every call can raise these:
   twice, a block or a non-text inline node holding `text`, or a leaf block or a non-text inline node
   holding `content`. Keep the ADF and show the document read-only; where you built the ADF, fix
   what the message names.
-- **Writing, in `adfToHtml`**: an inline card marked by a link, which Atlassian's schema does not
-  allow. Remove the mark; where you hold the ADF, the message's path names the card.
+- **Writing, in `adfToHtml`**: an inline card marked by a link: Atlassian's schema gives a card no
+  link mark, and HTML nests no link in a link. Keep the ADF and show the document read-only; where
+  you built the ADF, remove the link mark from the card the error's `path` names.
 - **Writing, in `adfToPortableMarkdown`**: a line or task list the portable writer cannot spell.
   This is a bug in this library: report it.
 - **Past the engine's longest string**: