E2E Test Selection:
The changes are in app/core/Authentication/Authentication.ts, a critical core module that handles login, unlock, and password reset flows.

Key changes:

1. Refactoring: clearAuthStorageFlags() extracted as a private method - previously only called in storePassword, now also called in resetPassword. This is a behavioral change: resetPassword now additionally clears biometry/passcode storage flags and resets allowLoginWithRememberMe Redux state, plus calls updateOsAuthEnabled(false).
2. New Android biometric error handling: When unlockWallet() fails with USER_NOT_AUTHENTICATED error (Android-specific, triggered when user changes biometrics), a non-dismissible alert is shown prompting re-enablement, then lockApp({ reset: true }) is called instead of reset: false. This is a new code path.
3. New locale strings: 3 new strings for the biometric changed alert.
4. New constant: USER_NOT_AUTHENTICATED error message.

Why SmokeAccounts: This tag covers account security flows including credential management, SRP export, and wallet details. The authentication changes directly affect how accounts are secured and accessed. The resetPassword behavioral change could affect account security flows.

Why SmokeWalletPlatform: This tag covers wallet lifecycle including SRP import flows, account deletion, and multi-SRP architecture - all of which go through authentication. The resetPassword change (now clearing auth flags) could affect wallet lifecycle flows.

Why NOT all tags: The changes are well-contained to authentication internals. The new biometric error handling is Android-specific and only triggers in an edge case (biometric change). The refactoring is clean. No UI components were changed. The locale strings are new additions (no existing strings modified). The unit tests provide good coverage of the new behavior.

Performance: No performance impact expected - these are error handling and storage flag cleanup operations, not rendering or data loading changes.

Performance Test Selection:
The changes are in authentication error handling and storage flag cleanup. No UI rendering, list components, data loading, or app startup paths are affected. The new biometric alert is an edge-case error handler. No performance impact expected.