Diagnose SES probation: clean now, historical cause, instrumentation inert

Current sending is healthy — 2,794 sent over 14 days, 0.18% bounce, 0.000% complaint — so probation is not caused by present behaviour. Suppression entries cluster in Jan 27-Mar 19 2026, pointing at a Q1 incident that was never cleared. Main finding: the newsletter-events configuration set is fully wired (reputation metrics, suppression, VDM, SNS destination on bounce/complaint/ delivery/open/click) but no code passes ConfigurationSetName — not in newsletter.org/lib/ses.ts nor ipartners-nextjs/src/lib/ses.ts. So the SNS topic receives nothing, transactional and bulk share one pooled reputation, and no reputation problem can be attributed to a sender. Includes the console checks that need a human (CLI returns only ~14 days of send stats, and the available IAM user lacks cloudwatch:GetMetricStatistics) plus the remediation order: attach config sets, then request review.