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`.) --- ## Preconditions (all required before any code change) 1. An `issue-assessment` verdict of `CONFIRMED-BUG` or `LIKELY-BUG`. 2. Scope is single-surface / localized (not a cross-cutting redesign). 3. The fix is **verifiable in this environment** (browser-free), OR the verification gap is explicitly carried into the PR as "needs human e2e." If any fails → do not resolve; return to `issue-assessment` (reply-only). --- ## Autonomy envelope (the action contract) Allowed autonomously: - ✅ Post one issue comment (status / reply to reporter). - ✅ Open a **draft** PR (push a `bugfix/`-prefixed branch off `develop`). - ✅ Run **browser-free / credit-free** verification (unit, lint, type, recording-verif, Gemini tool-path). Never (these require a human, regardless of pressure): - ❌ Spend Veo credits (no live video generation to "verify"). - ❌ Mark a PR ready for review or merge it. - ❌ Push to `main` or `develop`...