feat(catalog): add loyalty tier fields to egress catalog API

[dinosoeren]

Adds optional loyalty-tier fields to the egress catalog API so a game backend can serve tier-aware catalogs (e.g. a tier-based daily gift) without resolving the player's tier itself.

Response — FreeItem:

• target_tier_id (9): identifier of the loyalty tier a free item targets. For a locked preview of the next tier's reward, return the item with status LOCKED and the next tier's id.

Request — GetCatalogRequest:

• current_tier_id (7): the player's current loyalty tier, resolved by Stash when a loyalty program is enabled.
• next_tier_id (8): the tier directly above the current one (absent at the top tier), for returning a locked preview of the next tier's reward.

All fields are optional and additive (buf breaking clean vs main). Regenerated docs/gen/swagger.v1.json.

---

Note

Low Risk
Additive, optional protobuf/OpenAPI changes only; no runtime logic in this diff.

Overview
Extends the egress Get Catalog contract so tier-based free rewards (e.g. daily gifts) can be built without the game backend resolving loyalty tiers.

Request — optional query fields currentTierId and nextTierId: Stash supplies the player’s current tier and the tier above (when not at max), so the game can pick the right bundle and optionally show a locked preview of the next tier’s reward.

Response — optional targetTierId on FreeItem: tags which tier a free item belongs to; locked next-tier previews should use status LOCKED with that tier id.

docs/gen/swagger.v1.json is regenerated to match the proto changes. All fields are optional and additive.

^{Reviewed by Cursor Bugbot for commit 6b8724b. Bugbot is set up for automated code reviews on this repo. Configure here.}

[dinosoeren]

• feat(catalog): add loyalty tier fields to egress catalog API #28 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.