run-the-bots-review-before-it-doeslisted

# Run the bot's review before it does ## Purpose An automated reviewer changes the order of events: it comments within minutes, before a human has looked, so its findings are the first thing on the PR and the frame through which the human reads the change. That makes two things worth doing. First, its rulebook is knowable — every finding it has ever posted is public on the repo's other PRs — so the checklist it will apply can be run *before* pushing, and it finds nothing. Second, when it does find something, the reply is not for the bot: it is for the reviewer who will scroll past an unanswered "Medium Severity" and read it as an open defect. The bot is also genuinely useful in one specific way: it reads the implementation behind your call and reasons about what that implementation does asynchronously. That is a class of objection self-review tends to miss, because self-review checks what the code says and the bot checks what the code it calls actually does. ## When to use - Before the first push into a repo whose PRs carry bot comments — harvest first, then push. - A bot finding has landed and needs an answer, or is about to be read by a human reviewer. - Your change adds a wait, a guard, a helper, or a default that sits in front of something asynchronous — the bot's strongest category. - The change is test-only. Counter-intuitively this is where a bot has a lot to say: whether the test exercises the path it claims to. ## When NOT to use - No automated reviewer on