<!-- This file is managed by Lisa and IS replaced on each `lisa` run. -->
<!-- Do not edit directly — durable changes belong upstream in Lisa. -->

# GitHub Actions Configuration

This directory contains the CI/CD workflows and automation for the project. This document explains how to configure and use the GitHub Actions workflows.

## Table of Contents

- [Overview](#overview)
- [Quick Start](#quick-start)
- [Workflows](#workflows)
- [Secrets Configuration](#secrets-configuration)
- [Repository Variables](#repository-variables)
- [External Service Setup](#external-service-setup)
- [Customization](#customization)

## Overview

The CI/CD system provides:

- **Quality Gates**: Linting, type checking, formatting, and testing
- **Security Scanning**: Vulnerability detection, secret scanning, license compliance
- **Release Management**: Automated versioning, changelogs, and GitHub releases
- **Mobile Builds**: Expo EAS builds for iOS and Android
- **OTA Updates**: Expo EAS Update deployments
- **Performance Testing**: Lighthouse CI for web, k6 load testing
- **AI Integration**: Claude Code for automated code review and assistance

## Quick Start

### Minimum Configuration

To get started with basic CI, add these secrets to your repository:

```bash
# No secrets required for basic quality checks (lint, typecheck, build, format)
```

### Recommended Configuration

For full functionality, configure the following secrets:

| Secret | Purpose | Required For |
|--------|---------|--------------|
| `EXPO_TOKEN` | EAS builds and updates | Mobile deployment |
| `SENTRY_AUTH_TOKEN` | Error tracking | Release monitoring |
| `SENTRY_ORG` | Sentry organization slug | Release monitoring |
| `SENTRY_PROJECT` | Sentry project slug | Release monitoring |
| `SONAR_TOKEN` | Code quality analysis | Security scanning |
| `SNYK_TOKEN` | Vulnerability scanning | Security scanning |

## Workflows

### CI Quality Checks (`ci.yml`)

**Triggers**: Pull requests, manual dispatch

Runs on every pull request to validate code quality:

- Lint (ESLint)
- Type checking (TypeScript)
- Formatting (Prettier)
- Build verification
- Security scans (when configured)
- Lighthouse CI (web performance)

**Configuration**:
```yaml
# In ci.yml, modify these inputs:
node_version: '22.21.1'
package_manager: 'bun'
skip_jobs: 'test,test:integration,test:e2e'  # Comma-separated list
```

### Release and Deploy (`deploy.yml`)

**Triggers**: Push to `main`, `staging`, or `dev` branches; manual dispatch

Handles the complete release lifecycle:

1. Creates a new release with version bump
2. Generates changelog from commits
3. Triggers EAS build (if `app.config.ts` changed)
4. Publishes OTA update via EAS Update
5. Creates Sentry release (if configured)

**Environment Mapping**:
| Branch | Environment | EAS Channel |
|--------|-------------|-------------|
| `dev` | development | dev |
| `staging` | staging | staging |
| `main` | production | production |

### EAS Build (`build.yml`)

**Triggers**: Changes to `app.config.ts`, manual dispatch, workflow call

Builds native app binaries via Expo Application Services:

- **dev**: Development preview builds
- **staging**: Staging builds with auto-submit to TestFlight/Play Console
- **production**: Production builds with auto-submit

### Quality Checks (`quality.yml`)

**Type**: Reusable workflow

Comprehensive quality validation with 20+ configurable jobs. Called by other workflows.

**Skippable Jobs**:
```
lint, typecheck, test, test:unit, test:integration, test:e2e,
maestro_e2e, playwright_e2e, format, build, npm_security_scan,
sonarcloud, snyk, secret_scanning, license_compliance
```

### Release (`release.yml`)

**Type**: Reusable workflow

Enterprise-grade release management:

- Version strategies: `standard-version`, `semantic`, `calendar`, `custom`
- Changelog generation
- GPG signing (optional)
- SBOM generation
- Sentry release creation
- Jira release creation
- Compliance validation (SOC2, ISO27001, HIPAA, PCI-DSS)
- Optional human-approval gate (`require_approval` + `approval_environment`)

**Human-approval gate**: pass `require_approval: true` and the run pauses at the
`🚦 Release Approval` job until a required reviewer approves it in the Actions UI.
The pause is enforced by the GitHub Environment named in `approval_environment`
(falls back to `environment`, i.e. the branch name):

```yaml
# The ref is maintained for you. Lisa rewrites every `uses:` pointing at one of
# its reusable workflows to the commit your installed version's tag names, on
# every apply, with the version alongside it as a comment. Do not hand-edit it:
# a hand-pinned SHA rots, and `@main` would run whatever landed on Lisa's
# default branch since your run started rather than the Lisa you installed.
uses: CodySwannGT/lisa/.github/workflows/release.yml@<40-character commit sha> # v<x.y.z>
with:
  require_approval: true
  approval_environment: 'production'
```

Because everything downstream (versioning, GitHub Release, and any deploy job
that `needs: release`) chains off this gate, approval blocks the whole pipeline.
The Lisa stack `deploy.yml` templates wire both inputs automatically from the
optional `github.environments` block in `.lisa.config.json`, mapping the branch
to its friendly environment name (`main` → `production` via `deploy.branches`).
The environment itself — required reviewers and a deployment branch policy —
is provisioned by `/lisa:setup:github-repo`. Provision before enabling the gate:
GitHub auto-creates unprovisioned environments **without** protection rules, so
an unprovisioned gate blocks nothing. Not yet wired for rails
(`release-rails.yml` doesn't thread approval inputs) or harper-fabric (no
release.yml call).

**Blackout Periods** (configurable):
- Production: No weekends, no late nights (10 PM - 6 AM)
- Holiday blackouts: Dec 24 - Jan 2, Jul 3-5, Nov 27-29

### Lighthouse CI (`lighthouse.yml`)

**Type**: Reusable workflow

Web performance budget validation using Google Lighthouse.

### Claude Code (`claude.yml`)

**Triggers**: Comments/reviews mentioning `@claude`

AI-powered code assistance that can:
- Review code changes
- Suggest improvements
- Run tests and builds
- Answer questions about the codebase
- Edit files and create commits (write permissions enabled)

### Claude CI Auto-Fix (`claude-ci-auto-fix.yml`)

**Triggers**: CI Quality Checks workflow failure (non-environment branches)

Fixer of last resort for red CI on unattended branches: Claude analyzes error logs and prepares a fix as a pull request into the failing branch.

- Stands down when the branch has an active owner: a fresh `lisa:babysitter-on-duty` lease label on the branch's open PR (stamped by drive-pr-to-merge sessions), or any push during a quiet-period wait (default 20 minutes)
- Fetches failed job names and error logs from the CI run
- Runs Claude with full context to diagnose and fix the root cause
- Never pushes to the failing branch — commits land on a `claude-auto-fix-<branch>` side branch and a PR is opened into the failing branch
- Falls back to a non-frozen dependency install when the lockfile itself is broken, so Claude can repair and commit the lockfile
- When no fix can be produced, files a deduplicated ticket in the tracker declared in `.lisa.config.json` (`tracker`: jira | github | linear) with a title that says whether Claude ran at all
- Skips environment branches (`main`, `staging`, `dev`) and auto-fix branches (prevents infinite loops); failing checks on an auto-fix PR escalate to a ticket instead of re-entering
- Requires the caller to map `JIRA_API_TOKEN` / `LINEAR_API_KEY` (and `PAT`) explicitly in its `secrets:` block so tracker credentials reach the issue dispatcher — least-privilege by design; `secrets: inherit` also works mechanically but hands the chain every repo secret and trips SonarCloud security gates

### Claude Code Review Response (`claude-code-review-response.yml`)

**Triggers**: CodeRabbit review submitted on a PR

**Opt-in**: Set repository variable `ENABLE_CLAUDE_CODE_REVIEW_RESPONSE` to `true`

Automatically triages CodeRabbit review comments and either fixes valid findings or replies to dismiss invalid ones.

- Triggers when CodeRabbit submits a review (not per inline comment — once per review summary)
- Skips PRs authored by `coderabbitai[bot]` or `dependabot[bot]` to prevent bot-to-bot loops (PRs authored by `claude[bot]` or other bots are allowed)
- For each review comment, Claude determines if the finding is valid or a misunderstanding
- Valid findings: fixes the code and commits with conventional messages
- Invalid findings: replies to the comment explaining why the suggestion does not apply
- Pushes fixes directly to the existing PR branch (no new PR created)

### Claude Nightly Test Improvement (`claude-nightly-test-improvement.yml`)

**Triggers**: Cron at 3 AM UTC weekdays, manual dispatch

**Opt-in**: Set repository variable `ENABLE_CLAUDE_NIGHTLY` to `true`

Analyzes tests and creates a PR with improvements. Supports two modes:

- **Nightly mode** (default for cron and manual dispatch): Scopes analysis to files changed in the last 24 hours on the default branch. Maps changed source files to their corresponding test files and improves only those tests. Skips the run entirely if no source files changed in the last 24 hours.
- **General mode** (manual dispatch only): Full repository analysis. Scans all test files for weak, brittle, or poorly-written tests and improves 3-5 files with the most impactful changes.

Both modes look for: missing edge cases, weak assertions, missing error path coverage, and implementation-coupled tests. Verifies all tests pass before creating a PR. Prevents duplicate PRs (skips if one is already open).

To trigger general mode manually: **Actions** > **Claude Nightly Test Improvement** > **Run workflow** > set **Analysis mode** to `general`.

### Claude Nightly Test Coverage (`claude-nightly-test-coverage.yml`)

**Triggers**: Cron at 4 AM UTC weekdays, manual dispatch

**Opt-in**: Set repository variable `ENABLE_CLAUDE_NIGHTLY` to `true`

Incrementally increases test coverage thresholds toward a 90% target:

1. Reads `jest.thresholds.json` to get current coverage thresholds
2. For each metric (`statements`, `branches`, `functions`, `lines`) below 90%, proposes a 5% increase (capped at 90%)
3. Writes new tests to meet the proposed thresholds
4. Updates `jest.thresholds.json` with the new values
5. Verifies the updated thresholds pass with `bun run test:cov`
6. Creates a PR summarizing which metrics were bumped (e.g., "branches 65% -> 70%, functions 60% -> 65%")

Skips the run if all metrics are already at or above 90%. Prevents duplicate PRs (skips if one is already open).

`jest.thresholds.json` format:
```json
{
  "global": {
    "statements": 75,
    "branches": 65,
    "functions": 60,
    "lines": 75
  }
}
```

### Claude Nightly Code Complexity (`claude-nightly-code-complexity.yml`)

**Triggers**: Cron at 5 AM UTC weekdays, manual dispatch

**Opt-in**: Set repository variable `ENABLE_CLAUDE_NIGHTLY` to `true`

Incrementally lowers ESLint code complexity thresholds toward target minimums:

1. Reads `eslint.thresholds.json` to get current complexity thresholds
2. For `cognitiveComplexity` above 15, proposes a decrease of 2 (floored at 15)
3. For `maxLinesPerFunction` above 30, proposes a decrease of 5 (floored at 30)
4. Refactors functions to meet the stricter thresholds
5. Updates `eslint.thresholds.json` with the new values
6. Verifies lint and tests pass
7. Creates a PR summarizing which metrics were reduced

Does not modify the `maxLines` threshold. Skips if all metrics are at/below targets. Prevents duplicate PRs.

### Claude Nightly Jira Triage (`claude-nightly-jira-triage.yml`)

**Triggers**: Cron every 2 hours (all days), manual dispatch

**Auto-enables**: When Claude and Jira credentials are configured (`CLAUDE_CODE_OAUTH_TOKEN`, `JIRA_API_TOKEN` secrets and `JIRA_BASE_URL`, `JIRA_USER_EMAIL`, `JIRA_PROJECT_KEY` repository variables). No feature flag needed.

Automatically triages untriaged Jira tickets by examining them and posting actionable comments. Supports multi-repo setups where multiple repositories share a single Jira project:

1. Fetches untriaged tickets via JQL using repo-scoped labels (`claude-triaged-<repo-name>`, e.g., `claude-triaged-frontend-v2`). Each repo filters by its own label so every repo triages independently
2. **Relevance Gating**: Searches the local codebase for code related to the ticket. If no relevant code is found, adds the repo-scoped label and skips -- no noise posted to the ticket
3. **Cross-repo Awareness**: Reads existing comments on the ticket before posting. If another repo already posted triage findings, only adds supplementary findings from this repo's perspective. All comments are prefixed with the repo name (e.g., `*[frontend-v2] Ambiguity detected*`)
4. **Ambiguity Detection**: Flags vague language, untestable criteria, undefined terms, and missing scope. Posts a comment per ambiguity with a suggested clarifying question
5. **Edge Case Analysis**: Searches the codebase for related files, checks git history, and identifies boundary conditions, error handling gaps, and integration risks. Posts a consolidated comment referencing only files in this repo
6. **Verification Methodology**: For each acceptance criterion, specifies a concrete verification method scoped to what this repo can test (e.g., frontend suggests Playwright tests, backend suggests API curl commands). Posts a structured table comment
7. Labels the ticket with the repo-scoped label (`claude-triaged-<repo-name>`) so it is not reprocessed by this repo

**Manual dispatch inputs**:
- `ticket_key`: Triage a specific ticket by key (e.g., `PROJ-123`)
- `ticket_count`: Number of tickets to process in batch mode (default: 5)

This workflow is read-only — it does not modify code or create PRs. It only reads the codebase and posts Jira comments.

**How to activate**:

1. Add the secrets in **Settings** > **Secrets and variables** > **Actions** > **Secrets**:

   | Secret | Description | How to get |
   |--------|-------------|------------|
   | `CLAUDE_CODE_OAUTH_TOKEN` | OAuth token for Claude Code | See `CLAUDE_CODE_OAUTH_TOKEN` in the Core Secrets section below |
   | `JIRA_API_TOKEN` | API token from Atlassian | [Create API token](https://id.atlassian.com/manage-profile/security/api-tokens) |

2. Add repository variables in **Settings** > **Secrets and variables** > **Actions** > **Variables**:

   | Variable | Description | Example |
   |----------|-------------|---------|
   | `JIRA_BASE_URL` | Jira instance base URL | `https://company.atlassian.net` |
   | `JIRA_USER_EMAIL` | Email associated with the API token | `user@company.com` |
   | `JIRA_PROJECT_KEY` | Jira project key for ticket queries | `PROJ` |

3. The workflow auto-enables once all three variables and both secrets are set. No feature flag needed.

### Load Testing (`load-test.yml`)

**Type**: Reusable workflow

Performance load testing using k6:

- Scenarios: `smoke`, `load`, `stress`, `spike`, `soak`
- Configurable thresholds
- Result artifact uploads

## Secrets Configuration

### How to Add Secrets

1. Go to **Settings** > **Secrets and variables** > **Actions**
2. Click **New repository secret**
3. Enter the secret name and value

Or use the GitHub CLI:
```bash
gh secret set SECRET_NAME --body "secret-value"
```

For bulk setup, copy `.github/workflows/.env.example` and run:
```bash
gh secret set --env-file .env
```

### Core Secrets

#### EXPO_TOKEN
**Purpose**: Authenticate with Expo/EAS for builds and updates

**How to get it**:
1. Go to [expo.dev/settings/access-tokens](https://expo.dev/settings/access-tokens)
2. Click **Create Token**
3. Name it (e.g., "GitHub Actions")
4. Copy the token (starts with `expo_`)

**Required for**: EAS Build, EAS Update

---

#### SENTRY_AUTH_TOKEN
**Purpose**: Create releases and upload sourcemaps to Sentry

**How to get it**:
1. Go to [sentry.io/settings/account/api/auth-tokens/](https://sentry.io/settings/account/api/auth-tokens/)
2. Click **Create New Token**
3. Select scopes: `project:releases`, `project:write`
4. Copy the token

**Required for**: Error tracking, release monitoring

---

#### SONAR_TOKEN
**Purpose**: Authenticate with SonarCloud for code quality analysis

**How to get it**:
1. Go to [sonarcloud.io/account/security](https://sonarcloud.io/account/security)
2. Click **Generate Tokens**
3. Name your token and generate
4. Copy the token

**Required for**: Static code analysis (SAST)

**Additional Setup**:
Create `sonar-project.properties` in your repo root:
```properties
sonar.projectKey=your-org_your-project
sonar.organization=your-org
```

---

#### SNYK_TOKEN
**Purpose**: Scan dependencies for known vulnerabilities

**How to get it**:
1. Go to [app.snyk.io/account](https://app.snyk.io/account)
2. Find **Auth Token** section
3. Click **click to show** and copy

**Required for**: Dependency vulnerability scanning

---

#### GITGUARDIAN_API_KEY
**Purpose**: Detect hardcoded secrets in code

**How to get it**:
1. Go to [dashboard.gitguardian.com/api/personal-access-tokens](https://dashboard.gitguardian.com/api/personal-access-tokens)
2. Click **Create new token**
3. Select scope: `scan`
4. Copy the token

**Required for**: Secret detection

---

#### FOSSA_API_KEY
**Purpose**: License compliance checking for dependencies

**How to get it**:
1. Go to [app.fossa.com/account/settings/integrations/api_tokens](https://app.fossa.com/account/settings/integrations/api_tokens)
2. Click **Add API Token**
3. Copy the token

**Required for**: License compliance

---

#### CLAUDE_CODE_OAUTH_TOKEN
**Purpose**: Enable Claude AI code assistance in issues and PRs

**How to get it**:
1. Visit [claude.ai/code](https://claude.ai/code) or your Anthropic Console
2. Generate an OAuth token for GitHub integration
3. Copy the token

**Required for**: `@claude` mentions in issues/PRs

---

#### K6_CLOUD_TOKEN
**Purpose**: Run load tests on k6 Cloud infrastructure

**How to get it**:
1. Go to [app.k6.io/account/api-token](https://app.k6.io/account/api-token)
2. Copy your API token

**Required for**: Cloud-based load testing

---

#### DEPLOY_KEY
**Purpose**: Push version bumps and releases to protected branches

GitHub Actions workflows cannot push directly to protected branches using the default `GITHUB_TOKEN`. A deploy key (SSH key) with write access bypasses branch protection rules for automated releases.

**How to set it up**:

1. **Generate an SSH key pair locally**:
   ```bash
   # Generate a new SSH key (no passphrase for CI use)
   ssh-keygen -t ed25519 -C "github-actions-deploy-key" -f deploy_key -N ""

   # This creates two files:
   # - deploy_key (private key - goes to GitHub Secrets)
   # - deploy_key.pub (public key - goes to Deploy Keys)
   ```

2. **Add the public key to GitHub Deploy Keys**:
   - Go to your repository **Settings** > **Deploy keys**
   - Click **Add deploy key**
   - Title: `GitHub Actions Deploy Key`
   - Key: Paste contents of `deploy_key.pub`
   - **Check "Allow write access"** (required for pushing)
   - Click **Add key**

3. **Add the private key as a repository secret**:
   ```bash
   # Using GitHub CLI
   gh secret set DEPLOY_KEY < deploy_key

   # Or manually:
   # Go to Settings > Secrets and variables > Actions
   # Click "New repository secret"
   # Name: DEPLOY_KEY
   # Value: Paste entire contents of deploy_key file (including BEGIN/END lines)
   ```

4. **Clean up local keys**:
   ```bash
   # Delete the local key files after setup
   rm deploy_key deploy_key.pub
   ```

**Required for**: Automated releases pushing to protected branches (main, staging, dev)

**Note**: If your branch protection rules require signed commits, you'll also need to set up GPG signing (see Release Signing Secrets below).

---

### Release Signing Secrets (Optional)

For GPG-signed releases:

| Secret | Description |
|--------|-------------|
| `RELEASE_SIGNING_KEY` | Base64-encoded GPG private key |
| `SIGNING_KEY_ID` | GPG key ID |
| `SIGNING_KEY_PASSPHRASE` | GPG key passphrase |

To generate:
```bash
# Generate GPG key
gpg --full-generate-key

# Export and base64 encode
gpg --export-secret-keys YOUR_KEY_ID | base64 > signing-key.txt
```

---

### Jira Integration Secrets (Optional)

| Secret | Description |
|--------|-------------|
| `JIRA_API_TOKEN` | API token from Atlassian |
| `JIRA_AUTOMATION_WEBHOOK` | Webhook URL for Jira automation |

**How to get JIRA_API_TOKEN**:
1. Go to [id.atlassian.com/manage-profile/security/api-tokens](https://id.atlassian.com/manage-profile/security/api-tokens)
2. Click **Create API token**
3. Copy the token

## Repository Variables

Variables are non-sensitive configuration values. Set them in **Settings** > **Secrets and variables** > **Actions** > **Variables**.

| Variable | Description | Example |
|----------|-------------|---------|
| `ENABLE_CLAUDE_NIGHTLY` | Enable nightly Claude workflows | `true` |
| `ENABLE_CLAUDE_CODE_REVIEW_RESPONSE` | Enable Claude response to CodeRabbit reviews | `true` |
| `JIRA_BASE_URL` | Jira instance base URL (enables Jira triage workflow) | `https://company.atlassian.net` |
| `JIRA_USER_EMAIL` | Email associated with the Jira API token | `user@company.com` |
| `JIRA_PROJECT_KEY` | Jira project key for ticket queries | `PROJ` |

## External Service Setup

### SonarCloud

1. Sign in at [sonarcloud.io](https://sonarcloud.io)
2. Import your GitHub repository
3. Create `sonar-project.properties`:
   ```properties
   sonar.projectKey=org_project
   sonar.organization=org
   sonar.sources=src
   sonar.exclusions=**/node_modules/**,**/*.test.*
   ```

### Expo/EAS

1. Install EAS CLI: `npm install -g eas-cli`
2. Login: `eas login`
3. Configure project: `eas init`
4. Create `eas.json` with build profiles

### Sentry

1. Create a project at [sentry.io](https://sentry.io)
2. Note your organization and project slugs
3. Configure Sentry in your app (see Sentry React Native docs)

### Maestro Cloud (Mobile E2E)

1. Sign up at [cloud.mobile.dev](https://cloud.mobile.dev)
2. Create a project and note the project ID
3. Generate an API key
4. Add `MAESTRO_API_KEY` secret
5. Pass `maestro_project_id` input to quality workflow

## Customization

### Skipping Jobs

Add to your workflow call:
```yaml
uses: ./.github/workflows/quality.yml
with:
  skip_jobs: 'test:e2e,maestro_e2e,playwright_e2e'
```

### Compliance Frameworks

Enable compliance validation:
```yaml
uses: ./.github/workflows/quality.yml
with:
  compliance_framework: 'soc2'  # or iso27001, hipaa, pci-dss
```

**Note**: quality.yml's `approval_gate` job only records an audit artifact; it
does not pause the run. Do not pass `require_approval` or `approval_environment`
to this quality.yml example. For an enforced human gate, pass those inputs to
release.yml and create the environment in **Settings** > **Environments** first
(or declare it under `github.environments` in `.lisa.config.json` and run
`/lisa:setup:github-repo`).

### Custom Node Version

```yaml
uses: ./.github/workflows/quality.yml
with:
  node_version: '22.21.1'
  package_manager: 'bun'  # or npm, yarn
```

### Load Test Scenarios

```yaml
uses: ./.github/workflows/load-test.yml
with:
  test_scenario: 'stress'  # smoke, load, stress, spike, soak
  base_url: 'https://api.example.com'
  virtual_users: 100
  test_duration: '10m'
```

## Directory Structure

```
.github/
├── workflows/
│   ├── ci.yml                              # PR quality checks
│   ├── deploy.yml                          # Release and deploy
│   ├── build.yml                           # EAS builds
│   ├── quality.yml                         # Reusable quality checks
│   ├── release.yml                         # Reusable release workflow
│   ├── lighthouse.yml                      # Web performance
│   ├── load-test.yml                       # k6 load testing
│   ├── claude.yml                              # AI assistance
│   ├── claude-ci-auto-fix.yml                  # Auto-fix CI failures
│   ├── claude-code-review-response.yml         # Respond to CodeRabbit reviews
│   ├── claude-nightly-test-improvement.yml     # Nightly test quality
│   ├── claude-nightly-test-coverage.yml        # Nightly test coverage
│   ├── claude-nightly-code-complexity.yml      # Nightly code complexity
│   └── .env.example                            # Secrets template
└── k6/
    ├── scripts/                            # Test scripts
    ├── scenarios/                          # Test configurations
    ├── thresholds/                         # Performance thresholds
    └── README.md                           # K6 documentation
```

## Troubleshooting

### "Secret not found" errors
Ensure the secret is added to the repository, not just your local environment.

### SonarCloud scan fails
Verify `sonar-project.properties` exists and `SONAR_TOKEN` is set.

### EAS builds fail
Check `EXPO_TOKEN` is valid and has necessary permissions.

### Deployment fails on protected branches
Add `DEPLOY_KEY` (SSH deploy key) for pushing version bumps.

### Claude doesn't respond
Ensure `CLAUDE_CODE_OAUTH_TOKEN` is set and the comment includes `@claude`.

## Related Documentation

- [K6 Load Testing Guide](.github/k6/README.md)
- [K6 Scenario Selection Guide](.github/k6/SCENARIO_SELECTION_GUIDE.md)
- [Expo EAS Documentation](https://docs.expo.dev/eas/)
- [SonarCloud Documentation](https://docs.sonarcloud.io/)
- [Sentry React Native](https://docs.sentry.io/platforms/react-native/)
