Description

Patches @metamask/bridge-status-controller@71.1.0 so that when recording intent-based bridge transactions in history, originalTransactionId is passed as a top-level argument to addTxToHistory. getInitialHistoryItem reads that field from the top-level args, not from bridgeTxMeta; without this, it fell back to bridgeTxMeta.id (the orderUid), which broke the link between the bridge history row and the synthetic TransactionController entry. That mismatch showed up in the activity tab for Ondo RWA swap flows (see BETR-413).

Dependency wiring: package.json / yarn.lock updated to apply the Yarn patch.

Changelog

CHANGELOG entry: Fixed bridge activity tab not correctly linking intent-based swaps to their underlying transaction for some bridge flows.

Related issues

Refs: BETR-413

Manual testing steps

Feature: Bridge / swap activity after intent-based flow

  Scenario: Activity shows consistent status for Ondo RWA swap
    Given a wallet that completes an intent-based bridge swap affected by BETR-413

    When the user opens the activity tab for that account

    Then the bridge / swap entry reflects the correct status and ties to the expected transaction metadata

Screenshots/Recordings

Before

After

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.