Staged code review

Review the staged diff within the user's scope, including affected contracts and consumers. Derive tools and conventions from the workspace; do not assume a stack or product. A full review covers all staged changes, not a sample.

Mode and boundaries

• Default to read-only. Review-and-fix requires authorization to fix findings; a request to keep reviewing does not grant it by itself. Existing authorization persists for the agreed task until completed or revoked. Explicit read-only or proposal-only instructions take precedence.
• Preserve the index: do not stage, unstage, reset, commit, push, or rewrite history without an explicit request. Leave fixes and authorized generated output unstaged.
• Preserve unrelated user work. Ask only when a necessary fix cannot be isolated safely or a material product, policy, access, or external-system question cannot be resolved from evidence. Continue independent work rather than stopping the whole review.

Scope and evidence