[kasettadoo-sys]

What was wrong

GFM task lists render as disabled checkboxes with no name: Markdown passed remark-gfm's <input type="checkbox" disabled> through as it is. The existing streaming test renders - [x] search but runs no axe check on it.

Before:

<Markdown>{'- [x] search\n- [ ] read'}</Markdown>

axe reports a critical label violation on both checkboxes (<input disabled="" type="checkbox" checked="">), and a screen reader announces a checkbox with no name. Agents write - [x] plans and to-do lists all the time, in AgentMessage too.

After: each checkbox is named "Task", with its checked state as before. axe finds no violations.

What changed

• src/markdown.tsx: an input component, TaskCheckbox, that names a checkbox from labels.markdown.task. Other attributes are as remark-gfm sets them: disabled, and checked or not.
• src/lib/labels.ts: a new key, markdown.task ("Task"). The Portuguese labels (test/labels-pt.ts, examples/playground/lib/labels-pt.ts and the copy in content/docs/labels.md) add "Tarefa".
• test/labels-locale.test.tsx: the Markdown scenario renders a task list, so the new label has a state that shows it, and no English is left in it.
• content/components/markdown.md says how task lists read.
• A minor changeset, since it adds a label key: a translation typed as SignoffLabels needs markdown.task to type-check, and one passed as SignoffLabelsInput keeps the English (as in fix(approval-card, diff-review): accessibility and touch: Approve all's focus, what a card runs, code left to right, 16px fields #174).

How it was tested

New tests in test/markdown.test.tsx fail on main and pass here:

• names the checkboxes of a task list, which read with their state: two checkboxes named "Task", the first checked, both disabled, no axe violations.
• takes the task name from the labels: labels={{ markdown: { task: 'Tarefa' } }} names it "Tarefa".

Checks, all exit 0: pnpm build:lib, pnpm format:check, pnpm lint, pnpm lint:registry, pnpm registry:check, pnpm typecheck, pnpm test (1601 passed), pnpm size (AgentMessage stays 91.7 kB; /custom-markdown unchanged), pnpm test:site, pnpm examples:check.

For the owner to decide

• One name or two: the checkbox gets one name, with its checked state read separately. Two names ("Done", "To do") would read the state twice.
• Name from the item: naming each box after its item's text would need aria-labelledby and ids per item, which aren't stable while the text streams.