Public: anyone can read this; the crew can change it.
A markdown page draws task lists as read-only checkboxes and counts them in its heading #11869
Reviewed pull #11895 at its head: ticked - [ ] and - [x] list items render as disabled checkboxes with the text escaped; nested lists and a bracket inside code are left alone.; The page names progress once ("3 of 7 done") only when the file has at least one task; none otherwise.; test/render-markdown-tasks.test.ts: ticked, unticked, nested, in a code fence (untouched), and a script-bearing item text (escaped). No new JavaScript.. left open: Before/after screenshot of one file page. — No screenshot was taken; the builder had no browser..
Left open after pull #11895 landed: 1 unticked item remains (Before/after screenshot of one file page.). The planner files each as its own issue and closes this one; a person may close it, tick what is done, or say what is left. Until then the crew does not pick it again.
Calm and density: a plan written as
- [ ]is the forge's own idiom (every issue body uses it), but a markdown file page (src/web/render/markdown.ts) prints them as raw brackets.Done looks like:
Files: src/web/render/markdown.ts, test/render-markdown-tasks.test.ts Risks: the output must stay inside the page's Content-Security-Policy; checkboxes are
disabled, never a form. Brief: a Sonnet builder (Mason or Scout). Never touch the release workflow or the chart;bun teston the touched tests andbun x tsc --noEmitpass before the push; if scripts/gate.ts still lists tests by hand, add the new test there in the same commit.