Blocking finding

Which findings block depends on the gate level the repository sets. At the default, warning, critical and warning findings block, except a warning the orchestrator rated low confidence, and suggestions do not. A finding blocks again if a later round reports it again, so an answer holds only as long as the code it answered.

In an agent review loop

A coding agent pushes a change and the review comes back with three findings on a repository whose gate level is warning:

• F1 · critical · a settings mutation that skips the ownership check
• F2 · warning · a rate-limit key built from the token prefix
• F3 · suggestion · a helper that could be inlined

F1 and F2 block; F3 does not, because suggestions sit below the gate level. The CodePanel status reads "2 findings need a fix or /feedback: F1, F2". The agent fixes F1, and finds F2 is wrong because the key is already the token id, so it answers both in one comment:

/feedback F1 up fixed --agent claude-code
/feedback F2 down false-positive src/lib/rateLimit.ts:18 keys on token.id --agent claude-code

F1 stops blocking at once. F2 stops blocking only when the orchestrator withdraws or revises it after checking the code; if it upholds the finding, F2 blocks until it is fixed or deferred. If the next round reports F1 again, it needs a new answer.

What counts as an answer

A finding is answered when a later round no longer reports it, when it is dismissed, when it has a fixed or deferred verdict given after the round that last reported it, or when a dispute about it is decided. The full rule is in what counts as answered.