A tighter contract for AI code review review-pr tells an agent to review changed code for correctness, security, lifecycle, error handling, tests, and demonstrated performance risks. It also defines what does not count: speculative warnings, style commentary, untouched code that the change did not make unsafe, and test requests that merely repeat an already-covered behaviour. Every retained finding needs a repository-relative path, an exact changed line when possible, a concrete failure mode, and a fix direction. Critical and important findings can block approval; suggestions and nits cannot.