fr-debugginglisted

# fr-debugging `superpowers:systematic-debugging`, wrapped in isolation. The root-cause investigation, the failing test, and the fix all happen in the isolation workspace, so the base repo is never touched and the fix lands as a reviewed PR — the debugging analogue of `fr-brainstorming` / `fr-goal`. **Announce at start:** "I'm using fr-debugging to find the root cause in isolation." This skill owns WHERE debugging happens (isolation) and the autonomy contract. It delegates HOW — the Iron Law, the four phases, the supporting techniques — to `superpowers:systematic-debugging`, invoked unchanged. ## 0. Isolation first — hard gate Before ANY command — reproduction, evidence-gathering, instrumentation, reads included; "just check X first" never reorders this: - **Already inside an active fr isolation workspace?** (e.g. a bug found mid-fr-goal implementation) — **reuse it.** The failing test + fix land on that feature's branch and ride its existing PR; a bug found while building a feature must not spawn a competing PR. Confirm with `fr isolation status`. - **Cold start** (standalone bug, no active workspace): ```bash fr isolation up --branch fix/<slug> [--profile <name>] ``` Name the branch for the bug now (`fix/<slug>`); the worktree, PR, and cleanup key off it. A cold-start `fix/<slug>` is cut from freshly-fetched `origin/<default>` (#322), so the fix is clean of whatever the base checkout is parked on — to debug on the current branch by intent, add `--b