fix: Polish Earn toast for 8.6.0 release

[amandaye0h]

Description

Polishes Earn toast call sites for the 8.6.0 release so they align with the shared toast pattern (Confirmation icon, success/error icon colors, and default toast chrome instead of custom background colors).

Updates the Cash mUSD empty-state Merkl claim error toast label to bold for consistency with other plain toasts.

Changelog

CHANGELOG entry: Polished toast styling for consistency in the 8.6.0 release

Related issues

Fixes:

Related toast polish PRs for 8.6.0:

• fix: Polish Design System Engineers toast for 8.6.0 release #33765 — Design System Engineers
• fix: Polish Card toast for 8.6.0 release #33766 — Card
• fix: Polish Predict toast for 8.6.0 release #33767 — Predict
• fix: Polish Money Movement toast for 8.6.0 release #33769 — Money Movement
• fix: Polish Metamask Assets toast for 8.6.0 release #33770 — Metamask Assets
• fix: Polish Mobile Core UX toast for 8.6.0 release #33771 — Mobile Core UX
• fix: Polish Engagement toast for 8.6.0 release #33772 — Engagement
• fix: Polish Social AI toast for 8.6.0 release #33773 — Social AI
• fix: Polish Web3Auth toast for 8.6.0 release #33774 — Web3Auth
• fix: Polish Watchlist toast for 8.6.0 release #33791 — Watchlist

Manual testing steps

Feature: Cash claim error toast
  Scenario: Merkl claim error
    Given a Merkl claim error occurs on the Cash empty state
    When the toast appears
    Then the error label is bold

Screenshots/Recordings

Before

Screen.Recording.2026-07-28.at.3.28.29.PM.mov

After

Screen.Recording.2026-07-28.at.3.18.29.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.

Made with Cursor

[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.

[metamask-ci]

PR template — items to address before "Ready for review"

Warnings — informational, address before merging:

• Related issues section is empty. Add Fixes: #123 / Closes: <URL> / Refs: <Jira key>, or write a short rationale after the colon.

See docs/readme/ready-for-review.md for the full Definition of Ready for Review.

[github-actions]

🔍 Smart E2E Test Selection

• Selected E2E tags: None (no tests recommended)
• Selected Performance tags: None (no tests recommended)
• Risk Level: low
• AI Confidence: 95%

click to see 🤖 AI reasoning details

E2E Test Selection:
The only changed file is app/components/Views/Homepage/Sections/Cash/CashGetMusdEmptyState.tsx. The diff shows a single-line change: isBold: false → isBold: true for a toast label option when displaying a Merkl claim error. This is a purely cosmetic/styling change — it only affects whether the error toast text is rendered in bold. There are no functional logic changes, no API changes, no navigation changes, and no shared component modifications. Per the cosmetic changes rule, bold/styling-only changes have zero functional impact and must not trigger additional test selection. No E2E tags are warranted.

Performance Test Selection:
The change is a single cosmetic styling property (isBold: false → true) in a toast label. This has no measurable impact on app performance, rendering times, or any performance-sensitive flows.

View GitHub Actions results

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

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

See analysis details on SonarQube Cloud