test: add DMARC compatibility fixture pack

docs/milestones.md

@@ -163,7 +163,7 @@ Exit criteria:
 
 ## Milestone 10: Forensic Report Support
 
-Status: In Progress
+Status: Complete
 
 Goal: support DMARC RUF/forensic reports for individual failure investigation.
 
@@ -182,7 +182,7 @@ Exit criteria:
 
 ## Milestone 11: DMARC Format Compatibility (DMARCbis) and Standards Alignment
 
-Status: In Progress
+Status: Complete
 
 Goal: keep DMARQ compatible with evolving DMARC report formats and nomenclature without breaking existing imports.
 
@@ -190,11 +190,8 @@ Delivered:
 - Add parser compatibility for RFC 9990-style aggregate report namespaces, version detection, policy metadata, identifiers, override reasons, auth-result details, and namespaced extensions.
 - Keep legacy RFC 7489-style reports backward compatible through fixture coverage.
 - Persist and CSV-export newly introduced aggregate metadata with nullable, backward-safe database fields.
-
-Planned:
-- Update domain/source reporting to include new metadata where it improves operator actionability.
-- Add fixture-driven tests for representative real-world DMARCbis-style reports.
-- Update documentation to clarify supported formats and terminology.
+- Add a fixture-driven compatibility pack covering parser, upload, IMAP, and Gmail import paths with supported-format documentation.
+- Verify domain report views and CSV exports render fixture-backed DMARCbis-style imports correctly.
 
 Exit criteria:
 - A DMARCbis-style aggregate report can be imported via upload/IMAP/Gmail and renders correctly in dashboards and exports.