The prod retag is done

Audited prod today and applied the fix. Operators reloading the Create credit order drawer should now see packages for Dallas and O'ahu cards. Findings and what was changed, so you can give operators a definitive answer.

Audit findings

Every active offering was non-canonically tagged. All 10 active offerings carried bare market slugs, not canonical ids: 6 tagged dallas and 4 tagged oahu. These are plain slugs, not even mkt_ prefixed, so they could never match a canonical Platform geography market id and your fail-closed filter correctly showed nothing. The one remaining offering is Archived and was null-tagged (a global candidate), so it was left alone. The Dallas and O'ahu markets were exactly the culprit you expected, traced to the 2026-05-18 geography ids.

The canonical ids those slugs map to (from Platform's geography catalog, created 2026-05-18):

Dallas: mkt_019e393d-91b0-7249-b66f-b15a9affdf7c. O'ahu: mkt_019e393d-919e-7188-a183-24222ff92023.

A related note on the account side: of 33 credit accounts, 32 carry a null platform_market_id and 1 carries a non-canonical mkt_test. Per the null rule we agreed (null means market-unknown, do-not-scope-out), the null accounts should not have their offerings stripped, so this does not block the common case. The retag is what fixes the scoped path.

What was applied

One transaction against the revenue schema, with an invariant check that would have rolled back on any failure:

The Revenue Market mirror (revenue.markets, ADR-0023) was empty in prod, never seeded, so there was no canonical id space to map onto. It was seeded from Platform's active geography (Dallas and O'ahu, 2 rows). The 10 active offerings were retagged from the dallas and oahu slugs to the canonical ids above. The offerings.market_id FK (ADR-0023 expand phase) was backfilled from the canonical tag for all 10. Post-apply re-audit confirms zero non-canonical active offerings and zero active non-global offerings with a null market_id.

Ask back

Please confirm on your side that the Package dropdown now populates for a Dallas or O'ahu card, so we can close the operator symptom for good. If anything still reads empty, it is most likely an account whose card-market context does not resolve, which is the coverage-field path rather than the catalog, and we should look at that next.

Two things for the record, not blocking

The committed audit and backfill scripts run through Prisma, whose generated client in the Revenue repo is pinned to the revenue_test schema (the revenue/revenue_test split). Against prod that made the Prisma tools read and write the empty test schema, which is why a first pass falsely reported zero offerings. The retag was therefore applied via raw SQL against the explicit revenue schema. Revenue will fix the tool schema-pinning so the standard tooling is safe against prod, and is considering an internal ADR for it. Separately, the mirror being empty in prod means the ADR-0023 snapshot consumer and catalog seed had not run there; it is seeded now, but the durable snapshot pipeline in prod is still owed on Revenue's side and tracked separately from this retag.

References