Stop review gate re-blocks the same finding repeatedly, with no way to defer or cap it #790

Plugin version: codex 1.0.6 (Claude Code desktop, macOS)

What happens

With the stop-time review gate enabled, each stop reviews only the previous turn's edits
(prompts/stop-review-gate.md). When the user decides to stop iterating on a finding,
the next edit to the same area triggers a fresh review with no memory of earlier findings
or of that decision, so the gate blocks again on the same topic.

In about two days of use in one workspace: 226 stops were reviewed, with 202 ALLOW, 23 BLOCK and
1 failure. Most blocks were correct and useful. But one session produced 6 consecutive
blocks on the same check and another 3 on a single line of documentation. After a set
number of attempts, the user's working rule is to stop fixing and decide. The gate could
not see that decision, so each further stop was blocked again.

Expected

A way to stop the gate from re-raising a finding the user has already seen and deferred.
Options, any one of which would help:

1. Pass the previous gate findings for the same session into the stop-review prompt, and
   tell Codex not to block again on a finding that was already reported unless the new
   edit made it worse.
2. A per-session cap: after N blocks on the same files, downgrade to a non-blocking note.
3. A documented way for the user to acknowledge a finding (for example a session marker
   that the hook reads) so the next stop is ALLOW for that finding.

Why not a local edit

Editing prompts/stop-review-gate.md in the plugin cache would work, but an update to the plugin
overwrites it, so the fix belongs upstream.