independent-reviewlisted

# Independent Review Separate the author's explanation from the reviewer's judgment. Use one role at a time: prepare the review handoff in the implementation task, then conduct the review in a brand-new task with no inherited conversation history. ## Protect Independence - Start the reviewer in a new task, not a fork, continuation, or subagent that inherits the implementation conversation. - Treat the author's explanation as testimony to verify, not as repository truth or an approval recommendation. - Reconstruct the scope from the repository, canonical requirements, plan, Git state, code, tests, and executed checks. - Inspect the implementation before reading the author's rationale whenever the bootstrap and explanation can be passed separately. Record the preliminary concerns first. - State when a blind first pass was impossible because the explanation was already present in the reviewer context. - Keep the review read-only by default. Do not fix findings, alter the plan, stage changes, or create commits unless the user separately asks. ## Role A: Prepare The Author Explanation ### Freeze The Review Target Inspect applicable `AGENTS.md`, canonical requirements, implementation plan, Git status, branch, base or checkpoint, commits, and changed files. Define: - the objective and observable success criteria; - the exact base and head or the explicit working-tree boundary; - in-scope and excluded files, commits, requirements, and plan items; - relevant specs, ADRs, plans,