fix(commands): close the promises the command templates could not keep

DEL B chunk `interview` (+ discover/status/cleanup/help). Fasit written before
the run predicted 8 defects and refuted 4 candidates; all 8 confirmed, all 4
refutations held, and three predictions turned out too narrow.

- M-BUG-36: `drift --list` reached the command as 0 bytes. drift-cli accepted
  --output-file but list mode ignored it, and the listing goes to stderr, which
  the command discards per ux-rules rule 2. Fixing the caller alone would not
  have helped.
- M-BUG-37: feature-gap's "Create backup" step ran fix-cli without --apply.
  Dry-run is the default, so no backup existed (backupId: null) while the
  command went on to edit config believing it could roll back.
- M-BUG-38: fix-cli told users to recover with scanners/rollback-cli.mjs, which
  does not exist. Dead reference in the one message read after a bad fix.
- M-BUG-21 fourth arm: five templates carried literal [--global]/[--full-machine]
  inside executable bash blocks. A bracketed placeholder does not start with a
  dash, so every scanner's arg loop takes it as the scan target.
- interview and analyze never said which session they act on; interview could
  rewind a finished session; cleanup interpolated an unvalidated id into rm -rf
  (an empty id deletes every session); status advertised a `resume` command that
  does not exist and documented an `all` argument it never parsed.

TDD: 9 red tests first, including a machine sweep for dead /config-audit
references and for bracketed flags in bash blocks. Suite 1432 -> 1441/0.
Frozen v5.0.0 snapshots untouched; --raw/--json contracts unchanged.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01UGvA1uUQn2hPBPMaCKK6x3

commands/interview.md

@@ -32,10 +32,28 @@ AskUserQuestion requires synchronous terminal interaction and does not work when
    if echo "$ARGUMENTS" | grep -q -- "--raw"; then RAW_FLAG="--raw"; fi
    ```
 
-1. **Load session state**: Verify analysis phase completed, read analysis report for context
+1. **Resolve the session, then load its state**:
+
+   ```
+   Glob: ~/.claude/config-audit/sessions/*/state.yaml
+   Sort by modification time — the most recently modified session wins
+   ```
+
+   Every path below substitutes that session's id for `{session-id}`. Never guess
+   it: if the Glob returns nothing, say "No audit session found — run
+   `/config-audit discover` first" and exit. Read the session's `state.yaml` and
+   verify `completed_phases` contains `analyze`; if it doesn't, tell the user
+   analysis hasn't run yet and exit. Then read the analysis report for context.
 2. **Conduct interview inline**: Use AskUserQuestion tool directly (NOT via Task). Adapt questions based on analysis findings.
 3. **Save interview results**: Write to `~/.claude/config-audit/sessions/{session-id}/interview.md`
-4. **Update state** (see state-management rule)
+4. **Update state** (see state-management rule), with one bound specific to this
+   command: interview is optional and can be run against a session that already
+   moved past it. If `completed_phases` already contains a later phase (`plan`,
+   `implement`, `verify`), do **not** rewind `current_phase` and do not re-add a
+   phase already in `completed_phases` — append `interview` only if it is absent,
+   leave `current_phase`/`next_phase` pointing at the furthest phase reached, and
+   tell the user the preferences will apply the next time `/config-audit plan`
+   runs. Rewinding a finished session is how its progress gets lost.
 5. **Output summary**
 
 ## Interview Questions