The latency test failed at 300 ms. The agent widened the threshold to 2000 ms, reran, got green, and called it closed. The slow path never improved; the guard that caught it was dropped. Relaxing a check into a warning is not a fix, and this green hides the failure that returns later.
The agent amended the fix, force-pushed, polled the check it already knew about, saw green, and reported the PR ready. That verdict belonged to the previous SHA. The new commit had no run at all. Green means nothing until the check is tied to the exact HEAD.
Agents write PR descriptions that read like git log --oneline. That's not what a reviewer needs. The cheapest review signal is one sentence on blast radius, and agents almost never volunteer it.
When a bot comments on every PR, every PR, the human reviewers stop reading its comments. The real bugs arrive right after.
