[Git-on-my-level]

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 fix(billing): consistently name the current subscription Omi Pro #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

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	⚠️ Failed 2026-11-02T13:18:40.575029Z We couldn’t complete this review. Comment @codex review to try again.	33064be	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.

[cubic-dev-ai]

1 issue found across 53 files

Confidence score: 3/5

• The revision bump in plus_budget80.json leaves the hardcoded revision assertion in plan_storefront_test.dart stale, so the Dart test will fail. Update the expected revision to match the fixtures.

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. When an issue isn't valid or won't be fixed in this PR, reply in its thread with the reason and then resolve the thread. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="app/test/fixtures/storefront_v2/plus_budget80.json">

<violation number="1" location="app/test/fixtures/storefront_v2/plus_budget80.json:3">
P2: This revision bump breaks the Dart test that parses this fixture set. `app/test/models/plan_storefront_test.dart` still hardcodes `expect(data.catalogRevision, 12);` for `plus_monthly_yearly_toggle.json`, which now reports 13. Update that assertion to 13 in the same PR.</violation>
</file>

<sub>Reply with feedback, questions, or to request a fix.

View guided diff | Turn on auto-fix | Re-trigger cubic</sub>

[cubic-dev-ai]

P2: This revision bump breaks the Dart test that parses this fixture set. app/test/models/plan_storefront_test.dart still hardcodes expect(data.catalogRevision, 12); for plus_monthly_yearly_toggle.json, which now reports 13. Update that assertion to 13 in the same PR.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. When an issue isn't valid or won't be fixed in this PR, reply in its thread with the reason and then resolve the thread. At app/test/fixtures/storefront_v2/plus_budget80.json, line 3:

<comment>This revision bump breaks the Dart test that parses this fixture set. `app/test/models/plan_storefront_test.dart` still hardcodes `expect(data.catalogRevision, 12);` for `plus_monthly_yearly_toggle.json`, which now reports 13. Update that assertion to 13 in the same PR.</comment>

<file context>
@@ -1,6 +1,6 @@
 {
   "schema_version": 2,
-  "catalog_revision": 12,
+  "catalog_revision": 13,
   "show_subscription_ui": true,
   "header": "You've used 80% of this month's usage",
</file context>

[Git-on-my-level]

Addressed the fixture-consumer revision mismatch in e534058: app/test/models/plan_storefront_test.dart now expects catalog revision 13. The focused Flutter suite passed all 19 tests; the unchanged cap-hold file passed all 38 tests on its one-worker retry.

The final candidate is 3baaed9 after syncing current main. Its PR diff is still exactly 52 revision-only fixture updates, the matching one-line parser assertion and the internal-only changelog fragment. All price, entitlement, policy and copy bytes and assertions remain unchanged. Full final-head CI and the second delta review are the remaining merge gates.