refirelisted

# Refire - the plate failed the pass, send it back A refire is a fix run whose spec already exists on disk: the `findings.md` a taste wrote after validating every finding. That is what makes the ticket unusually precise - file, line, failure scenario, prescribed fix, all confirmed against the code. Your job is to carry that precision through and then prove each finding is actually gone. ## Inputs - Default: the `findings.md` the most recent `/sous-chef:taste` wrote - its report names the path; inside `/sous-chef:serve` it is the `findings:` line in the run's `state.md`. (Lost the path? It's the newest `findings.md` under `$SCRATCHPAD`.) - Alternative: a review the user pastes or points to. Validate unfamiliar findings against the code first (taste's step 3); never refire a finding you have not confirmed yourself. - No findings available? Say so and stop. Refire without a review is just a fire. ## Preflight Same as fire, and for the same reasons: 1. Git repo with at least one commit (`git rev-parse HEAD`). 2. The resolved worker's route preflight - resolve the worker (a leading `--with <worker>` or, inside a serve, state.md's `worker:` line; default Codex), then run that route's preflight from fire's `--with` table. Default route: `test -f ~/.codex/sous-chef.config.toml`; missing means stop and offer `/sous-chef:mise` (Codex silently ignores a missing profile). 3. Mint a fresh job dir: `JOB=$(mktemp -d "$SCRATCHPAD/refire-XXXXXX")` (`$SCRATCHPAD` i