lilleman
|
2c8ea5c30b
|
Answer prose round 1: 0 🔴, 1 🟡; say the refusal costs Goal 4 too
|
2026-10-17 23:27:55 +02:00 |
|
lilleman
|
6ede19861d
|
Rule Goal 7 over Goal 4 for the over-wide pipe-table row and close item 117
|
2026-10-17 23:27:55 +02:00 |
|
lilleman
|
e680927e37
|
Answer prose round 1: 0 🔴, 3 🟡; disambiguate the README fallback, reword item 117's citation and item 118's tagline, record the writer panel
|
2026-10-14 22:49:13 +02:00 |
|
lilleman
|
311fe491c7
|
Answer architecture round 2: 1 🔴, 0 🟡; cite item 117 in the GFM refusal entry, name the url fallback
|
2026-10-14 22:49:13 +02:00 |
|
lilleman
|
928752a58d
|
Answer architecture round 1: 1 🔴, 3 🟡; name the other-target link and no-alt case, pin both, file items 117 and 118
|
2026-10-14 22:49:13 +02:00 |
|
lilleman
|
3f3d0bdde7
|
Keep both targets of a linked external image standing inline in adfToPortableMarkdown
|
2026-10-14 22:49:13 +02:00 |
|
lilleman
|
251c8193e6
|
Answer prose round 1: 0 🔴, 1 🟡; scope the hard-break exception to the CommonMark link, split the refusal sentence, say who kept the directive refusal
|
2026-10-14 22:09:42 +02:00 |
|
lilleman
|
492a7fa828
|
Retitle the mark-skipping decision to name the link and directive marks it refuses, and land item 73 last in 0.3.0
|
2026-10-14 22:09:42 +02:00 |
|
lilleman
|
e56291eb90
|
Answer prose round 1: 0 🔴, 8 🟡; say which reader skips what, reorder the migration's keep-the-mark advice, file the decision title as a question
|
2026-10-14 21:10:41 +02:00 |
|
lilleman
|
c9f9276df9
|
Answer architecture round 1: 1 🔴, 2 🟡; read a node's taken mark types once, let the highlight ask takesMark, correct the README's code-span bullet
|
2026-10-14 21:10:41 +02:00 |
|
lilleman
|
278ebbbad5
|
Give code text no mark but code, link and annotation, in every reader
|
2026-10-14 21:10:41 +02:00 |
|
lilleman
|
6c389b9c83
|
Answer prose round 1: 0 🔴, 8 🟡; say which marks a node refuses, and name the fix in the directive mark refusal
|
2026-10-14 15:08:46 +02:00 |
|
lilleman
|
bb3a128233
|
Answer product-owner round 1: 0 🔴, 1 🟡; name the refusal stored markdown meets, and make the next release 0.3.0
|
2026-10-14 15:08:46 +02:00 |
|
lilleman
|
6842f386ae
|
Answer architecture round 1: 2 🔴, 4 🟡; refuse a link around only nodes that take none, mark the change breaking, file code-text marks
|
2026-10-14 15:08:46 +02:00 |
|
lilleman
|
1ae7ba6992
|
Give an inline node no mark Atlassian's schema withholds from it, in every reader
|
2026-10-14 15:08:46 +02:00 |
|
lilleman
|
aefcd4b9e3
|
Answer prose round 1: 0 🔴, 6 🟡; the changelog names what breaks, the fallback reads as untyped mark, attribute or value, the spec's value list and marks paragraph split, messages name the JSON array to write
|
2026-10-14 10:48:12 +02:00 |
|
lilleman
|
d5b9356a29
|
Record the marks and colwidth spellings in the spec, decisions, changelog and migration guide
|
2026-10-14 10:48:12 +02:00 |
|
lilleman
|
1c7518aea1
|
Answer prose round 1: 1 🔴, 4 🟡; the entry claims only the refusal, item 112 opens with its verb and cites Goal 4 alone
|
2026-10-14 07:52:41 +02:00 |
|
lilleman
|
8faaa35915
|
Decide that the portable reader refuses what GFM's reading would drop
|
2026-10-14 07:52:41 +02:00 |
|
lilleman
|
5f1c64b371
|
Answer prose round 1: 0 🔴, 7 🟡; the guarantee splits per reader, the spec's portable sentence follows the named errors, item 112 names rows holding no pipe
|
2026-10-14 01:17:39 +02:00 |
|
lilleman
|
ec9492635a
|
Read GFM's pipe table without leading pipes and with alignment colons in portableMarkdownToAdf
|
2026-10-14 01:17:39 +02:00 |
|
lilleman
|
6152808194
|
Answer prose round 1: 0 🔴, 2 🟡; the slot's rule joins the node-tables bullet, the remedies offer the space alike, the message says lines
|
2026-10-14 00:26:19 +02:00 |
|
lilleman
|
5cd07cafec
|
Answer architecture round 1: 0 🔴, 2 🟡; the slot's line ending is a value the slot does not take, and its message offers the space again
|
2026-10-14 00:26:19 +02:00 |
|
lilleman
|
06df26727a
|
Fold unspellable-whitespace into unsupported-node-shape
|
2026-10-14 00:26:19 +02:00 |
|
lilleman
|
667360f6e6
|
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 20:10:29 +02:00 |
|
lilleman
|
d13a17565b
|
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 20:10:29 +02:00 |
|
lilleman
|
a0fdfe377e
|
Answer architecture round 2: 1 🔴, 1 🟡; the CommonMark ask answers yes or no, the memo's callers name themselves, the bound's policy reads at its constant, Firefox's bare out-of-memory string is engine-limit, and the floor entry no longer points at item 110
|
2026-10-13 20:10:29 +02:00 |
|
lilleman
|
563133f3ee
|
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 20:10:29 +02:00 |
|
lilleman
|
d90898c6ec
|
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 20:10:29 +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
|
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
|
a0bb09b80d
|
Answer architecture round 4: the forecast and the indent leave, a writer refuses a document whose text alone passes the bound, and the joins are the one bound left
|
2026-10-13 01:30:12 +02:00 |
|
lilleman
|
ae1a47f1bc
|
Answer architecture round 3: the forecast never overcounts, the carry's JSON and the portable code block join through joinedWithin, and the list's choice of form stands in its own function
|
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
|
2b5d22cbc6
|
Answer architecture round 1: every container joining several walks sums their projections before it joins, the portable reduction refuses a list whose spelling is refused, and heldTextLength moves beside textLength
|
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
|
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
|
38a3d5f265
|
Record the maintainer's decision to ship items 85 and 86 under a fall, and file item 102 to place a refused task-list block without the replay
|
2026-10-11 13:31:18 +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
|
580bc862f2
|
Write an external image a link marks as [](href) in both writers
|
2026-10-11 13:31:18 +02:00 |
|
lilleman
|
66a4d4bf72
|
Answer auto-reviewer round 1: the floor's decision says item 56 is still to give the walk's state one owner
|
2026-10-10 13:20:05 +02:00 |
|
lilleman
|
4d83706ad9
|
Record the maintainer's decision to ship item 94 under a Locality fall
|
2026-10-10 13:20:05 +02:00 |
|
lilleman
|
3741b9e5b3
|
Answer prose round 1: the comments say why, items 95, 96, 91 and 34 read in one pass, the floor's decision drops the rule CLAUDE.md holds, and item 97 files the changelog's order
|
2026-10-09 19:17:20 +02:00 |
|
lilleman
|
d38f563b03
|
Answer stability round 1: item 34 names the flanking reads that remain, and the floor's decision records who put item 95 in it
|
2026-10-09 19:17:20 +02:00 |
|
lilleman
|
3e9c56d399
|
Answer architecture round 3: the comprehension floor's decision names item 95, the directive read takes its index from the claimed prefix, and only the claimed prefix leaves directive-syntax.ts
|
2026-10-09 19:17:20 +02:00 |
|