PR Merge occurs too quickly: need time post-review to address and update to avoid a second PR

[sebastientaggart]

Currently when /submit-for-review runs the PR merges immediately after a review that produces no blockers. This is too quick, since often the NOTE items that come out of a review are in scope and should be resolved before the PR is merged.

[sebastientaggart]

Agent Implementation Notes

File to change: skills/submit-for-review.md

Approach: Modify Step 8's "ai" mode APPROVE path to add a human gate when non-blocking findings (NOTE/WARNING) exist.

Current behavior: APPROVE verdict → immediate merge → Step 9 offers follow-up issues for NOTE/WARNING items.

New behavior: APPROVE verdict with NOTE/WARNING findings → present findings to user → ask: address now (return to coding loop) or merge now? Only if zero non-blocking findings, merge immediately as today. If user chooses to merge, proceed to Step 9 as before.

Key decisions:

• Gate only applies in "ai" mode (advisory always merges, off skips review)
• Clean APPROVE (no findings at all) still auto-merges — no friction added for clean reviews
• User gets three choices: fix now, merge now, or review the PR comment for details
• Step 9 follow-up offer still runs after merge for any remaining NOTE/WARNING items

[sebastientaggart]

Resolution

The submit-for-review flow now pauses after a review that contains non-blocking findings (notes and warnings), giving you a chance to address them before merging. Clean reviews with no findings still merge automatically.

See #97 for full technical details.