A flagged reply is refused on its own instead of failing the task

Before this, a reply the screen flagged stopped the run and marked the task failed, so one false positive halted work mid-task. Now the flagged message gets a short refusal where it was sent, and the task carries on with whatever comes next. Flagged issue text, review feedback, and the message that starts a new task still stop it. On Linear the flagged comment stays on the issue: while it is among the issue's five most recent comments, later turns in the same run are refused too, and a fresh run that finds it, such as after a day idle, stops the task; delete or edit it to continue. A GitHub issue comment, Slack message or API reply that arrives after a task went idle is still screened as a new task would be and can still stop it; on Linear, the message that starts each run, whether it opens a task or wakes one up, is now also screened on its own, even when it isn't among the comments Sinatra reads back from the issue.