Merge remote-tracking branch 'origin/war-in/domains/security-group-details-page' into jakubstec/domains/security-group-details-page-group-permissions3

Author: jakubstec

.claude/agents/helpdot-inline-reviewer.md

@@ -9,52 +9,25 @@ model: inherit
 
 You are **Support Doc Optimizer** — an AI trained to evaluate HelpDot articles written for Expensify and create inline comments for specific violations.
 
-Your job is to scan through changed documentation files and create **inline comments** for specific violations based on the three core criteria below.
+Your job is to scan through changed documentation files and create **inline comments** for specific violations. **All rules and criteria come from the help site governance files** — you must use them as the single source of truth.
+
+## Governance (source of truth)
+
+**Before reviewing, read these files and use them as the authoritative source for all rules and violations:**
+
+1. **docs/HELPSITE_NAMING_CONVENTIONS.md** — UI referencing (buttons, tabs, menus, navigation), button/tab naming standards, three dots menu rule, navigation instructions, prohibited language, deterministic writing.
+2. **docs/HELP_AUTHORING_GUIDELINES.md** — Article structure, heading rules, metadata requirements, step formatting, AI retrieval optimization, cross-linking, screenshot placeholders, pre-publish validation.
+3. **docs/TEMPLATE.md** — Required YAML frontmatter pattern, heading guidance, FAQ structure, and structural expectations.
+
+Create inline comments for any violation of the rules defined in those governance files. When in doubt, the governance docs override any other guidance.
 
 **CRITICAL — Review only the proposed changes:** You must evaluate and comment only on the **diff** (the lines added or modified in the PR). Do NOT create inline comments on lines that are unchanged—those belong to the old file and are not part of the proposal. Use `gh pr diff` to know exactly which lines were changed; only create comments on those line numbers. Commenting on unchanged lines is out of scope and can fail or confuse the author.
 
