issue-resolve

# `issue-resolve` — drive an assessed issue to a draft PR Takes a verdict from `issue-assessment` and produces a reviewable fix. The terminal state is a **draft PR a human promotes** — never an autonomous merge. **Core principle:** the agent's job is to get the problem *review-ready*, not to declare victory. A fix is "verified" only after it runs green on the **affected surface**; when that surface can't be reached here (headed Flow browser, macOS-only, credits), say so in the PR and stop. (Memory: `done-means-e2e-verified`, `pr-must-verify-on-affected-surface`.) --- ## The Bug Lane — canonical here, cited everywhere **This is the chain a bug travels in gflow-cli.** It is written out once, in this file. `AGENTS.md`, `skills/spike`, `skills/scenario` and `docs/E2E_TESTING.md` all point here — none of them restate it, because a duplicated checklist drifts. ``` 0 SPIKE measure the live surface ── only when a claim about Flow is in play 1 DEBUG systematic-debugging → ROOT CAUSE ── the symptom is never the finding 2 SCENARIO BDD Gherkin written at the ROOT ── the reproduction, in Given/When/Then 3 TDD that Gherkin RED before any fix ── red for the right reason 4 FIX minimal change, at the root ── grep every caller before editing one 5 FORMALIZE UI/Flow surface ⇒ it is an E2E test ── a browser-free proxy does not discharge it ``` ### The surface gate — steps 0–2 are conditional, 3–5 never are Run **0 SPIKE*...