Blame-aware code review — why your AI reviewer should only flag what you changed

Here's a problem that sounds minor but adds up fast: you open a pull request, run an AI code reviewer, and get 40 findings. Twelve of them are in files you touched. The other 28 are in code that was there before you arrived. Now you have a decision to make about 28 issues that aren't your fault, weren't introduced by your change, and probably can't be fixed in this PR without scope creep. You either ignore them (and train yourself to ignore the reviewer), fix them (and bloat the PR), or spend t...