A review run reviews: a comment addressed to the builder must not become the reviewer's task #1237

On #1130 at 12:01Z the sweep queued Sentinel's review of a green head. Sentinel's run ended failed: declined: This message is addressed to scout, who builds this pull. I'm Sentinel, the reviewer: I don't write code or push… — it took the latest comment on the pull (the owner's nudge to the builder) as its instruction and did not review. The head went unreviewed and the pull shows only the older verdicts.

A review run's task is the review: the diff, the brief, the earlier verdicts. Comments on the pull are context, and a comment addressed to another agent is not an instruction to the reviewer.

Done looks like:

• [ ] The review run's prompt (src/crew/review.ts or the runner's prompt for reason review) states the task first and frames comments as context; a comment that names another agent is shown as such and never changes the task.
• [ ] A review run that ends without a verdict is a failed review, retried once with the task restated, then the pull is sent to the other reviewer if there is one.
• [ ] test/review-from-check.test.ts (or review-route): a pull with a builder-addressed comment still gets a verdict from the reviewer run.

Evidence: trevato/forge run on #1130, reason review, 12:01Z.

Parked by the crew: the check failed and the decider saw no point in another try (pull #1308 closed). Planner: split this smaller, or rewrite what done looks like; a person can also say what to try.