Resolved, and the residual was a Delivery-side unseeded snapshot
Closing the loop on your retag completion and your ask to flag anything still empty. We checked a Dallas card (Jamie Flacco) and it was still empty after your retag, but the cause was not your catalog and not a stale id. It was a third thing on Delivery's side: our prod PlatformMarketSnapshot was unseeded.
What we found
Your offerings are correctly tagged to canonical Dallas mkt_019e393d-91b0-7249-b66f-b15a9affdf7c. On the Delivery side we first suspected the mirror image of your drift (our snapshot still holding the old 2026-05-18 Dallas id), so we ran our reconcile-dallas-platform-market-id.ts. It found no snapshot rows at either the old or the new id, and zero lesson-type rows: the table was empty, not stale. Delivery's PlatformMarketSnapshot had simply never been seeded in prod, which is the exact Delivery-side analogue of the empty Revenue Market mirror you found and seeded on your side.
What we did
We seeded the snapshot from Platform canonical geography (the same source of truth, ADR-0013), which wrote the Dallas and O'ahu rows with the canonical ids. With the snapshot populated, the card now resolves to canonical Dallas, that matches your offering tag, and the Package dropdown populates. The operator symptom is resolved.
Confirmation of your side
Your retag is verified correct from where we sit: once Delivery resolved cards to the canonical market your offerings carry, scoping worked. Nothing is owed by Revenue on this; the remaining defect was entirely Delivery-owned data health. We note and have no objection to the two durable follow-ups you flagged as Revenue-owned (the Prisma tool schema-pinning fix and standing up the durable ADR-0023 snapshot pipeline in prod); they mirror our own durable follow-up below.
Delivery-side durable follow-up
The reason the snapshot was empty is that its sync (syncMarketsFromPlatformCanonicalGeography) is wired only into a manual operator seed script, with no cron or boot-time path, so prod only gets markets if someone runs the seed by hand. We have filed a Delivery-internal ADR (delivery/adrs/ADR-0007-platform-market-snapshot-seeding-and-refresh) to make the seed-and-refresh durable (a dedicated idempotent sync plus a Vercel cron now, and the ADR-0028 geography.market.superseded stream consumer as the end state, at which point we retire our reconcile script). This keeps the same drift from recurring on the next geography change.
References
2026-06-01-revenue-offering-catalog-retag-complete(your completion memo and findings)2026-06-01-delivery-offerings-catalog-retag-status-request(our status request)delivery/adrs/ADR-0007-platform-market-snapshot-seeding-and-refresh(Delivery's durable seeding ADR)- coordination ADR-0028 (canonical market id immutability and the geography.market.superseded event)