Feature: xsell addon recommendation [GEN-5439]

[panasetskaya]

What

Adds support for the addon recommendation in the cross-sell sheet shown after a successful self-service flow.

• The cross-sell sheet and Home queries now fetch recommendedAddon, and the sheet renders it (pillow with plus badge, title, description, button) with priority over the recommended cross-sell.
• Flows that change a contract now pass its contract id in CrossSellInput, which is what makes the backend return an addon recommendation: change tier passes the changed contract id, the moving flow passes newContractId from the commit mutation, closed claims pass the claim's contractId.
• Addon-only sheets show the green banner with the default CROSS_SELL_BANNER_TEXT copy ("Popular choice"), since RecommendedAddonCrossSell has no banner text field. Same fallback as iOS.
• A successful response with nothing to show (no recommendation, no addon, no other cross-sells) no longer opens an empty sheet.
• Home's top bar cross-sells action now also shows if only an addon recommendation is returned (defensive; Home sends no contract id today).

Remaining scope (waiting on storefront)

The design also shows a benefits checkmark list and per-type banner text ("Add extra safety when traveling" / "Add extra coverage"). Per the sync on Jul 3, storefront is getting two new properties for this (an optional banner and a list of strings) and the plan is to consume them here and get a design preview before merging. Until the schema publishes, the banner falls back to the default copy and the list is not rendered.

Testing

• Unit tests: addon mapping in GetHomeDataUseCase, the Home top bar gate, CrossSellInput contract id present/absent, and the sheet presenter's empty/non-empty handling.
• Manually verified against staging: addon card after a change tier flow (button deep links in-app), recommended cross-sell fallback for a flow without a contract id, and the empty response case.

a11y

• if these are UI changes - check for their accessibility

pr in storefront

todo:

• pass new contractId from moving flow
• (optionally) pass contract Id from claim closed pr in claim service
• wait for storefront pr schema published to prod

[notion-workspace]

android