{
  "prNumber": 47903,
  "prTitle": "release: 13.58.0",
  "generatedAt": "2026-11-16T16:17:19.431Z",
  "modelUsed": "gpt-5",
  "summary": {
    "totalFilesChanged": 1041,
    "totalCommitsInRelease": 150,
    "releaseRiskScore": "51/100",
    "highRiskScenarios": 5,
    "mediumRiskScenarios": 6
  },
  "testScenarios": {
    "cherryPickScenarios": [
      {
        "area": "Transaction Confirmations — Money Account pay-token balance checks",
        "riskLevel": "high",
        "testSteps": [
          "1. Using a profile with Money Account enabled and funded with a small decimal balance of a pay-token, initiate a payment/transaction that uses Money Account with an amount exactly equal to the available balance and navigate to the confirmation screen.",
          "2. Verify the Confirm/Submit action is enabled (no false 'insufficient funds' due to precision) and the transaction can be submitted.",
          "3. Increase the amount slightly above the balance and confirm the UI blocks submission with an insufficient funds message.",
          "4. As a regression check, perform a similar transaction using a standard account balance and confirm behavior is unchanged."
        ],
        "whyThisMatters": "Cherry-pick 47981 fixes precision issues by comparing Money Account pay-token balances as strings; a mistake here can incorrectly block valid transactions or allow overspending."
      },
      {
        "area": "Token Management — Custom token import mainnet-address warning behavior",
        "riskLevel": "medium",
        "testSteps": [
          "1. Switch to a non-Mainnet network (e.g., Sepolia), open Import tokens, and paste a known Mainnet ERC-20 address (e.g., a popular mainnet token).",
          "2. Verify a non-blocking warning appears about providing a Mainnet address while on another network, and proceed with the import.",
          "3. Confirm the token is added to the current network’s list (likely with zero balance) and the flow completes without being blocked.",
          "4. Switch to Mainnet and repeat with the same address; verify no cross-network warning blocks import. Try an invalid address and confirm the flow is still blocked appropriately."
        ],
        "whyThisMatters": "Cherry-pick 47983 fixes the custom token import flow to warn but not block when a Mainnet address is used on other networks; regressions could either block legitimate imports or allow silent, unsafe imports without proper warning."
      }
    ],
    "initialScenarios": [
      {
        "area": "State Migrations — Basic functionality consolidation (Migration 235)",
        "riskLevel": "high",
        "testSteps": [
          "1. Start from a pre-13.58 profile where the legacy child preferences for token/NFT detection and NFT media were previously disabled (seed a 13.57 profile representing that state), then upgrade the same profile to 13.58.",
          "2. Open Settings → Security & privacy and verify the new Basic functionality control is OFF.",
          "3. Open the NFTs tab and confirm it shows the off-state with the control that routes to Privacy settings (no grid of NFTs, no media).",
          "4. Turn Basic functionality ON and return to the home Assets/NFTs; confirm the NFTs grid renders and detection resumes without needing a restart.",
          "5. Lock and unlock the wallet, then re-check that the Basic functionality state persisted."
        ],
        "whyThisMatters": "A faulty migration can silently alter user privacy defaults or break token/NFT detection, causing loss of trust or missing assets."
      },
      {
        "area": "State Migrations — Preserve previous ON state (Migration 235)",
        "riskLevel": "high",
        "testSteps": [
          "1. Start from a pre-13.58 profile where legacy detection and NFT media were previously enabled (seed a 13.57 profile representing that state), then upgrade the same profile to 13.58.",
          "2. Open Settings → Security & privacy and verify Basic functionality is ON by default post-upgrade.",
          "3. On the Assets tab, switch networks (e.g., Mainnet → Sepolia) and confirm auto-detected tokens still appear as expected.",
          "4. On the NFTs tab, confirm media renders and items remain visible.",
          "5. Restart the extension and verify the ON state and behavior persist."
        ],
        "whyThisMatters": "Incorrect defaulting after migration could unexpectedly disable features users rely on, or expose privacy risks if flipped the wrong way."
      },
      {
        "area": "Security & Privacy — Social-login wallet restriction on Basic functionality",
        "riskLevel": "high",
        "testSteps": [
          "1. Log in with a social-login wallet profile that has been upgraded to 13.58.",
          "2. Navigate to Settings → Security & privacy and inspect the Basic functionality control.",
          "3. Verify that the control cannot be turned OFF for social-login wallets (disabled state or no toggle present).",
          "4. Confirm the NFTs tab shows active state and detection behaves as expected (since it must remain on)."
        ],
        "whyThisMatters": "If social-login wallets can disable Basic functionality, users may enter unsupported states leading to broken UX or loss of key features."
      },
      {
        "area": "Token Management — Asset list control bar refactor: Manage tokens (hide/unhide)",
        "riskLevel": "high",
        "testSteps": [
          "1. On the Assets tab, use the new control bar to open Manage tokens.",
          "2. Hide a low- or zero-balance token and confirm it is removed from the list after saving.",
          "3. Switch networks (e.g., Mainnet → Sepolia) and verify the hide state is scoped appropriately per network.",
          "4. Return to Manage tokens, unhide the token, and confirm it reappears.",
          "5. Lock/unlock the wallet and verify the hidden/visible state persists correctly."
        ],
        "whyThisMatters": "A major UI refactor can regress token visibility management, confusing users or hiding important assets unintentionally."
      },
      {
        "area": "Token Management — Asset list control bar refactor: Search/filter",
        "riskLevel": "medium",
        "testSteps": [
          "1. In the Assets tab, use the control bar’s search to query by token symbol (e.g., USDC) and verify the list filters in real time.",
          "2. Clear the search and confirm the full list returns without layout glitches.",
          "3. Search for a token with zero balance and ensure it still appears if it is being tracked.",
          "4. Switch networks and repeat a search to confirm results update for the active network only."
        ],
        "whyThisMatters": "Search/filter regressions can make it hard to find assets, especially across networks and for zero-balance tokens."
      },
      {
        "area": "Token/DeFi Actions — Asset list control bar: DeFi options menu",
        "riskLevel": "medium",
        "testSteps": [
          "1. Open the DeFi options menu from the control bar on the Assets tab.",
          "2. Trigger each visible action (e.g., Swap, Bridge, Buy) and verify it routes to the correct view with the expected pre-selected network/token when applicable.",
          "3. Cancel out of each flow and confirm you return to the Assets list without state corruption.",
          "4. Repeat once after switching networks to ensure routing respects the active chain."
        ],
        "whyThisMatters": "Misrouted DeFi actions can cause failed transactions, wrong network usage, or user funds at risk."
      },
      {
        "area": "Network Management — Test network visibility and switching (init refactors)",
        "riskLevel": "medium",
        "testSteps": [
          "1. Go to Settings → Advanced and enable Show test networks.",
          "2. Open the network picker and confirm test networks (e.g., Sepolia) appear and can be selected.",
          "3. Switch between Mainnet and a test network; verify assets and activity reflect the selected chain.",
          "4. Disable Show test networks and confirm test networks disappear from the picker without breaking the current network state."
        ],
        "whyThisMatters": "Refactors around network initialization can break chain availability or cause asset lists to desync across networks."
      },
      {
        "area": "Analytics/Telemetry — MetaMetrics consent and persistence",
        "riskLevel": "medium",
        "testSteps": [
          "1. Fresh install: during onboarding, decline MetaMetrics data collection.",
          "2. After onboarding, open Settings → Security & privacy and confirm the participation setting reflects your choice.",
          "3. Toggle participation ON, lock and unlock the wallet, and confirm the setting persists.",
          "4. Perform a common action (e.g., open Swap) and ensure no blocking errors or unusual prompts occur."
        ],
        "whyThisMatters": "Changes to analytics controllers can lead to incorrect consent states or runtime errors that impact core flows."
      },
      {
        "area": "On/Off Ramp — Buy flow entry points (ramps integration changes)",
        "riskLevel": "medium",
        "testSteps": [
          "1. From the Assets tab on Mainnet, click Buy and choose a provider.",
          "2. Proceed to the quote screen and confirm quotes load and the selected asset/network are correct.",
          "3. Back out/cancel and ensure you return to the Assets list without a blank or stuck screen.",
          "4. Repeat on a test network and confirm the UI communicates availability/unsupported states correctly."
        ],
        "whyThisMatters": "Ramps integration regressions can strand users in broken purchase flows or present wrong chain/asset combinations."
      }
    ]
  }
}