E2E Test Selection:
All changes are within E2E test infrastructure and automation layers: Playwright adapters, context helpers, gestures, matchers, utilities, performance fixtures, MMConnect page objects (AddChainModal, DappConnectionModal, SignModal, SnapSignModal, SwitchChainModal, RN/Browser playground dapps), selectors, and related WDIO screen objects. These components are shared across nearly all Detox E2E flows: dApp connections, chain switching, signature requests, transaction confirmations, snaps interactions, and multi-chain flows. Because these are foundational abstractions used by multiple tags (Confirmations, NetworkAbstractions, NetworkExpansion, MultiChainAPI, Trade, Card, Perps, Predictions, Snaps), regressions could impact any vertical. No app production code changed, but the testing harness itself changed significantly. Therefore, a full E2E sweep is required to safely validate that the refactored framework and page objects still drive the app correctly across all domains. This is a high-risk infrastructure change rather than a feature change.

Performance Test Selection:
The performance test fixture (tests/framework/fixtures/performance/performance-fixture.ts) and shared framework utilities were modified. Although no production performance-sensitive code changed, the performance test harness itself was altered. Running all performance tags ensures that the updated fixture, setup/teardown, and shared helpers still correctly measure and execute performance scenarios without regression or false readings.