Email Suppression Contract Repair

The problem

Email eligibility and suppression logic often drifts across multi-tenant systems, leading to accidental sends to unsubscribed users or global suppression affecting the wrong workspace. You are likely facing queue races where unsubscribed users still receive enqueued messages, or CRM imports that silently reactivate hard-bounced addresses.

What it does

• Identifies cross-tenant preference collisions and global email identity leaks in multi-tenant architectures.
• Audits the repository for missing final send gates where queued messages bypass recent preference changes.
• Detects idempotency gaps in provider callbacks (SendGrid, SES, Mailgun) that cause repeated audit events or stale suppression effects.
• Analyzes CRM and CSV import logic for unsafe defaults that treat blank fields as new subscriptions.
• Maps drift between application state and provider-state abstractions represented in the repository.

Why this beats prompting it yourself

This skill systematically traces the entire email lifecycle from recipient creation to final provider callback across your models, workers, and adapters. It prevents the common pitfall of collapsing complex suppression states into a single Boolean 'active' flag, ensuring your patches respect tenant isolation and address versioning.

Use cases

• Enforce tenant-scoped suppression in systems where email addresses are globally unique.
• Fix race conditions where one-click unsubscribe fails to block already-queued campaign messages.
• Add idempotent handling for provider webhooks to prevent duplicate complaint processing.
• Standardize category-aware eligibility checks to ensure security alerts aren't blocked by marketing unsubscribes.

Known limitations

This skill operates only on repository code and fixtures. It cannot access live provider suppression lists, send real test messages, or make legal determinations regarding consent policy.