 lilleman
|
fc5d5c7e5d
|
Answer prose round 1: 0 🔴, 9 🟡; the retry paragraph, the guarantees, the changelog and the code-list entry each say one thing once, the engine-limit message names what it covers, the persona line excepts engine-limit by the maintainer's call, and the error row's split is filed as item 111
|
2026-10-13 19:49:53 +02:00 |
|
|
lilleman
|
e110834159
|
Answer architecture round 3: 0 🔴, 0 🟡; an out-of-memory throw is engine-limit whatever the engine ran short of, the ruling reads same
|
2026-10-13 17:42:11 +02:00 |
|
|
lilleman
|
025ccc0cf8
|
Answer architecture round 1: 2 🔴, 5 🟡; readableBlock alone fills and reads the spelling memo, the escaper's steps hand on what they claim rather than write a shared buffer, engine-limit names only the throws an engine returns, and the docs agree on it
|
2026-10-13 17:32:36 +02:00 |
|
|
lilleman
|
ecd695a6d1
|
Return the new code engine-limit where the engine runs short of memory or passes its longest array, so unsupported-node-shape stays deterministic
|
2026-10-13 16:38:48 +02:00 |
|
|
lilleman
|
2b5992858e
|
Answer product-owner round 2: one retry rule, any unsupported-node-shape at the empty path, in the paragraph and the error table, and the memory refusal says it ran the engine out of memory
|
2026-10-13 12:04:34 +02:00 |
|
|
lilleman
|
e6fa3db1f5
|
Answer stability round 1: the escape flags flow through return values, and V8's failed typed-array allocation is refused as its memory running short
|
2026-10-13 12:02:31 +02:00 |
|
|
lilleman
|
7bc69355c3
|
Answer prose round 1: the refusal messages name what passed the bound, the decisions read one idea a sentence, and the changelog gives the readers' fix its own bullet
|
2026-10-13 01:30:12 +02:00 |
|
|
lilleman
|
142ed310c2
|
Answer stability round 2: the retry advice covers every call, readers included, and names JavaScriptCore as the one exception to determinism
|
2026-10-13 01:30:12 +02:00 |
|
|
lilleman
|
4657796d4d
|
Answer stability round 1: the guard's comment holds at both its call sites, and a giving-way list's items keep the list's path
|
2026-10-13 01:30:12 +02:00 |
|
|
lilleman
|
7caa8237f0
|
Answer architecture round 6: each block is held to the bound as it is built, the reader's ask takes the engine guard, and the chunk ships under a worse comprehension ruling by the maintainer's call, with item 110 to fill the memo in one place
|
2026-10-13 01:30:12 +02:00 |
|
|
lilleman
|
6f518dab93
|
Answer architecture round 5: the builders keep main's spelling, each writer's result and the CommonMark ask's spelling are held to the bound once built, and the engines' own overflows refuse alike
|
2026-10-13 01:30:12 +02:00 |
|
|
lilleman
|
3414c8690a
|
Answer architecture round 2: every builder joins its pieces through one bounded join, the readers take the engine guard, every refusal stands at the document's path, and a portable list's refusal names its own place
|
2026-10-13 01:30:12 +02:00 |
|
|
lilleman
|
e3aa790ec8
|
Refuse markdown past V8's longest string on every engine, before building it
|
2026-10-13 01:30:12 +02:00 |
|
|
lilleman
|
1ab405fa74
|
Answer auto-reviewer round 1: the README says to retry the engine-limit refusal once on JavaScriptCore, and the merged-text test says why it stays cheap
|
2026-10-11 21:05:07 +02:00 |
|
|
lilleman
|
62d80a69b7
|
Answer prose round 1: the README says which refusal differs between engines, items 106 and 107 read one idea a sentence, and two test titles and a comment read on one pass
|
2026-10-11 21:05:07 +02:00 |
|
|
lilleman
|
5e05fa6f30
|
Answer stability round 2: the advice names the array limit, the guard's test names both, and the decision rewraps
|
2026-10-11 21:05:07 +02:00 |
|
|
lilleman
|
80b4e0a9b7
|
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
|
2026-10-11 21:05:07 +02:00 |
|
|
lilleman
|
fdf7f1c2b7
|
Answer architecture round 1: the guard refuses only the measured overflow errors, the README keeps such a document read-only, and items 106 and 107 take the heap and the carry's indentation
|
2026-10-11 21:05:07 +02:00 |
|
|
lilleman
|
a9331b4125
|
Return a result where a conversion's text would pass the engine's longest string
|
2026-10-11 21:05:07 +02:00 |
|
|
lilleman
|
0b3f6e8973
|
Answer product-owner round 2: the text row names strike and the hard break's sides
|
2026-10-11 19:04:56 +02:00 |
|
|
lilleman
|
ab01c5f7ae
|
Answer product-owner round 1: the README drops the roadmap, spells every lossless form, alternates list markers truly, checks results in its examples, and lists each call's refusals once; item 105 pins the portable writer's codes
|
2026-10-11 19:04:56 +02:00 |
|
|
lilleman
|
3b5fed9a2c
|
Refit the README for search and a quick start, with a full reference below its contents
|
2026-10-11 19:04:56 +02:00 |
|
|
lilleman
|
5fa53cb795
|
Answer stability round 1: tryImage drops an exit the comparison already takes, the README and changelog scope the linked image, and item 101 files the refusal naming its spelling
|
2026-10-11 13:31:18 +02:00 |
|
|
lilleman
|
580bc862f2
|
Write an external image a link marks as [](href) in both writers
|
2026-10-11 13:31:18 +02:00 |
|
|
lilleman
|
cc40fb95f2
|
Answer prose round 1: the README drops the parse-path sentence and the comments say what stands in and why
|
2026-10-11 12:13:51 +02:00 |
|
|
lilleman
|
be3ac4af22
|
Answer product-owner round 1: the README says a parse's path points into the document the call returns
|
2026-10-11 12:13:51 +02:00 |
|
|
lilleman
|
cea9137495
|
Answer prose round 1: the comments and test name say what ends a list, the README says because, the changelog leads with the rename and gives the definition's trigger, and items 56 and 98 state their claims plainly
|
2026-10-10 13:20:05 +02:00 |
|
|
lilleman
|
419bb10324
|
Answer product-owner round 1: the migration row names the trigger and how to keep one list, the changelog groups the list entries and labels its fixes, and the README's second group says it has other reasons
|
2026-10-10 13:20:05 +02:00 |
|
|
lilleman
|
7d00b11b2c
|
Answer architecture round 1: closeLeaf records the block definitions end beside the blocks it pushes, openedList's comment names the exception, the README drops its counts, the changelog puts other changes last, and item 98 files the blank-line re-scan
|
2026-10-10 13:20:05 +02:00 |
|
|
lilleman
|
fa7f4ef987
|
Read two lists a link reference definition parts as two lists, and put the changelog's breaking entries first
|
2026-10-10 13:20:05 +02:00 |
|
|
lilleman
|
167bf1ff9b
|
Answer prose round 1: the decision says right after and keeps only its reason, the README counts the link-definition exception, and the comments and spec say which list alternates
|
2026-10-09 15:39:13 +02:00 |
|
|
lilleman
|
e689b83f64
|
Answer product-owner round 2: the README's backslash bullet ends on the reason GitHub's task markers need it
|
2026-10-09 15:39:13 +02:00 |
|
|
lilleman
|
a0166982b1
|
Answer product-owner round 1: the README states the alternate marker and the * escape, and the changelog names which writer dropped ::listBreak
|
2026-10-09 15:39:13 +02:00 |
|
|
lilleman
|
40580e6948
|
Read a list whose bullet or ordered delimiter changes as two lists, and alternate the marker between adjacent lists in place of !adf:listBreak
|
2026-10-09 15:39:13 +02:00 |
|
|
lilleman
|
cd6cb8bece
|
Answer prose round 1: a task item keeps the task lists right after its paragraphs nested, and the README, changelog, decision, comment, item 49 and a test title say it plainly
|
2026-10-09 14:37:06 +02:00 |
|
|
lilleman
|
217ab190f3
|
Answer product-owner round 2: the README's read-back cell and the changelog keep a nested task list nested, and item 93 ships in 0.2.0, where the portable reader first ships
|
2026-10-09 14:37:06 +02:00 |
|
|
lilleman
|
5b9fd4127d
|
Answer product-owner round 1: the README's read-back cell states the split, and the changelog and decision word it exactly
|
2026-10-09 14:37:06 +02:00 |
|
|
lilleman
|
654a960888
|
Stand a block a task item cannot hold after its task list, in portableMarkdownToAdf and adfToPortableMarkdown
|
2026-10-09 14:37:06 +02:00 |
|
|
lilleman
|
c66cbc288b
|
Describe only markdown in the package description and the README's tagline
|
2026-10-09 13:07:56 +02:00 |
|
|
lilleman
|
e4364b19d0
|
Answer prose round 1: plainer decision title and spec, the refusal the spec owes, and comments that say why
|
2026-10-09 12:21:18 +02:00 |
|
|
lilleman
|
06c225f8f4
|
Keep the hard breaks a link text holds alone, after its destination, and move item 89 to 0.2.1
|
2026-10-09 12:21:18 +02:00 |
|
|
lilleman
|
852d010ff7
|
Answer product-owner round 1: an emphasis or link run spans an unmarked hard break, the recipe drops a hard break's marks, and the refusal names hard breaks
|
2026-10-09 12:21:18 +02:00 |
|
|
lilleman
|
2340937fb2
|
Answer architecture round 2: the refusal row says a carried node escapes it, and the empty-link decision's title names the hard-break case
|
2026-10-09 12:21:18 +02:00 |
|
|
lilleman
|
2ca5ac41e6
|
Answer architecture round 1: the node table says a hard break takes no marks, and a link text of hard breaks alone reads as its destination
|
2026-10-09 12:21:18 +02:00 |
|
|
lilleman
|
d677222050
|
Read an image alone on an alert's marker line or the lines after it as the image, as a reader panel expected; item 88 filed
|
2026-10-09 10:49:08 +02:00 |
|
|
lilleman
|
ee3086ad1e
|
Answer prose round 1: one sentence per idea for the image readings, a decision title that states the rule, item 86 names its shapes
|
2026-10-09 10:49:08 +02:00 |
|
|
lilleman
|
446efded6c
|
Answer product-owner round 2: keeping an image an image needs nothing else on its line, and a quoted image is pinned
|
2026-10-09 10:49:08 +02:00 |
|
|
lilleman
|
c3c624f66e
|
Answer product-owner round 1: the docs say how to keep an image an image, and the empty link takes its own changelog entry
|
2026-10-09 10:49:08 +02:00 |
|
|
lilleman
|
3a41e9ccca
|
Answer architecture round 3: a link alone holding a titled image keeps its caption, and the decision's title names []()
|
2026-10-09 10:49:08 +02:00 |
|
|
lilleman
|
4454aaca92
|
Answer architecture round 2: the decision's title states it whole, an image's title drops inside a link, the readers refuse nesting past 500 levels, one owner for the empty-alt rule
|
2026-10-09 10:49:08 +02:00 |
|