Use the specified diff, branch, PR, or working tree and its intended behavior. Remain read-only unless fixes are also requested. 1. Understand the trigger and expected result before judging the implementation. Read tests to learn which claims are actually exercised. 2. Check the in-scope review dimensions, including docs/README when behavior changed. Spawn 2–3 read-only explorers that split those dimensions. Concentrate on changed behavior, callers, and failure paths. Skip dimensions that are out of scope and say so. 3. Validate suspected defects with a concrete execution path, failing case,…