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
|
ae4aa55e30
|
Answer product-owner round 1: the changelog states the memory a character costs, not a heap that varies by machine, and what the reader returns now
|
2026-10-13 11:50:14 +02:00 |
|
lilleman
|
ddbb362703
|
Spell a line in memory linear in its length, so a paragraph up to V8's longest string converts within Node's default heap
|
2026-10-13 11:48:18 +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
|
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
|
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
|
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
|
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
|
1b39f17ac0
|
Answer prose round 1: the spec names each title and destination, the writing verdict is its own decision citing item 100, items 99 and 101 state what holds, and the migration and changelog rows say what they replace
|
2026-10-11 13:31:18 +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
|
5f2c5083e9
|
Answer architecture round 1: the portable writer builds the linked image through externalMedia, the properties generate the image shapes, linkDefinition sits beside linkMark, the changelog drops a refusal no release met, and items 99 and 100 file the inline linked image and the caption reading
|
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
|
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
|
c6017526ac
|
Answer auto-reviewer round 1: the changelog line says a long run took seconds before and takes milliseconds now
|
2026-10-09 19:17:20 +02:00 |
|
lilleman
|
c0d93e4db3
|
Answer product-owner round 1: the changelog line says what a long run cost before, and item 33 states its cost at this commit
|
2026-10-09 19:17:20 +02:00 |
|
lilleman
|
b953be2ed4
|
File item 95 for the read-back, and note the linear escape in the changelog
|
2026-10-09 19:17:20 +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
|
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
|
0c56a479bb
|
Answer product-owner round 3: the changelog keeps nested only a task list before the block that splits the item
|
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
|
1870111427
|
Answer product-owner round 1: the changelog adds no gap note, item 7 names HTML in the tagline and keywords again, and the keywords name gfm
|
2026-10-09 13:07:56 +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
|
ba21c7a462
|
Answer architecture round 4: the writers close a mark run at a hard break again, and item 91 plans the joined spelling
|
2026-10-09 12:21:18 +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
|
1d05ee3df3
|
Answer stability round 2: a run that cannot be spelled parts at its hard breaks before the carry takes it, and the recipe bullet names the content it passes
|
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
|
3ff5c95f4c
|
Build a hardBreak carrying no marks where a mark spelling spans a line break, in every reader
|
2026-10-09 12:21:18 +02:00 |
|
lilleman
|
c7dcf67f70
|
Reflow the image changelog entry
|
2026-10-09 10:49:08 +02:00 |
|
lilleman
|
b868ba9ce2
|
Answer product-owner round 3: the changelog names the task marker
|
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
|
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
|
88aef1c8c4
|
Answer architecture round 1: one owner for the image's ADF shape, the readings' decision, marker paragraphs, the exceptions the README names; items 87 filed and 56 widened
|
2026-10-09 10:49:08 +02:00 |
|
lilleman
|
3b621a9cef
|
Read every CommonMark image and empty link: an image ADF holds no node for as its linked alt text, a title as its caption, an empty link text as its destination
|
2026-10-09 10:49:08 +02:00 |
|
lilleman
|
a821d0e97d
|
Answer stability round 1: every reader names unsupported-nesting-depth, Flavour stays file-local; product-owner round 1: model markdown reads in portableMarkdownToAdf, the migration rows say what each reader builds, each code names its readers, item 84 filed
|
2026-10-09 03:08:39 +02:00 |
|
lilleman
|
4d5f83459f
|
Answer architecture round 1: the claims type pins what every writer spells, the HTML calls take flavour names, model-written GFM reads in portableMarkdownToAdf
|
2026-10-09 03:08:39 +02:00 |
|
lilleman
|
66e4c7e8b5
|
Document the three markdown readers: README, MIGRATION, CHANGELOG, the grammar, the decisions and the plan
|
2026-10-09 03:08:39 +02:00 |
|
lilleman
|
9519606838
|
Answer product-owner round 2: the changelog names the markdown the library wrote
|
2026-10-08 14:10:50 +02:00 |
|