fix(tests): refresh storefront catalog revision goldens

Merged
GI
11h ago
+56-53

What changed and why

Refresh storefront snapshots from catalog revision 12 to 13 after #24367's approved Unlimited → Omi Pro display-name change. Update the Flutter fixture consumer's matching revision assertion so the mirrored fixtures keep parsing successfully.

All 52 fixture payloads differ only in catalog_revision; every price, entitlement, policy and copy byte is unchanged. Add the required kind: none mobile changelog fragment for this internal test correction.

Product invariants affected

none

How it was verified

  • A recursive comparison of #24367's canonical catalog found exactly the revision bump and display-name change. A separate byte audit pins every fixture change to catalog_revision: 12 → 13, permitting only the matching Dart assertion and internal-only fragment alongside it.
  • BACKEND_UNIT_TEST_FILE_LIST=<storefront-list> BACKEND_PYTEST_WORKERS=4 bash backend/test.sh: 345 passed.
  • flutter test --concurrency=1 test/models/plan_storefront_test.dart: 19 passed.
  • Local shard 4 was stopped after 65 files by the release coordinator's explicit ruling; it found an unchanged cap-snapshot concurrency assertion failure. Its one-worker retry through backend/test.sh passed all 38 tests. No cap-hold code, assertions or timing budgets were changed.
  • Full backend proof is the exact-head six-shard CI run. All six passed before the one-line Flutter assertion correction; the backend tree is identical, and the final-head full run remains the merge gate.

Local tests ran serially through omi-heavy and nice -n 19. Normal push hooks remain enabled.

Tests

Existing regression checks: test_golden_storefront_scenarios, test_localized_storefront_goldens, and the Flutter storefront model suite. Complete payload, pricing, entitlement and parser rejection assertions remain intact.

UI evidence

UI-Evidence: none -- fixture metadata and a matching test assertion; no runtime UI change.

Failure class (fixes)

Failure-Class: none