 lilleman
|
4aa55e9ee1
|
Record the reading cost
|
2026-10-09 14:51:01 +02:00 |
|
|
lilleman
|
14ec866bed
|
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 14:50:50 +02:00 |
|
|
lilleman
|
875c0e5335
|
Rescore: the paired ruling at e487fa4 reads better
|
2026-10-09 14:37:06 +02:00 |
|
|
lilleman
|
180840532d
|
Answer architecture round 2: itemParts takes one run of task lists over the item, the properties share blockTaskItemChildren, and readBlock's bullet case names who reads a task list first
|
2026-10-09 14:37:06 +02:00 |
|
|
lilleman
|
2e640ded91
|
Answer architecture round 1: splitTaskList groups a list into items, bulletBlocks returns the split blocks itself, isTaskItem lives in adf/, a property reads generated task lists through portableMarkdownToAdf, and items 56 and 93 name today's code
|
2026-10-09 14:37:06 +02:00 |
|
|
lilleman
|
3ad1bd504e
|
Record the paired ruling: same
|
2026-10-09 14:37:06 +02:00 |
|
|
lilleman
|
335c3fbc70
|
Answer stability round 3: the portable writer merges adjacent nested task lists after the split, so it never writes !adf:listBreak
|
2026-10-09 14:37:06 +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
|
67bdc3ca44
|
Answer stability round 1: a task list nested beside a task item of paragraphs stays nested when written, the property checks every block task item holds paragraphs alone, item 49 names the checkbox loss it closes, and item 93 files the stale refusal path
|
2026-10-09 14:37:06 +02:00 |
|
|
lilleman
|
1ece265ea4
|
Record the reading cost
|
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
|
3f7cc81e80
|
Record the reading cost
|
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
|
310207fab5
|
Rescore: the paired ruling at 239218f reads the same
|
2026-10-09 12:21:18 +02:00 |
|
|
lilleman
|
a616f798af
|
Answer auto-reviewer round 1: the migration recipe keeps the marks of a hard break no text beside it holds, so a link of a hard break alone keeps its target
|
2026-10-09 12:21:18 +02:00 |
|
|
lilleman
|
7be5f70851
|
Rescore: the paired ruling at 37629e4 reads the same
|
2026-10-09 12:21:18 +02:00 |
|
|
lilleman
|
6b09275387
|
Answer stability round 5: item 89 replaces takesMarks, and the decision's date line wraps
|
2026-10-09 12:21:18 +02:00 |
|
|
lilleman
|
8beefe8833
|
Answer product-owner round 3: the spec says a directive mark's content holds something besides hard breaks
|
2026-10-09 12:21:18 +02:00 |
|
|
lilleman
|
4c9b46f57e
|
Keep a directive mark's content on one line where it is emitted, as main does
|
2026-10-09 12:21:18 +02:00 |
|
|
lilleman
|
90de9ba7be
|
Rescore: the paired ruling at f195ebd reads the same
|
2026-10-09 12:21:18 +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
|
b3f4d0f5c1
|
Rescore: the paired ruling at 45b5446 reads worse
|
2026-10-09 12:21:18 +02:00 |
|
|
lilleman
|
77a6806160
|
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 12:21:18 +02:00 |
|
|
lilleman
|
e04f026676
|
Rescore: the paired ruling at 6f1a16b reads worse
|
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
|
d1a47e861c
|
Answer stability round 4: the empty-link decision's title names the hard breaks kept
|
2026-10-09 12:21:18 +02:00 |
|
|
lilleman
|
c9aa49d99d
|
Move item 33 to 0.2.1
|
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
|
486661311f
|
Answer stability round 3: a link directive holding a joined hard break falls back to parting it
|
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
|
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
|
32bee5ab91
|
Record the reading cost
|
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
|
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 |
|