release: 7.64.0

.cursor/BUGBOT.md

@@ -21,3 +21,11 @@ Use the rules in the [unit testing guidelines](rules/unit-testing-guidelines.mdc
 - Check for proper imports and framework utilities from `tests/framework/index.ts`
 
 Use the rules in the [e2e-testing-guidelines](rules/e2e-testing-guidelines.mdc) to enforce the test quality and bug detection.
+
+### 3. Initial Setup - Component View Tests
+
+- **ALWAYS** load and reference [component-view-testing](rules/component-view-testing.mdc)
+- Verify test file naming pattern: `**/*.view.test.{ts,tsx,js,jsx}`
+- Check for proper use of presets and renderers from `app/util/test/component-view/`
+
+Use the rules in the [component-view-testing](rules/component-view-testing.mdc) to enforce the test quality and bug detection.

.cursor/commands/create-deeplink-handler.md

@@ -161,21 +161,21 @@ export const PREFIXES = {
 import { handle{PascalCaseName}Url } from './handle{PascalCaseName}Url';
 ```
 
-#### Step D: Add to SUPPORTED_ACTIONS enum
+#### Step D: Add to SUPPORTED_ACTIONS object
 
 **File:** `app/core/DeeplinkManager/handlers/legacy/handleUniversalLink.ts`
 
 ```typescript
-enum SUPPORTED_ACTIONS {
+const SUPPORTED_ACTIONS = {
   // ... existing actions
-  {UPPER_SNAKE_CASE} = ACTIONS.{UPPER_SNAKE_CASE},
-}
+  {UPPER_SNAKE_CASE}: ACTIONS.{UPPER_SNAKE_CASE},
+} as const;
 ```
 
 #### Step E: Add switch case (CRITICAL - Most commonly forgotten!)
 
 **File:** `app/core/DeeplinkManager/handlers/legacy/handleUniversalLink.ts`
-**Location:** Inside the switch statement (around line 254+)
+**Location:** Inside the switch (action) block (around line 358)
 
 ```typescript
 switch (action) {
@@ -203,6 +203,32 @@ const WHITELISTED_ACTIONS: SUPPORTED_ACTIONS[] = [
 ];
 ```
 
+#### Step G: Add to SUPPORTED_ACTIONS array (for isSupportedAction)
+
+**File:** `app/core/DeeplinkManager/types/deepLink.types.ts`
+
+Add the new action to the `SUPPORTED_ACTIONS` array so `isSupportedAction(action)` returns true and analytics route is not INVALID.
+
+```typescript
+export const SUPPORTED_ACTIONS = [
+  // ... existing actions
+  ACTIONS.{UPPER_SNAKE_CASE},
+] as const satisfies readonly ACTIONS[];
+```
+
+#### Step H: Map action to route (for analytics)
+
+**File:** `app/core/DeeplinkManager/util/deeplinks/deepLinkAnalytics.ts`
+
+In `mapSupportedActionToRoute`, add a case for the new action returning the appropriate `DeepLinkRoute`. If the action needs its own route: add a new value to `DeepLinkRoute` in `app/core/DeeplinkManager/types/deepLinkAnalytics.types.ts` and optionally add an entry in `routeExtractors` in deepLinkAnalytics.ts.
+
+```typescript
+case ACTIONS.{UPPER_SNAKE_CASE}:
+  return DeepLinkRoute.{ROUTE_OR_EXISTING};  // e.g. DeepLinkRoute.REWARDS or new enum value
+```
+
+**Note:** Skipping Steps G and H still allows navigation to work, but analytics will record the route as INVALID.
+
 **After completing all integration steps (full mode only), verify the handler is fully connected by:**
 
 - Checking that all files were actually modified (not just showing snippets)
@@ -239,8 +265,7 @@ adb shell am start -W -a android.intent.action.VIEW \
 
 Remind user to manually update:
 
-- `docs/readme/deeplinking.md` - Add to Supported Actions table
-- `docs/deeplink-test-urls.md` - Add test URLs
+- `docs/readme/deeplinking.md` - Add to Supported Actions table and document test URLs (e.g. in a Test URLs section) if applicable
 
 ## Naming Conventions
 
@@ -261,10 +286,10 @@ Remind user to manually update:
 - [ ] All user information collected interactively (including integration mode)
 - [ ] Handler file created with proper structure
 - [ ] Test file created with all test cases
-- [ ] **Full mode:** All integration steps (A-F) actually performed in code files
+- [ ] **Full mode:** All integration steps (A–H) actually performed in code files
 - [ ] **Full mode:** Handler verified to be hooked up and ready to use
 - [ ] **Snippets mode:** Integration snippets provided for all steps
-- [ ] **Snippets mode:** User reminded which files to modify
+- [ ] **Snippets mode:** User reminded which files to modify (including Steps G and H)
 - [ ] Test commands provided
 - [ ] Documentation reminders included
 - [ ] Switch case step emphasized as critical
@@ -278,3 +303,5 @@ Remind user to manually update:
 @app/core/DeeplinkManager/handlers/legacy/handlePerpsUrl.ts
 @app/core/DeeplinkManager/handlers/legacy/handleRewardsUrl.ts
 @app/core/DeeplinkManager/handlers/legacy/handlePredictUrl.ts
+@app/core/DeeplinkManager/types/deepLink.types.ts
+@app/core/DeeplinkManager/util/deeplinks/deepLinkAnalytics.ts

.cursor/rules/component-view-testing.mdc

@@ -10,25 +10,29 @@ alwaysApply: false
 
 Follow these rules for all component-view tests. Nested, component-specific rules may also apply.
 
-- **Mock policy**
-  - Only mock `../../../core/Engine`, `../../../core/Engine/Engine`, and `react-native-device-info`.
-  - No mocking of hooks or selectors; drive behavior via Redux state.
-  - Enforced by runtime guard in `app/util/test/testSetup.js` and ESLint override in `.eslintrc.js`.
-
-- **Framework usage (REQUIRED)**
-  - Use presets: `initialStateBridge`, `initialStateWallet`.
-  - Use renderers: `renderBridgeView`, `renderWalletView`.
-  - Use `stateFixture.ts` helpers for overrides (e.g., quotes, feature flags).
-  - Prefer `deterministicFiat: true` for exact fiat assertions.
-
-- **Navigation tests**
-  - Use `renderScreenWithRoutes` and build `state` via the preset + minimal overrides.
-  - Assert using route names from `app/constants/navigation/Routes.ts`.
-
-- **Test structure**
-  - AAA pattern with blank lines between sections.
-  - Action-oriented names (no “should”).
-  - One behavior per test; robust assertions over brittle formatting.
+## Mock Policy - MANDATORY
+
+- Only mock `../../../core/Engine`, `../../../core/Engine/Engine`, and `react-native-device-info`.
+- No mocking of hooks or selectors; drive behavior via Redux state.
+- Enforced by runtime guard in `app/util/test/testSetup.js` and ESLint override in `.eslintrc.js`.
+
+## Framework Usage - MANDATORY
+
+- Use presets: `initialStateBridge`, `initialStateWallet`.
+- Use renderers: `renderBridgeView`, `renderWalletView`.
+- Use `stateFixture.ts` helpers for overrides (e.g., quotes, feature flags).
+- Prefer `deterministicFiat: true` for exact fiat assertions.
+
+## Navigation Tests
+
+- Use `renderScreenWithRoutes` and build `state` via the preset + minimal overrides.
+- Assert using route names from `app/constants/navigation/Routes.ts`.
+
+## Test Structure - MANDATORY
+
+- AAA pattern with blank lines between sections.
+- Action-oriented names (no "should").
+- One behavior per test; robust assertions over brittle formatting.
 
 - **Execution**
   - Prefer `--coverage=false` during iteration for speed.