fix(admin): purge cascade map learns crm_auto_lead_cursors (163) - #406
Merged
Conversation
…#399 x #403 cross-PR seam Each PR was green alone: #399 added the offboarding purge whose cascade map is derived-and-asserted from the migrations; #403 added a table FKing email_accounts. Merged together the map assertion went red on main. The auto-lead cursor is per-mailbox state and goes with the mailbox. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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
1 participant
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.
Cross-PR seam: #399's cascade-map assertion × #403's new
email_accountschild. Each was green alone, red combined on main — this is the one-line map addition (+ count comment) that makes them agree. Local:test_admin_member_purge.py+test_crm_auto_lead.py, 114 passed.🤖 Generated with Claude Code