test: suppress duplicate remaining-risk prose#20
Conversation
Co-authored-by: Peter Steinberger <58493+steipete@users.noreply.github.com>
|
/clawsweeper automerge |
|
ClawSweeper automerge is enabled for this PR. I added A maintainer can pause this with |
|
Codex review: needs maintainer review before merge. What this changes: The PR adds a unit regression test in test/clawsweeper.test.mjs asserting that keep-open PR review comments suppress duplicate Maintainer follow-up before merge: Normal PR review, CI validation, and duplicate-PR coordination are maintainer actions; the branch itself is the proposed fix, so there is no separate automated repair to queue. Best possible solution: Land one canonical passing regression test for duplicate remaining-risk suppression, keep the existing renderer contract unchanged, and retire the duplicate source PR if this replacement is merged. Acceptance criteria:
What I checked:
Likely related people:
Remaining risk / open question:
Codex review notes: model gpt-5.5, reasoning high; reviewed against 00524d5fcb52. |
|
/clawsweeper approve |
|
ClawSweeper is pausing automerge for human review. Source: I added |
|
/clawsweeper approve |
|
Maintainer-approved ClawSweeper automerge is complete. Approver: The automerge loop is complete. |
Carry forward @steipete's automerge smoke regression from #19 with the requested repair: the keep-open PR review comment test should assert that duplicate
Remaining risk / open question:prose is suppressed.Source PR credit: #19 by @steipete.
Validation:
ClawSweeper 🐠 replacement reef notes:
fish notes: model gpt-5.5, reasoning medium; reviewed against bc94cce.