harness-looplisted

# /harness-loop > **HUMAN-ONLY-EDITED.** This file is the §5 "program.md analog" > (`docs/harness-improvement-plan.md` §5.1): it states the loop's own rules. > The loop agent reads it every iteration but must never edit > `skills/harness-loop/SKILL.md` itself — TARGET below is fixed to the > reviewer-prompt pair precisely so a candidate cannot rewrite the regulation > it runs under. Changing this file is a deliberate, human-reviewed act > outside any loop session. ## Mission Apply the autonomous-improvement-loop procedure (§5, `docs/harness-improvement-plan.md`) to this harness's own reviewer prompts. Default TARGET (the only files a loop iteration may edit): `agents/code-reviewer.md` and `agents/security-reviewer.md`. A hook-surface mission (editing `core/hooks/`) is allowed only when the target hook already has its own per-hook test battery (P1-3) — otherwise the grader's signal doesn't cover it and the loop would be scoring blind. This skill specializes `/loop` (`skills/loop/SKILL.md`) to one fixed mission; all mechanical enforcement is still `core/infra/loop-run.sh` — nothing here duplicates it. ## Procedure Work on branch `harness-loop/<tag>` (e.g. `harness-loop/reviewer-precision-2026-08`). Steps 2–9 repeat per attempt, subject to the cap, timeout, and circuit-breaker checked in step 9. 1. **Check git state.** Confirm the current branch and commit (`git status`, `git log -1`) before touching anything — the loop must know exactly what "the mission's starting