Merge branch 'main' into fix/82818

Author: nkdengineer

.claude/agents/deploy-blocker-investigator.md

@@ -129,6 +129,10 @@ removeDeployBlockerLabel.sh "$ISSUE_URL" DeployBlocker      # For Frontend bugs
 
 Call scripts by name only (e.g., `removeDeployBlockerLabel.sh`), not with full paths.
 
+### Step 8: Assign contributors
+
+When a causing PR is identified with medium or high confidence, assign the PR author and all approving reviewers to the deploy blocker issue using `gh issue edit "$ISSUE_URL" --add-assignee`. Extract approving reviewers from `gh pr view <PR_NUMBER> --json reviews`.
+
 ---
 
 ## Decision Tree
@@ -182,6 +186,7 @@ Post ONE comment using this exact format:
 Brief explanation of why this recommendation (1-2 sentences).
 
 
+**Assigned**: @author (PR author), @reviewer (approving reviewer) — or omit if no causing PR identified
 **Labels**: [Describe any label changes made]
 
 <details>

.claude/commands/investigate-deploy-blocker.md

@@ -1,5 +1,5 @@
 ---
-allowed-tools: Bash(gh issue view:*),Bash(gh issue comment:*),Bash(gh issue list:*),Bash(gh pr view:*),Bash(gh pr list:*),Bash(gh pr diff:*),Bash(gh api:*),Bash(git log:*),Bash(git show:*),Bash(git blame:*),Bash(removeDeployBlockerLabel.sh:*),Glob,Grep,Read
+allowed-tools: Bash(gh issue view:*),Bash(gh issue comment:*),Bash(gh issue edit:*),Bash(gh issue list:*),Bash(gh pr view:*),Bash(gh pr list:*),Bash(gh pr diff:*),Bash(gh api:*),Bash(git log:*),Bash(git show:*),Bash(git blame:*),Bash(removeDeployBlockerLabel.sh:*),Glob,Grep,Read
 description: Investigate a deploy blocker issue to find the causing PR and recommend resolution
 ---
 

.claude/settings.json

@@ -38,7 +38,21 @@
             "mcp__playwright__browser_wait_for",
             "mcp__playwright__browser_close",
             "mcp__playwright__browser_evaluate",
