E2E Test Selection:
The changes are contained within the Perps controller layer (app/controllers/perps/):

1. errorUtils.ts: New isHyperLiquidUserNotFoundError() utility to detect when a user has no HyperLiquid account yet.

2. HyperLiquidProvider.ts: Added a new error-handling branch in #ensureUnifiedAccountEnabled() that gracefully handles the "user not found" case — caches the result with reason: 'no_hl_account' and fires analytics with NOT_APPLICABLE status instead of treating it as a real error. This is a bug fix for new Perps users who haven't yet created a HyperLiquid account.

3. TradingReadinessCache.ts: Added optional reason discriminator field to SigningOperationState and TradingReadinessCacheEntry types, propagated through get(), set(), and clearUnifiedAccount().

4. eventNames.ts: Added NOT_APPLICABLE: 'not_applicable' to PERPS_EVENT_VALUE.STATUS constants.

5. Test files: Unit tests covering the new behavior.

Tag rationale:

• SmokePerps: Directly impacted — the HyperLiquidProvider initialization flow is changed, specifically the unified account setup path that runs when users open the Perps section. The fix affects new users (no HL account) and the Add Funds flow.
• SmokeWalletPlatform: Required by SmokePerps tag description — Perps is a section inside the Trending tab, so changes to Perps views/controllers affect Trending.
• SmokeConfirmations: Required by SmokePerps tag description — Add Funds deposits are on-chain transactions that go through confirmations.

The changes are scoped to Perps internals with no impact on other wallet features (accounts, networks, browser, swaps, etc.).

Performance Test Selection:
The changes are internal error-handling improvements in the Perps controller layer. The TradingReadinessCache change adds a minor reason field to cache entries (negligible memory/performance impact). The HyperLiquidProvider change actually improves performance for new users by adding an early-exit path that prevents repeated failed API calls. No UI rendering changes, no list rendering changes, no app startup changes, and no data loading pipeline changes that would affect measurable performance metrics.