Backend Change Review

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

Review flow

1. Establish the base, diff, intended behavior, runtime stack, and changed backend surfaces.
2. Read repository instructions for every changed path.
3. Trace each changed path through transport, application or domain logic, persistence, schema, asynchronous work, and protecting tests as applicable.
4. Compare with the nearest current pattern in the same repository and stack.
5. Exclude untouched debt, style preferences, and hypothetical failures. A prohibited flow is in scope only when the diff materially changes it.
6. Report only reachable failures with confidence of at least 80/100, anchored to a changed file or line with 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.

Select references