Skip to content

Require evidence before the Effect review bot opens PRs - #228

Merged
MaggieAppleton merged 4 commits into
mainfrom
fix/effect-review-evidence-gates
Sep 30, 2026
Merged

MaggieAppleton merged 4 commits into
mainfrom
fix/effect-review-evidence-gates

Conversation

@MaggieAppleton

@MaggieAppleton MaggieAppleton commented Sep 30, 2026 •

Copy link
Copy Markdown
Collaborator

The Effect review bot proposed PR #222 solely to remove a dependency suppression, without establishing a reachable bug. Require caller and lifecycle evidence, a concrete failure or measurable unnecessary work, preserved setup/cleanup ownership, and verification of the actual claim. Missing required checks now mean no PR; zero findings is explicitly successful.

Regenerated the workflow lock file. Schedule, permissions, and the five-PR limit are unchanged.

Also stabilizes the PostgreSQL job-lock lease regression: handle the expected rejection immediately, observe the actual lock wait, and wait for expiry using PostgreSQL’s clock.

Validation: workflow compilation; bun run ci, types, build, 1,729 unit tests, and all 59 PostgreSQL tests pass. The repaired lease test also passes 10 consecutive runs.

Acceptance gates

The Effect review bot must trace the lifecycle, justify the change, and verify its claim before opening a draft PR.

@MaggieAppleton
MaggieAppleton merged commit 379402d into main Sep 30, 2026
3 checks passed
@MaggieAppleton
MaggieAppleton deleted the fix/effect-review-evidence-gates branch September 30, 2026 14:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant