feat: Add Perps Withdraw button into Developer Options, show new Perps Withdraw UI

[dan437]

Description

Adds the UI scaffolding for the Perps Withdraw confirmation flow. When triggered from Developer Options, the "Perps Withdraw" button navigates to a full-screen CustomAmountInfo confirmation page that displays the user's available Perps balance and uses the post-quote "Receive as" token picker pattern (same as Predict Withdraw).

This is the UI-only foundation — the end-to-end withdrawal execution (HyperLiquid signatures, Relay integration) will follow in a subsequent PR.

Changes:

• Added "Perps Withdraw" button and useAddPerpsTransactionBatch hook in Developer Options
• Created PerpsWithdrawInfo component that wires CustomAmountInfo with Perps balance display
• Created PerpsWithdrawBalance component showing available Perps balance from live account data
• Added perpsWithdraw to FULL_SCREEN_CONFIRMATIONS and POST_QUOTE_TRANSACTION_TYPES
• Added perpsWithdraw routing in info-root.tsx
• Updated useButtonLabel to show "Withdraw" for perpsWithdraw transactions
• Added locale strings for Perps Withdraw title and available balance

Changelog

CHANGELOG entry: Add Perps Withdraw button into Developer Options, show new Perps Withdraw UI

Related issues

Fixes: https://consensyssoftware.atlassian.net/browse/CONF-1072

Manual testing steps

Feature: Perps Withdraw confirmation UI

  Background:
    Given I am logged into MetaMask Mobile
    And I have Developer Options enabled (export MM_ENABLE_SETTINGS_PAGE_DEV_OPTIONS="true" in .js.env)

  Scenario: user triggers Perps Withdraw from Developer Options
    Given I am on the Developer Options screen (Settings -> Developer options)
    And I scroll to the Perps Withdraw section

    When user taps the "Withdraw" button under "Perps Withdraw"
    Then the Perps Withdraw confirmation page should appear
    And the page title should show "Withdraw"
    And the available Perps balance should be displayed
    And the "Withdraw" action button should be visible at the bottom

Screenshots/Recordings

Before

N/A

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.

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

Medium Risk
Adds a new perpsWithdraw transaction type path through the confirmations UI (routing, labels, constants) and a developer-only trigger that creates batched transactions; changes are mostly UI scaffolding but touch confirmation flow selection logic and transaction batching.

Overview
Introduces a Perps Withdraw confirmation flow scaffold: a new Developer Options button triggers a perpsWithdraw transaction batch on Arbitrum USDC and navigates into the Perps confirmation stack.

Adds a new PerpsWithdrawInfo full-screen CustomAmountInfo view that registers Arbitrum USDC, uses the post-quote Receive as pattern, and shows an available Perps balance via the new PerpsWithdrawBalance component.

Updates confirmations plumbing to recognize TransactionType.perpsWithdraw (info routing, full-screen + post-quote type lists, withdraw button labeling, locales) and adds targeted unit tests/snapshots. Also bumps @metamask/bridge-status-controller and @metamask/transaction-controller dependency versions.

^{Written by Cursor Bugbot for commit 6d73fcc. This will update automatically on new commits. 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.

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

[github-actions]

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

[github-actions]

🔍 Smart E2E Test Selection

• Selected E2E tags: SmokeAccounts, SmokeConfirmations, SmokeIdentity, SmokeNetworkAbstractions, SmokeNetworkExpansion, SmokeTrade, SmokeWalletPlatform, SmokeCard, SmokePerps, SmokeRamps, SmokeMultiChainAPI, SmokePredictions, FlaskBuildTests
• Selected Performance tags: @PerformanceAccountList, @PerformanceOnboarding, @PerformanceLogin, @PerformanceSwaps, @PerformanceLaunch, @PerformanceAssetLoading, @PerformancePredict, @PerformancePreps
• Risk Level: high
• AI Confidence: 100%

click to see 🤖 AI reasoning details

E2E Test Selection:
Hard rule (controller-version-update): @MetaMask controller package version updated in package.json: @metamask/bridge-status-controller, @metamask/transaction-controller. Running all tests.

Performance Test Selection:
Hard rule (controller-version-update): @MetaMask controller package version updated in package.json: @metamask/bridge-status-controller, @metamask/transaction-controller. Running all tests.

View GitHub Actions results

[sonarqubecloud]

Quality Gate passed

Issues
2 New issues
0 Accepted issues

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

See analysis details on SonarQube Cloud