How duplicate report ingestion is prevented

Every raw report file's hash is recorded, and the combination of (domain, reporting organization, report ID) is a database uniqueness constraint. If ingestion runs twice over the same mailbox — intentionally, or because a cron overlapped — the second pass simply can't insert the same report again; the database itself is what prevents duplication, not a check in the ingestion code, which is a more reliable guarantee.