 lilleman
|
46effbf53c
|
Rescore: the paired ruling at f195ebd reads the same
|
2026-10-09 12:02:23 +02:00 |
|
|
lilleman
|
f195ebd14e
|
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:00:40 +02:00 |
|
|
lilleman
|
5e649d46b0
|
Rescore: the paired ruling at 45b5446 reads worse
|
2026-10-09 11:57:25 +02:00 |
|
|
lilleman
|
45b5446f63
|
Answer architecture round 3: one joinsBreaks flag in place of the parted set and its retry loops, a directive link spells its break, and takesMarks names the table's field
|
2026-10-09 11:55:32 +02:00 |
|
|
lilleman
|
84db16613a
|
Rescore: the paired ruling at 6f1a16b reads worse
|
2026-10-09 11:52:41 +02:00 |
|
|
lilleman
|
6f1a16b04a
|
Answer prose round 1: plainer decision title and spec, the refusal the spec owes, and comments that say why
|
2026-10-09 11:50:23 +02:00 |
|
|
lilleman
|
ce827fe7bf
|
Answer stability round 4: the empty-link decision's title names the hard breaks kept
|
2026-10-09 11:45:30 +02:00 |
|
|
lilleman
|
f6149930ae
|
Move item 33 to 0.2.1
|
2026-10-09 11:43:38 +02:00 |
|
|
lilleman
|
1f8df75917
|
Keep the hard breaks a link text holds alone, after its destination, and move item 89 to 0.2.1
|
2026-10-09 11:42:38 +02:00 |
|
|
lilleman
|
b4f8c042e6
|
Answer stability round 3: a link directive holding a joined hard break falls back to parting it
|
2026-10-09 11:32:38 +02:00 |
|
|
lilleman
|
ecfcdcd4f0
|
Answer product-owner round 2: the changelog names the joined spelling, and a run spans a sequence of hard breaks (fixes in the commit before)
|
2026-10-09 11:21:56 +02:00 |
|
|
lilleman
|
ddaec3087e
|
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 11:21:56 +02:00 |
|
|
lilleman
|
c68101e456
|
Answer stability round 1: the directive-mark refusals keep their order and the decision names its hard-break premise (fixes in the commit before)
|
2026-10-09 11:15:58 +02:00 |
|
|
lilleman
|
dd7e791d0e
|
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 11:15:58 +02:00 |
|
|
lilleman
|
0c89af5a5a
|
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 11:07:11 +02:00 |
|
|
lilleman
|
018c8b1ea7
|
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 11:04:30 +02:00 |
|
|
lilleman
|
fe5c731b1f
|
Record the reading cost
|
2026-10-09 10:55:17 +02:00 |
|
|
lilleman
|
39fda3341e
|
Build a hardBreak carrying no marks where a mark spelling spans a line break, in every reader
|
2026-10-09 10:54:56 +02:00 |
|
|
lilleman
|
78655bcdc0
|
Rescore: the paired ruling at e7029c1 reads better
|
2026-10-09 10:49:08 +02:00 |
|
|
lilleman
|
f7eb88ec1b
|
Answer architecture round 5: name the alert and callout markers by their spelling, and item 56 its functions
|
2026-10-09 10:49:08 +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
|
38d2fa94e1
|
Rescore: the paired ruling at 1098b5e reads better
|
2026-10-09 10:49:08 +02:00 |
|
|
lilleman
|
8a28df1026
|
Reflow the marker-line paragraph
|
2026-10-09 10:49:08 +02:00 |
|
|
lilleman
|
7da47d7aab
|
Answer architecture round 4: a folded callout's title line is no paragraph, and item 56 names the bracket resolution's range
|
2026-10-09 10:49:08 +02:00 |
|
|
lilleman
|
0c6379a541
|
File the em 1/3 exceptions for examples 638 and 639 as pending under item 87
|
2026-10-09 10:49:08 +02:00 |
|
|
lilleman
|
255a1fced7
|
Record the maintainer's approval of the node-model exceptions and the reader panel's verdicts
|
2026-10-09 10:49:08 +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
|
050364dbdc
|
Answer stability round 2: a link slot keeps a linked image linked, so the link-in-link refusal holds
|
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
|
d97c5c2935
|
Answer stability round 1: an !adf:link slot reads an image as plain alt text
|
2026-10-09 10:49:08 +02:00 |
|
|
lilleman
|
029b835e22
|
Rescore: the paired ruling at c45320b reads better
|
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 |
|
|
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
|
8370230fee
|
Record the reading cost
|
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
|
847c358358
|
Reflow the claimed-shapes bullet
|
2026-10-09 03:15:17 +02:00 |
|
|
lilleman
|
ce5a3b124e
|
Answer product-owner round 2: the claimed shapes read as text or code in CommonMark
|
2026-10-09 03:15:17 +02:00 |
|
|
lilleman
|
b1f6f9c08c
|
Answer product-owner round 1: CommonMark is valid input to commonMarkToAdf, and a claimed shape that does not complete is an error result
|
2026-10-09 03:15:17 +02:00 |
|
|
lilleman
|
724517d594
|
Word goal 6.1 as which markdown a name reads or writes, and drop plain from the bot persona
|
2026-10-09 03:15:17 +02:00 |
|
|
lilleman
|
9a242c7206
|
Rescore: the paired ruling at 5fc877e reads better
|
2026-10-09 03:08:39 +02:00 |
|
|
lilleman
|
6a1229cee0
|
Answer prose round 1: the parsing codes list each reader, the CommonMark guarantee splits into three bullets, the migration row and two decisions read once
|
2026-10-09 03:08:39 +02:00 |
|
|
lilleman
|
73ef96173f
|
Answer product-owner round 2: the bullet names the pipe tables the reader takes, the migration row links its section, the codes name their table
|
2026-10-09 03:08:39 +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
|
f310a437e2
|
Answer architecture round 2: the claims type keeps directives apart from alerts and highlights, two paragraphs reflowed
|
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
|
9805275bf7
|
Record the reading cost
|
2026-10-09 03:08:39 +02:00 |
|