E2E Test Selection:
These changes modify 9 onboarding page objects and WalletView.ts — all critical test infrastructure files.

Why all tags are selected:

1. Onboarding page objects are universally shared: The wallet.flow.ts imports ALL of the changed onboarding page objects (CreatePasswordView, ImportWalletView, MetaMetricsOptInView, OnboardingSheet, OnboardingSuccessView, OnboardingView, ProtectYourWalletView, SkipAccountSecurityModal, TermsOfUseModal) and exposes loginToApp, CreateNewWallet, and importWalletWithRecoveryPhrase functions.

2. loginToApp is used by virtually every smoke test: Confirmed via grep — tests in swap, confirmations, ramps, multichain, predict, trending, identity, accounts, perps, snaps, and more all call loginToApp() from wallet.flow.ts.

3. Migration pattern introduces risk: The changes migrate from simple Detox-only element getters to encapsulated() wrappers with encapsulatedAction() dispatch. While backward-compatible for Detox, any subtle behavioral change (e.g., in asDetoxElement() unwrapping, timing differences in UnifiedGestures vs Gestures) could break the onboarding flow for all tests.

4. WalletView.ts changes: New accountNameLabelText and accountNameLabelInput encapsulated getters, plus longPressAccountNameLabel and editAccountNameLabel methods. WalletView is the main wallet screen used by all tests after login.

5. Specific high-risk changes:

   • tapContinueButton in ImportWalletView now uses UnifiedGestures.waitAndTap unconditionally for onboarding=true path (previously used Gestures.tap)
   • tapIUnderstandCheckBox in SkipAccountSecurityModal now uses UnifiedGestures.waitAndTap (previously Gestures.waitAndTap)
   • tapAgreeButton in MetaMetricsOptIn now delegates to tapIAgreeButton which has different Detox behavior (swipe then tap)
   • New proceedWithoutWalletSecure() convenience method in SkipAccountSecurityModal

6. SmokeWalletPlatform directly: Seedless tests (google/apple login flows) use OnboardingView and OnboardingSheet directly; analytics tests use CreateNewWallet/importWalletWithRecoveryPhrase.

7. FlaskBuildTests: Snaps tests also use loginToApp from wallet.flow.ts.

The conservative approach of running all tags is warranted because the onboarding flow is the entry point for essentially all E2E tests.

Performance Test Selection:
The onboarding page objects (CreatePasswordView, ImportWalletView, OnboardingView, etc.) are directly used in the onboarding performance test flow. Changes to how these page objects interact with elements (migration to encapsulated/UnifiedGestures) could affect timing measurements in the @PerformanceOnboarding test. Other performance tests (Login, Launch, AccountList, Swaps, etc.) use loginToApp which relies on these page objects, but their primary measurement focus is post-onboarding. @PerformanceOnboarding is the most directly impacted.