Bug write-up: subtasks could not be ticked off (#88) Four faults stacked, each hiding the next: 1. The propagation guard was on onchange, but ticking a checkbox fires CLICK, which bubbled to the row and opened the subtask. Happens on every install - the fault you actually see, and the one Ed spotted. 2. The endpoint asked for the status literally named 'Done'. Renameable display name, so a German install could never complete a subtask at all. Same fault as #79. 3. The tick and strikethrough were drawn by comparing the status to the English word too, so a completed subtask still showed an empty box. 4. The refusal was silent - the response was never read. That is why the report says "no errors observed", and why 2 went unnoticed. Also records the two found in passing (completion time written in the server's local clock beside UTC columns; three error toasts styled as successes), the i18n position (the German pack was already complete - what shows English is the seeded STATUS NAMES, which are database rows), and two verification notes worth keeping: why the navigation assertion is on the DOM rather than selectedTaskId (a top-level `let`, reads undefined, would false-pass), and how the first attempt broke tasks.js entirely by putting backticks inside a template literal while the page went on rendering normally. Adds the Bugs-Resolved row.