-            "mcp__playwright__browser_handle_dialog"
+            "mcp__playwright__browser_handle_dialog",
+            "mcp__sentry__find_organizations",
+            "mcp__sentry__find_projects",
+            "mcp__sentry__find_releases",
+            "mcp__sentry__find_teams",
+            "mcp__sentry__get_doc",
+            "mcp__sentry__get_event_attachment",
+            "mcp__sentry__get_issue_details",
+            "mcp__sentry__get_issue_tag_values",
+            "mcp__sentry__get_trace_details",
+            "mcp__sentry__search_docs",
+            "mcp__sentry__search_events",
+            "mcp__sentry__search_issue_events",
+            "mcp__sentry__search_issues",
+            "mcp__sentry__whoami"
         ]
     },
     "enabledPlugins": {

.claude/skills/coding-standards/rules/clean-react-0-compiler.md

@@ -101,6 +101,8 @@ Before flagging, verify that the file actually compiles with React Compiler:
 check-compiler.sh <filepath>
 ```
 
+**IMPORTANT:** Run `check-compiler.sh` exactly as shown above - by name only, without an absolute path or `bash` prefix. The script is already on `$PATH`.
+
 If the output contains **"Failed to compile"** for the file under review, the rule **does not apply** — the author may have no alternative to manual memoization until the compilation issue is resolved.
 
 #### Condition

.claude/skills/coding-standards/rules/clean-react-1-composition-over-config.md

@@ -462,11 +462,11 @@ In all cases, the rule applies to: **new components**, **new features added to e
 - The optional prop is used for logic beyond just conditional rendering (e.g., computing derived values, passed to callbacks, used in multiple places within the component)
 - The component is a thin wrapper around a platform primitive (e.g., wrapping `TextInput`, `ScrollView`, `Pressable`) — these naturally pass through configuration props
 - Items come from **runtime data** (API responses, user-generated content, Onyx collections) — dynamic data must be mapped
-- The array is used with **list components** (e.g., `FlatList`, `SectionList`, or custom wrappers) — these require data arrays by design
+- The array is used with **list components** (e.g., `FlatList`, or custom wrappers) — these require data arrays by design
 - Items are truly **homogeneous** (same shape, same behavior, only values differ) and the count is **unbounded** (e.g., list of chat messages, search results)
 - The array is a **framework requirement** (e.g., React Navigation screen config, form validation rules)
 - The `ReactNode` prop is `children` itself — `children` is the foundation of composition, not configuration
-- The render function is a **list component callback** (`renderItem` on `FlatList`, `SectionList`, `DraggableList`) — these are framework requirements
+- The render function is a **list component callback** (`renderItem` on `FlatList`, `DraggableList`) — these are framework requirements
 - The render function receives **per-item runtime data** from a dynamic collection (e.g., `renderSuggestionMenuItem(item, index)`) — this is list-style rendering, not slot configuration
 
 **Search Patterns** (hints for reviewers):

.claude/skills/coding-standards/rules/perf-1-no-spread-in-renderitem.md

@@ -37,7 +37,7 @@ title: No spread in list item's renderItem
 
 Flag ONLY when ALL of these are true:
 
-- Code is inside a renderItem function (function passed to FlatList, SectionList, etc.)
+- Code is inside a renderItem function (function passed to FlatList, etc.)
 - A spread operator (...) is used on an object
 - That object is being passed as a prop to a component
 - The spread creates a NEW object literal inline

.claude/skills/sentry/SKILL.md

@@ -0,0 +1,48 @@
+---
+name: sentry
+description: Analyze Sentry issues, spans, crashes, and performance metrics. Use when user requests check in Sentry, asks about performance metrics and spans or asks about crash rates.
+---
+
+# Sentry 
+
+## When to Use This Skill
+
+Use Sentry skill when:
+- User requests any data from Sentry
+- User asks about performance metrics or span summary
+- User want to compare metrics between any date ranges
+- User asks about latest production crashes and issues
+- User want to investigate profiles or traces from production sessions
+
+## Sentry MCP
+
+The Sentry MCP server is configured in `.mcp.json` and gives Claude Code direct access to Sentry.
+
+### Prerequisites
+
+**Setup** (one-time per engineer): On first use, Claude Code will open a browser OAuth login to Sentry. Sign in and authorize — no manual token setup required.
+
+### Available MCP Tools
+
+Use these tools for data analysis:
+
+| Tool | Purpose |
+|------|---------|
+| `mcp__sentry__find_releases` | Find release versions for scoping queries |
+| `mcp__sentry__search_issues` | Search for errors/crashes by query, project, date range |
+| `mcp__sentry__search_events` | Query raw events/spans (performance data, durations) |
+| `mcp__sentry__search_issue_events` | Get individual events for a known issue ID |
+| `mcp__sentry__get_issue_tag_values` | Inspect tag distributions (e.g. device, version) on an issue |
+| `mcp__sentry__get_sentry_resource` | Fetch a specific Sentry resource by URL/ID |
+
+**Do not use** `mcp__sentry__analyze_issue_with_seer` — AI analysis is out of scope for this skill.
+
+Always use:
+- **org slug**: `expensify`
+- **project slug**: `app`
+
+## Example uses
+
+- "Search Sentry for crashes in the last 24h related to expense creation"
+- "Get details on Sentry issue APP-123"
+- "Compare P90 of ManualAppStartup durations between last two weeks"

.env.example

@@ -44,5 +44,6 @@ FB_PROJECT_ID=YOUR_PROJECT_ID
 GITHUB_TOKEN=YOUR_TOKEN
 OPENAI_API_KEY=YOUR_TOKEN
 
+SENTRY_DSN=https://7b463fb4d4402d342d1166d929a62f4e@o4510228013121536.ingest.us.sentry.io/4510228107427840
 SENTRY_AUTH_TOKEN=SENTRY_AUTH_TOKEN
 SENTRY_ALLOW_FAILURE=true

.env.production

@@ -7,7 +7,6 @@ PUSHER_APP_KEY=268df511a204fbb60884
 USE_WEB_PROXY=false
 ENVIRONMENT=production
 SEND_CRASH_REPORTS=true
-
 FB_API_KEY=AIzaSyBrLKgCuo6Vem6Xi5RPokdumssW8HaWBow
 FB_APP_ID=1:1008697809946:web:08de4ecb7656b7235445a3
 FB_PROJECT_ID=expensify-mobile-app

.github/ISSUE_TEMPLATE/Standard.md

@@ -1,7 +1,7 @@
 ---
 name: Standard issue template
 about: A standard template to follow when creating a new issue in this repository
-labels: Bug, Daily, External
+labels: Bug, Daily
 ---
 
 If you haven’t already, check out our [contributing guidelines](https://github.com/Expensify/ReactNativeChat/blob/main/contributingGuides/CONTRIBUTING.md) for onboarding and email contributors@expensify.com to request to join our Slack channel!