E2E Test Selection:
The changes modify the ReactQueryService, which is a core infrastructure component that wraps the entire app via QueryClientProvider in Root/index.tsx. The key change replaces new QueryClient() with createUIQueryClient() from the new @metamask/react-data-query package, adding an adapter that bridges Engine's controllerMessenger to the query client.

Key observations:

1. Root-level impact: ReactQueryService is instantiated at app root (Root/index.tsx), so any behavioral difference in QueryClient initialization could affect all features.
2. DATA_SERVICES is empty: The new DATA_SERVICES constant is an empty array, meaning no actual data services are registered yet. This is foundational scaffolding.
3. Ramp dependency: ReactQueryService is explicitly imported in app/components/UI/Ramp/routes.tsx, making Ramp flows a direct consumer.
4. QueryClient options preserved: The same staleTime, retry, and cacheTime options are passed through, but createUIQueryClient may add a default queryFn (visible in test assertions: queryFn: expect.any(Function)), which could affect queries that don't specify their own queryFn.
5. New package: Adding @metamask/react-data-query@^0.2.0 introduces a new dependency that needs validation.

Selected tags rationale:

• SmokeRamps: Direct consumer of ReactQueryService in Ramp routes; most likely to be affected by query client changes.
• SmokeWalletPlatform: Core wallet features that use React Query for data fetching (transaction history, trending, etc.).
• SmokeConfirmations: Transaction flows that may use React Query for data fetching.
• SmokeTrade: Swap/bridge flows that use React Query for quote fetching and token data.

Not selecting all tags because DATA_SERVICES is empty (no new data service behavior), the QueryClient options are preserved, and the change is primarily infrastructure scaffolding with low likelihood of breaking existing query patterns.

Performance Test Selection:
The ReactQueryService change replaces QueryClient initialization with createUIQueryClient, but DATA_SERVICES is empty so no new data fetching behavior is introduced. The QueryClient options (staleTime, retry, cacheTime) are preserved. While this is a data layer change, it doesn't introduce new rendering paths, list components, or critical flow changes that would meaningfully impact measured performance metrics. No performance tests are warranted.