Record the enum-ordering trap the PBX rollout hit

Ya

27 Agosti 2026, 04:14 UTC

Mwandishi

Kamo

Ahadi ya

b0c1417

Seeding a catalog row whose pricing_model is a new enum value makes that row unreadable to any service still on an older shared-lib, and getCatalog loads every active add-on in ONE query - so one bad row takes the whole catalog down, public pricing page and order wizard alike. The phase ordering in the spec was wrong: consumers must be rebuilt BEFORE the rows are seeded, not after.