Trace cardinality across normalization and persistence

For missing-related-entity investigations, check cardinality at every boundary: provider payload, normalized contract, creation helper, persisted rows, and UI projection. A model that supports several entities does not imply every ingestion path preserves them; successful import or enrichment can still omit secondary entries when normalization selects only a primary.

Distinguish simultaneous entities from replacement assignments. A refreshed snapshot establishes what was available at fetch time, not what existed at initial creation. A summary flag should not substitute for actual populated slots without a documented provider contract.