feat(stripe): capture early fraud warnings for review#3554
Merged
Conversation
Contributor
Code Review SummaryStatus: No Issues Found | Recommendation: Merge Executive SummaryFull PR reviewed across all 13 files; observation-only EFW capture is correctly scoped, idempotent, and the SELECT FOR UPDATE + transaction correctly prevents GDPR-deleted users from being re-linked during concurrent deletion. Files Reviewed (13 files)
Reviewed by claude-sonnet-4.6 · 771,368 tokens Review guidance: REVIEW.md from base branch |
866f753 to
34349ec
Compare
markijbema
approved these changes
May 28, 2026
markijbema
approved these changes
May 28, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
review_requiredobservations, resolving canonical ownership where safe while preserving the no-enforcement rollout boundary.Verification
/admin/early-fraud-warnings, but Chrome DevTools MCP could not start because its browser profile was locked by another running browser instance.Visual Changes
Reviewer Notes
main.