E2E Test Selection:
The only changed file is a critical CI workflow file: .github/workflows/post-merge-validation.yml. There are no application code changes (no modifications in app/, controllers, Engine, UI components, or test infrastructure). Therefore, there is no direct functional impact on wallet features.

However, because this is a CI workflow change that likely orchestrates post-merge validation and test execution, the primary risk is pipeline misconfiguration (e.g., jobs not triggered, incorrect test matrix, environment issues, missing artifacts, or mis-scoped tags). To safely validate that the workflow still executes all required coverage correctly, we should run the full E2E smoke suite.

Running the full set of smoke tags ensures:

• All major feature verticals (accounts, confirmations, trading, network expansion, snaps, identity, etc.) are properly triggered by the updated workflow.
• Tag-based filtering and job routing inside CI still function correctly.
• No regressions in workflow configuration (e.g., conditional execution, environment setup, secrets, build variants like Flask).

There is no indication of feature-specific changes that would justify narrowing scope to a subset of tags. Since this change affects CI orchestration rather than product logic, broad validation is the safest minimal-risk strategy.

No additional dependent tag adjustments were required beyond including all available E2E smoke tags.

Performance tests are not selected because:

• No app runtime code, rendering logic, controllers, or startup paths were modified.
• No performance test infrastructure (tests/performance/) was changed.
• Workflow-level changes do not affect app performance characteristics.

Thus, full E2E smoke coverage is recommended, with no performance test execution required.

Performance Test Selection:
No application code, rendering logic, controllers, or performance test infrastructure was modified. The change is limited to a CI workflow file, which does not affect runtime performance characteristics of the app. Therefore, no performance tests are required.