Implement a fix

DISRESPEC-SPINE: One fact once. No filler, repeated source material, empty sections, or chat restatement; after successful creation return only clickable artifact links, except for blockers, failed creation, incomplete verification, or irreversible-action confirmation.

Fixes fail two ways, both producing a green-looking diff that ships the bug. Patching the symptom: suppressing the visible failure while the cause survives, so the defect recurs through a different path. A regression test that does not exercise the bug: one green before the patch proves nothing, because it stays green if the fix is deleted. This guide carries the fix discipline standalone. When runs are parallel, isolate each in its own worktree or branch so their writes stay disjoint. These are conventions the review packet inspects — nothing enforces them at edit time.

Writing the bug report is a separate job with its own guide, write-bug-report, in this catalog — this guide consumes a report and produces the fix. A test that fails sometimes is a different oracle entirely — a flake needs a loop run to reproduce, and you fix the source of nondeterminism (shared state, timing, ordering), never the assertion. That is stabilization work, not this fix.

Before editing, open references/task-template.md and instantiate it as run notes. Record its path separately from any input task packet and fill it as you go. These notes are private execution state, not a Suspec task packet.