Answer stability round 1: the docs name V8's array limit in one text node, a test pins Invalid array length, and item 106 takes the readers' RangeError and JavaScriptCore's Out of memory

docs/decisions.md

@@ -461,9 +461,9 @@ handles one cause alike whichever node, attribute or direction raised it.
   knows which direction it called and parting them after `0.1.0` is MAJOR (2026-09-23).
 - A non-finite number takes two codes: `unsupported-node-shape` parsing, `not-an-adf-document`
   emitting — no document holds one, so no round-trip crosses them (2026-09-23).
-- A document whose markdown runs past the longest string the JavaScript engine holds is
-  `unsupported-node-shape` at the document's path, in either writer: the document does not convert,
-  and the bound is the engine's own. A carried node reaches it on about 1 MB of deeply nested JSON,
+- A document whose markdown would be longer than the longest string or array the JavaScript engine
+  builds is `unsupported-node-shape` at the document's path, in either writer: the document does not
+  convert, and the bound is the engine's own. A carried node reaches it on about 1 MB of deeply nested JSON,
   since the block carry indents two spaces a level; `todo.md` item 107 spells it in a length linear
   in its JSON (2026-10-11).
 - The markdown readers and `htmlToAdf` refuse a value that is not a string as `not-a-string`, at