Review, Fix, and Address Bots

Execute the phases in order. Treat reviewer read-only behavior as an invariant, not a preference. The primary agent alone owns edits, judgment, validation, staging, commits, pushes, PR mutations, and bot replies.

Reviewer role boundary

Reviewers may read files, diffs, history, test source, existing test output, and repository instructions with read-only tools. Explicitly prohibit each reviewer from:

• creating, editing, moving, or deleting files,
• executing tests, builds, typechecks, linters, formatters, generators, installers, package scripts, or arbitrary repository commands,
• staging, committing, amending, rebasing, resetting, checking out, or pushing,
• creating or updating PRs, reviews, comments, checks, or other external state,
• delegating implementation to another agent.

Tell each reviewer: “Operate in read-only mode. You are advisory only. Never modify the workspace or Git/PR state, and never commit or push. Return findings and critique to the primary agent, who makes the final decision.”

Run log

Read references/run-logging.md completely. Start its structured run log before phase 1, append an event after every reviewer pass and material workflow transition, and finish it even when the run is blocked or fails. Keep requested and actually applied reviewer settings separate, use stable reviewer and deduplicated finding IDs, and record actual token usage only when the runtime exposes it.