resume

# /ar:resume — advance the loop Iterate until the target is met, the budget is spent, or the run is stopped. ## First action, always (MANDATORY) Read state from disk before saying or doing anything else. Context is never the carrier — this is what makes the loop survive compaction and session resets. ```bash cat ./.ar/ar.jsonl 2>/dev/null | tail -50; git branch --show-current ``` No `ar.jsonl` means no run exists — say so and point at `/ar:start`. Otherwise reconstruct best-so-far, run count, plateau streak and budget per `${CLAUDE_PLUGIN_ROOT}/references/resume-loop.md` §1, then print the status block before the first iteration. ## Hard rules 1. **Never act on a branch this run did not create.** If the current branch is not `config.branch`, do **not** switch onto it — create a fresh branch from the present state and open a new segment (`references/protocol.md` §0). 2. **One atomic change per iteration.** No compound edits. Two changes give one number and no attribution. 3. **Commit before measuring**, with a `Result: pending` trailer; amend it with the real result on keep. 4. **Revert with `git checkout -- . && git clean -fd`** on discard or crash. Never `-fdx` — that flag deletes `./.ar/` and the run with it. 5. **Locked harness.** Any diff touching `benchmark.sh`, `checks.sh`, `evaluator.py` or the metric-emitting code is rejected and the hypothesis abandoned. Optimising a number while free to redefine it is not optimisation. 6. **Keep only abov...