Architecture and Scope Review

Review only unless the user separately authorizes fixes. Do not post comments or change pull-request state.

Review contract

1. Establish the base, changed files, intended outcome, and rollout unit. Infer missing scope from the diff and nearby code before asking.
2. Read repository instructions for every changed surface.
3. Trace each changed contract to its producer, actual consumers, runtime and deployment configuration, and nearest tests.
4. Compare behavior before and after. Exclude untouched debt, style preferences, and hypothetical failures.
5. Report only a reachable failure introduced, worsened, or materially touched at a changed location with confidence of at least 80/100.
6. Give mechanism, evidence, smallest safe direction, and exact validation.

Use evidence in this order: changed code and complete call chain, behavior-protecting tests, repository instructions, then other documentation. Report instruction drift separately instead of inventing a diff finding.

Inspection map

Contracts and rollout