run-review-repair-loop

# Run Review Repair Loop Review the real repository state, score the change honestly, repair concrete findings, and repeat. Treat the final score as a self-assessment supported by evidence, never as independent approval. ## Establish The Contract Before reviewing or editing: 1. Read all applicable system, developer, `AGENTS.md`, repository, and user instructions. 2. Identify the repository, branch, base or comparison range, dirty state, staged state, authorized files, protected paths, required gates, prohibited actions, and iteration limit. 3. Use an explicit user-supplied base or range when provided. Otherwise, prefer the current branch's upstream merge base and include relevant working-tree changes. If the intended range cannot be determined safely, ask one concise question before editing. 4. Default to at most five review-repair iterations unless the user specifies another bound. 5. Preserve pre-existing user changes. Never revert, stage, commit, push, open a pull request, deploy, access production, or mutate external systems unless the current request explicitly authorizes that action. 6. Stop and report if a required fix needs a file outside the authorized scope. Name the exact file and reason instead of silently broadening scope. If the request is review-only, report findings and scores without editing. If repair is requested or clearly implied, perform the repairs within the established contract. ## Load Repository Doctrine Treat repository-owned instructions an...