fix(rewards): match carousel design from perps

[Montoya]

Description

This makes the Rewards carousel match the Perps carousel.

Changelog

CHANGELOG entry: null

Related issues

Fixes: n/a

Manual testing steps

Feature: my feature name

  Scenario: user [verb for user action]
    Given [describe expected initial app state]

    When user [verb for user action]
    Then [describe expected outcome]

Screenshots/Recordings

Before

After

Screen.Recording.2026-04-16.at.2.16.11.PM.mov

Pre-merge author checklist

• I've followed MetaMask Contributor Docs and MetaMask Mobile Coding Standards.
• I've completed the PR template to the best of my ability
• I've included tests if applicable
• I've documented my code using JSDoc format if applicable
• I've applied the right labels on the PR (see labeling guidelines). Not required for external contributors.

Performance checks (if applicable)

• I've tested on Android
  • Ideally on a mid-range device; emulator is acceptable
• I've tested with a power user scenario
  • Use these power-user SRPs to import wallets with many accounts and tokens
• I've instrumented key operations with Sentry traces for production performance metrics
  • See trace() for usage and addToken for an example

For performance guidelines and tooling, see the Performance Guide.

Pre-merge reviewer checklist

• I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
• I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.

---

Note

Low Risk
Primarily UI/layout tweaks and copy changes to the Rewards tour carousel, with a small test addition; low likelihood of impacting core app flows beyond the onboarding screen.

Overview
Aligns the Rewards campaign tour carousel UI with the Perps carousel by adjusting spacing/layout, left-aligning step text, resizing/repositioning the optional image, and restyling the footer (notably changing Skip from a secondary button to a centered text link).

Updates the primary CTA to show "Let’s go" on the last step (new rewards.onboarding.step_finish i18n string), and adds a test to assert the final-step label swap from Next to Let’s go.

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

[github-actions]

CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.

[github-actions]

🔍 Smart E2E Test Selection

⏭️ Smart E2E selection skipped - draft PR

All E2E tests pre-selected.

View GitHub Actions results

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit a7f0ba8. Configure here.}

[cursor]

Test uses fragile text queries instead of testIDs

Low Severity

The new test uses getByText('Next') for pressing the button, while every other test in the same file uses getByTestId(CAMPAIGN_TOUR_STEP_TEST_IDS.NEXT_BUTTON) for the same action. This violates the "Element Selection - PREFER DATA TEST IDs" rule which states to always prefer testID props and avoid selecting by hardcoded text content. The CAMPAIGN_TOUR_STEP_TEST_IDS.NEXT_BUTTON constant is already available and used consistently elsewhere in this file. Additionally, expect(queryByText('Next')).toBeNull() uses a weak matcher — not.toBeOnTheScreen() is preferred per assertion guidelines.

 

^{Triggered by project rule: Unit Testing Guidelines}

^{Reviewed by Cursor Bugbot for commit a7f0ba8. Configure here.}

[Montoya]

Not fixing right now, will fix in another PR

[github-actions]

✅ E2E Fixture Validation — Schema is up to date
11 value mismatches detected (expected — fixture represents an existing user).
View details

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud