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 `/expo:taste` wrote - its report names the path; inside `/expo: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. ## Choosing the worker Refire runs on the same worker as the fire it corrects - see fire's `--with` table. Two ways the worker is set: - **Inside a serve:** the worker is already chosen; serve records it on state.md's `worker:` line (and the Codex tier on the `tier:` line). Read them, don't re-parse the task text - serve's contract is that fire and refire run on the same worker and tier (taste stays Codex/sol). No `worker:` line means the default Codex route. - **Standalone `/expo:refire --with <worker>` / `--tier <tier>`:** strip both flags from the args first, same convent