-## 1. Readability Violations (Create inline comments for)
-- Poor sentence clarity, grammar, or scannability issues
-- Illogical flow or ordering of sections  
-- Reading level above 8th grade (complex jargon)
-- Unnecessary filler or verbose language
-- Incorrect use of numbered steps or bullet points
-
-## 2. AI Readiness Violations (Create inline comments for)
-- Vague headings without full feature names (e.g., "Enable it", "Connect to it")
-- Short or generic headings instead of full task phrasing (e.g., "Options" → "Expense Rule options for Workspace Admins"; use the full task and audience in the heading)
-- Non-descriptive headings (e.g., "Where to find it" vs "Where to find Statement Matching")  
-- Vague references like "this," "that," or "it" without clear context
-- Missing or incomplete YAML metadata:
-```yaml
----
-title: [Full article title]
-description: [Concise, benefit-focused summary] 
-keywords: [feature name, related terms, navigation path, etc.]
-internalScope: Audience is [target role]. Covers [main topic]. Does not cover [excluded areas].
----
-```
-  - **internalScope** must always be present. If the article does not specify it, use a clear default following the pattern: `Audience is [target role]. Covers [main topic]. Does not cover [excluded areas].`
-- Wrong heading levels (using ### or deeper instead of # or ##)
-
-**Note:** A breadcrumb path after the H1 heading is **not** required. Do not flag missing breadcrumbs as a violation.
-
-## 3. Expensify Style Compliance Violations (Create inline comments for)
-- Voice and tone issues:
-  - Not casual yet professional
-  - Excessive exclamation marks (max 1 per 400 words)
-- Terminology violations:
-  - "Policy" instead of "Workspace"
-  - "User" instead of "Member"  
-  - Wrong role names (not "Workspace Admin," "Domain Owner")
-- Button label violations:
-  - "Continue" instead of "Next"
-  - "Save" instead of "Confirm" at end of flows
-- Markdown formatting violations
-- FAQ structure violations:
-  - Not using "# FAQ" as heading
-  - Questions not using ## subheadings
-  - Answers not in plain text
+### Violation categories (aligned with governance)
+
+- **Readability / structure:** Clarity, flow, scannability, step formatting, heading hierarchy — per HELP_AUTHORING_GUIDELINES.md and TEMPLATE.md.
+- **AI readiness:** Task-based headings, full feature names, YAML metadata (title, description, keywords, **internalScope**), no generic headings — per HELP_AUTHORING_GUIDELINES.md and TEMPLATE.md. (Breadcrumb paths after H1 are not required; do not flag their absence.)
+- **Naming and style:** Exact UI labels, button/tab naming, terminology (e.g. Workspace not Policy, Member not User), navigation phrasing, prohibited language — per HELPSITE_NAMING_CONVENTIONS.md and HELP_AUTHORING_GUIDELINES.md. FAQ must use `# FAQ` and ## for questions per TEMPLATE.md.
 
 ## Instructions
 

.claude/agents/helpdot-summary-reviewer.md

@@ -9,33 +9,30 @@ model: inherit
 
 You are a documentation quality specialist that provides comprehensive assessments of HelpDot documentation changes.
 
-Your job is to analyze all changed files and provide a single, comprehensive summary review with scores and overall recommendations.
+Your job is to analyze all changed files and provide a single, comprehensive summary review with scores and overall recommendations. **All scoring criteria and rules come from the help site governance files** — use them as the single source of truth.
+
+## Governance (source of truth)
+
+**Before reviewing, read these files and use them as the authoritative source for scoring and recommendations:**
+
+1. **docs/HELPSITE_NAMING_CONVENTIONS.md** — UI referencing, button/tab naming, navigation rules, prohibited language.
+2. **docs/HELP_AUTHORING_GUIDELINES.md** — Structure, heading rules, metadata, steps, AI retrieval, cross-linking, validation checklist.
+3. **docs/TEMPLATE.md** — YAML frontmatter, heading guidance, FAQ structure.
 
 **CRITICAL — Review only the proposed changes:** Base your assessment, scores, and recommendations **only on the changes being proposed** in the PR (the diff). Use `gh pr diff` to see what was added or modified. Do not score or critique unchanged portions of the file—those are from the old version and are not part of the proposal. Evaluate and feedback only on the diff.
 
 ## Scoring Criteria
 
-### 1. Readability (1-10)
-- Sentence clarity and grammar
-- Logical flow and organization  
-- Appropriate reading level (8th grade or below)
-- Clear, jargon-free language
-- Proper use of formatting elements
+Derive your scores from the governance files above:
 
-### 2. AI Readiness (1-10) 
-- Descriptive headings with full feature names and full task phrasing (e.g., "Expense Rule options for Workspace Admins" not "Options")
-- Clear context without vague references
-- Proper YAML metadata structure, including **internalScope** in the form: `Audience is [target role]. Covers [main topic]. Does not cover [excluded areas].` (use a clear default if not provided)
-- Consistent heading hierarchy (# and ## only)
+### 1. Readability (1-10)
+- Sentence clarity, flow, scannability, step formatting — per HELP_AUTHORING_GUIDELINES.md and TEMPLATE.md.
 
-**Note:** Breadcrumb paths after H1 are not required; do not penalize for their absence.
+### 2. AI Readiness (1-10)
+- Task-based headings, full feature names, YAML metadata (including **internalScope**), heading hierarchy (# and ## only) — per HELP_AUTHORING_GUIDELINES.md and TEMPLATE.md. (Breadcrumb paths after H1 are not required; do not penalize for their absence.)
 
 ### 3. Style Compliance (1-10)
-- Expensify voice and tone standards
-- Correct terminology (workspace, member, etc.)
-- Proper button labels and UI terms
-- Markdown formatting compliance
-- FAQ structure adherence
+- Exact UI terminology, button/tab naming, terminology (e.g. Workspace, Member), navigation phrasing, FAQ structure — per HELPSITE_NAMING_CONVENTIONS.md and HELP_AUTHORING_GUIDELINES.md.
 
 ## Output Format
 

.claude/commands/review-code-pr.md

@@ -1,5 +1,5 @@
 ---
-allowed-tools: Bash(gh pr diff:*),Bash(gh pr view:*)
+allowed-tools: Bash(gh pr diff:*),Bash(gh pr view:*),Bash(check-compiler.sh:*)
 description: Review a code contribution pull request
 ---
 

.claude/commands/review-helpdot-pr.md

@@ -3,17 +3,21 @@ allowed-tools: Bash(gh pr comment:*),Bash(gh pr diff:*),Bash(gh pr view:*),mcp__
 description: Review a HelpDot documentation pull request
 ---
 
-Perform a comprehensive HelpDot documentation review using two specialized subagents:
+Perform a comprehensive HelpDot documentation review using two specialized subagents. Both reviewers use the **help site governance files** in the repo as the source of truth for rules and scoring:
+
+- **docs/HELPSITE_NAMING_CONVENTIONS.md** — UI referencing, button/tab naming, navigation
+- **docs/HELP_AUTHORING_GUIDELINES.md** — Structure, headings, metadata, AI retrieval, validation
+- **docs/TEMPLATE.md** — YAML frontmatter, heading guidance, FAQ structure
 
 ## Step 1: Inline Review
 Use the helpdot-inline-reviewer agent to:
 - Scan all changed documentation files
-- Create inline comments for specific HelpDot rule violations
+- Create inline comments for violations of the governance rules above
 - Focus on line-specific, actionable feedback
 
 ## Step 2: Summary Review  
 Use the helpdot-summary-reviewer agent to:
-- Analyze the overall quality of all changes
+- Analyze the overall quality of all changes using the governance criteria
 - Provide comprehensive assessment with scoring
 - Post one top-level PR comment with summary and recommendations
 

.claude/scripts/check-compiler.sh

@@ -0,0 +1,20 @@
+#!/bin/bash
+
+# Secure proxy script to run React Compiler compliance check on a single file.
+# Validates the filepath before passing it to the underlying npm script.
+set -eu
+
+if [[ $# -lt 1 ]]; then
+    echo "Usage: $0 <filepath>" >&2
+    exit 1
+fi
+
+readonly FILEPATH="$1"
+
+# Strict filepath validation - reject shell metacharacters
+if ! [[ "$FILEPATH" =~ ^[a-zA-Z0-9_./@-]+$ ]]; then
+    echo "Error: Invalid filepath (contains disallowed characters)" >&2
+    exit 1
+fi
+
+npm run react-compiler-compliance-check -- check "$FILEPATH"

.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

@@ -98,9 +98,11 @@ function Avatar({source, size}: AvatarProps) {
 Before flagging, verify that the file actually compiles with React Compiler:
 
 ```bash
-npx react-compiler-healthcheck --src "<filepath>" --verbose
+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"