sentry-fixerlisted

# sentry-fixer Turns a Sentry issue into a fix: fetch it, map it onto the code actually in this working tree, verify the code hasn't already moved on, reason about root cause, propose a plan, and — only once the user says yes — implement the fix and a regression test. Read-only against Sentry throughout, and never touches git. This file is the workflow spine. Domain detail (path normalization, the stale-code method, root-cause reasoning, the fix-plan shape) lives in `references/` and is loaded at the step that needs it — don't try to work from memory of those files, read them at the point below that names them. ## 1. Preflight Run `scripts/sentry.sh detect`. It prints `{"backend":"cli|api|none", "org":..., "project":..., "base_url":..., "python":...}`. `python` is the interpreter the script resolved by actually running it (`python3`, then `python`, then `py`). **Use that value, not a literal `python3`, for the `summarize_event.py` call in step 3** — on Windows the `python3` on `PATH` is often the Microsoft Store stub, which is not Python. - **Exit 3 (`backend":"none"`)**: no `sentry-cli` session and no token found. Look for Sentry MCP tools already present in the session — if one exists that fetches an issue, an event, and a list of issues, use those in place of `sentry.sh` for the rest of this workflow (see `references/sentry-access.md` → *MCP tool discovery* for how to match them by purpose, since tool names aren't fixed). If no such tools are present, tel