Code review

Review the current change without modifying code. The goal is a reliable merge decision with a small number of proven findings. Be direct and constructive.

Decision standard

A material finding identifies all three of these:

1. a concrete failure or policy violation present on the current head;
2. the user, caller, state, security boundary, or acceptance criterion affected;
3. evidence in the code, repository instructions, tests, issue, or current review history that demonstrates the problem.

Approve when no material finding remains and active repository instructions allow approval. Do not manufacture feedback to avoid approving. Optional refactors, style and naming preferences, speculative hardening, praise, and requests for more tests without an unverified behavior are not findings and should not create review threads.