E2E Test Selection:
The changed files are all within the Rewards/Campaigns UI subsystem, specifically:

1. CampaignLeaderboard.tsx - New shared base component providing generic leaderboard row rendering (CampaignLeaderboardEntryRow, CampaignLeaderboardSkeleton, CampaignLeaderboardNeighborSeparator) used by both Ondo and Perps leaderboards.

2. OndoLeaderboard.tsx - Ondo campaign-specific leaderboard that imports from the new shared CampaignLeaderboard component and uses ONDO_GM_TIER_MAX_WINNERS constant.

3. PerpsTradingCampaignLeaderboard.tsx - Perps trading campaign leaderboard that uses the shared CampaignLeaderboard components and PERPS_TRADING_MAX_WINNERS/HYPERTRACKER_ATTRIBUTION_URL constants. Also navigates to Routes.BROWSER.HOME for HyperTracker attribution.

4. ondoCampaignConstants.ts - Constants and eligibility logic for Ondo GM campaigns.

5. perpsCampaignConstants.ts - Constants for Perps trading campaigns including qualification threshold and HyperTracker URL.

6. Test files - Unit tests for the above components.

Tag Selection Rationale:

• SmokePerps: Directly relevant - PerpsTradingCampaignLeaderboard is a core component of the Perps trading campaign flow. The leaderboard is embedded in PerpsTradingCampaignDetailsView, PerpsTradingCampaignStatsView, and PerpsTradingCampaignLeaderboardView. Changes to constants (PERPS_TRADING_MAX_WINNERS, PERPS_QUALIFICATION_NOTIONAL_USD) could affect display logic.
• SmokeWalletPlatform: Required per SmokePerps tag description - "Perps is also a section inside the Trending tab (SmokeWalletPlatform); changes to Perps views affect Trending. When selecting SmokePerps, also select SmokeWalletPlatform."

Not Selected:

• SmokeConfirmations: Not selected because these are leaderboard display components, not transaction confirmation flows. The Add Funds flow (which triggers confirmations) is not modified here.
• No E2E tests directly cover the Rewards leaderboard components (confirmed by grep), so the risk of breaking existing E2E tests is low.
• The changes are self-contained within the Rewards feature and don't touch shared navigation, Engine, controllers, or other critical paths.

Performance Test Selection:
The changes are UI component additions/refactors for campaign leaderboard displays within the Rewards feature. These are standard list rendering components with no significant performance implications - they render a fixed number of rows (max 20) with simple text and skeleton states. No performance-sensitive paths like account lists, app startup, login flows, or heavy data loading are affected.