Improve the framework

Use this for backlog missions ("look at all the issues, plan each one, implement, verify") and for any issue where the goal is a better engine, not just a closed ticket. The deliverable is two-fold: the fixes themselves, and a framework where the next fix is measurably cheaper.

Plan the pass

1. List open issues, drop stale or duplicate ones, and group the rest by shared root cause or seam using workflow PR-boundary rules.
2. Order the queue so early fixes create seams later fixes reuse: infrastructure-shaped issues first, consumers after.
3. Use fan-out only for groups that are genuinely independent; keep issues sharing a seam in one sequential lane.

Ship one issue

Route through jgengine intake and deliver through workflow, with evidence via jgengine-verify. Merge only when the mission explicitly asks for merges; otherwise park the PR for the user.

While implementing, record friction as it happens:

• blocker — no engine path existed; you wrote one-off or game-local code
• workaround — an engine path existed but fought you
• ergonomics — it worked but took too many edits, lookups, or retries