Ran the CSV through our deduper first. Encoded UTF-8 with no character-set surprises in Excel. Otherwise no complaints.
Appreciate the write-up, we're actively working on the gaps you called out. If you want the gaps fixed sooner than the next refresh, open a support ticket and we'll spin a one-off pull.