E2E Test Selection:
The changes are isolated to the SDKConnectV2 compression utility (compression-utils.ts) which handles decompression of deeplink payloads for mobile wallet protocol connections. The modifications:

1. Security Enhancement: Switches from inflate to streaming Inflate from pako to prevent decompression bomb attacks by tracking cumulative output size
2. Size Limit: Adds a 5MB maximum decompressed payload size limit
3. Better Error Handling: Adds proper error handling for size limit exceeded and decompression failures

The changes are:

• Internal implementation changes that don't alter the external API for valid payloads
• Well-covered by updated unit tests that verify round-trip compression, size limit enforcement, and corrupt data handling
• Isolated to the SDKConnectV2 module which handles deeplink-based dApp connections (different from browser-based dApp connections)

None of the available E2E test tags directly test SDKConnectV2 deeplink handling. The existing E2E tests focus on browser-based dApp connections (SmokeNetworkExpansion, SmokeMultiChainAPI) which use different code paths. The SDKConnectV2 module is used for QR code scanning and SDK disconnect modal, but these flows aren't covered by the available test tags.

Since this is a security fix with comprehensive unit test coverage and doesn't change behavior for valid payloads, no E2E tests are required.

Performance Test Selection:
The changes are to a compression utility function used during deeplink parsing for SDK connections. This is a one-time operation during connection establishment, not a frequently executed path that would impact app performance. The change from inflate to streaming Inflate is primarily for security (preventing decompression bombs) rather than performance optimization. No performance-sensitive areas like UI rendering, list loading, or critical user flows are affected.