320 Commits

Author	SHA1	Message	Date
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	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	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	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	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	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	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	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	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	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	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	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	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	80e1124f39	Name each markdown call by its flavour: a goal, the decision and the panel's pick of portable	2026-10-09 03:08:39 +02:00
lilleman	dfb3206d7e	Answer prose round 3: the decisions cite no removed item, the reader's comment is its bug link, item 83's tagline reads in order	2026-10-08 14:10:50 +02:00
lilleman	d7f2384876	Answer architecture round 1: the reader returns its refusals and owns its stack, a decision and a test keep JSON.parse out, item 83 filed, the scoring run recorded	2026-10-08 14:10:50 +02:00
lilleman	bfe26dd438	Round-trip JSON keys holding a backslash, quote or control character, and generate them in the properties	2026-10-08 14:10:50 +02:00
lilleman	8d1c75fa8b	Re-plan: 0.2.0 also takes item 43, which item 49 lands after	2026-10-08 12:08:02 +02:00
lilleman	d0b13a5056	Re-plan: 0.2.0 also takes items 59, 60, 61 and 62	2026-10-08 12:08:02 +02:00
lilleman	c2c71e1736	Re-plan: 0.2.0 ships four reader fixes, HTML moves to 0.3.0, later releases shift one	2026-10-08 12:08:02 +02:00
lilleman	380a894589	Answer prose round 1: one name per thing in the new docs, the changelog points at MIGRATION's rows, item 82 drops its partial file list	2026-10-07 12:39:45 +02:00
lilleman	dbc8b91f91	Answer product-owner round 1: list each input the new code takes in MIGRATION's table, a String object among them, and give htmlToAdf the code	2026-10-07 12:39:45 +02:00
lilleman	41ac4510f5	Answer architecture round 1: name a non-string by typeof alone, name and comment what the seats could not read, file items 81 and 82	2026-10-07 12:39:45 +02:00
lilleman	2c4fadbd8b	Refuse a markdown input that is not a string with not-a-string	2026-10-07 12:39:45 +02:00
lilleman	459b64ceda	Answer prose round 2: item 77 names its open code question, rewrap the quick start's goals line	2026-10-05 09:02:45 +02:00
lilleman	4d4f292fbe	Answer prose round 1: item 72 waits on the rest of 0.2.0, item 77 counts its values; answer product-owner round 1: link the goals the quick start serves	2026-10-05 09:02:45 +02:00
lilleman	e7a1aa1194	Put the README's goals and audience after the quick start, and record the answers on items 72 and 77	2026-10-05 09:02:45 +02:00
lilleman	e8066ee2fd	Answer prose round 2: item 78 also rewords the position paragraph	2026-10-05 08:49:28 +02:00
lilleman	a4ff89df07	Answer prose round 1: item 78 names what it records and that it breaks	2026-10-05 08:49:28 +02:00
lilleman	328ec88f52	Item 78 takes not-a-string, the maintainer's pick	2026-10-05 08:49:28 +02:00
lilleman	51b9272350	Answer prose round 2: item 80 says what it names, the comment names its writer	2026-10-05 01:07:55 +02:00
lilleman	db5d6c0e46	Answer prose round 1: item 78 names its cause	2026-10-05 01:07:55 +02:00
lilleman	02204b3b48	Item 78 asks for its code first	2026-10-05 01:07:55 +02:00
lilleman	7da3c1fbbe	Refuse an attribute value JSON does not hold, and push a folded callout's title leaves one at a time	2026-10-05 01:07:55 +02:00
lilleman	59ea87f6aa	Answer prose round 2: rewrap items 71 and 78	2026-10-05 00:37:21 +02:00
lilleman	6aadd29934	Answer prose round 2: the plain bullet says which call keeps what, and items 71, 78 and 79 read once	2026-10-05 00:37:21 +02:00
lilleman	f4022d62c9	Answer stability round 1: item 71 waits on items 7 and 46 again, keywords match the GitHub topics	2026-10-05 00:37:21 +02:00
lilleman	3fb21b9766	Open the README with what the package does and for whom, and give npm search keywords	2026-10-05 00:37:21 +02:00
lilleman	4b23ec90d0	Answer prose round 2: item 77 says the reader, not the copy, reads arrays by index	2026-10-04 23:57:16 +02:00
lilleman	d803f18f6e	Answer prose round 1: item 77 refuses what its detail refuses, names item 45's reader and the keys it drops, and the decision expires with it	2026-10-04 23:57:16 +02:00
lilleman	6d66a5f868	Plan item 77 as one read of the input into a plain copy, landing with item 45	2026-10-04 23:57:16 +02:00
lilleman	640772bc0f	Answer prose round 2: the edge-whitespace comment names the real spelling, the Raw HTML paragraph loses its half clause, items 75 and 77 read once	2026-10-04 23:36:47 +02:00
lilleman	e4435008ac	Answer architecture round 1: the publish job's write token reaches only the tag push, publishing names main, and the audit's other findings are filed	2026-10-04 23:36:47 +02:00