workflow-engineer-fix-buglisted

# workflow-engineer-fix-bug The **back half** of the bug lifecycle: turn an approved fix plan into committed, tested code. Dispatched by the `fix-bug` workflow (`workflows/fix-bug.mjs`), which runs only after a human approved the `# Bug Analysis` comment (flipping the bug to `status:ready-to-implement`, then the kickoff stage to `status:in-progress`). The bug's defining discipline lives here: **the regression test is written first, fails on the pre-fix code, and passes after the fix** — locking the defect out so it can't silently return. The fan-out review's `pattern-test-coverage` (deletable-code) lens gates exactly this, so a fix without a locking regression test blocks the review. ## When to activate - The dispatch prompt opens with `Fix bug #<n>` (initial regression-fix), OR - The dispatch prompt opens with `Fix the review feedback on bug #<n>` (post-review fix), OR - The user types `/workflow-engineer-fix-bug`. Do NOT activate to diagnose a bug (that is `workflow-engineer-analyze-bug`, the read-only pre-approval step) or for slice / PR work. ## Input contract The fix branch is `fix/<n>-<intent>`, already created on origin by the `fix-bug` workflow's Prep. Resolve it by prefix (the slug suffix is not load-bearing): ``` git ls-remote --heads origin "fix/<n>-*" ``` Take the single matching branch name. If zero or more than one match, halt and surface the ambiguity — do not guess. ## Workflow ### 1. Read the bug + the approved analysis Fetch the bug via `bash ski