@terreno/mcp 57.4.0 → 57.6.1

package/dist/docs/versioned/next/how-to/README.md

@@ -30,6 +30,8 @@ Problem-oriented, practical steps. Use these when you know what you want to do.
 - [Password reset and email verification](password-reset.md) — JWT routes, comms templates, Better Auth hooks
 - [Add WebSocket integration](websocket-integration.md) — Set up real-time Socket.io connections
 - [Expose Model Context Protocol tools](expose-mcp-tools.md) — Turn `modelRouter` models into MCP tools an LLM can call
+- [Set up Terreno MCP](set-up-terreno-mcp.md) — Configure hosted docs/codegen and local runtime tools
+- [Debug with MCP](debug-with-mcp.md) — Diagnose backend, browser, Metro, app, and client-state failures
 - [Connect an MCP client with a service token](connect-mcp-service-token.md) — Mint a personal `mcp_` key for Perplexity and other remote clients
 - [Install agent skills](install-agent-skills.md) — `npx skills`, the Cursor plugin, the Codex plugin, or the Claude Code plugin
 - [GitHub issue lifecycle](github-issue-lifecycle.md) — Create pick-ready issues, Pick ⇄ Roast, or unattended `status:ready-for-dev` pickup
@@ -40,6 +42,7 @@ Problem-oriented, practical steps. Use these when you know what you want to do.
 - [Compose charts in a dashboard grid](charts-and-dashboards.md) — `LineChart` / `BarChart` / `AreaChart` / `DonutChart` inside `Card`s in `DashboardGrid`
 - [Compare rendered chart snapshots](compare-chart-rendered-snapshots.md) — PNG goldens for the chart visual gallery, not JSON snapshots
 - [Migrate from @terreno/rtk to @terreno/syncdb](migrate-rtk-to-syncdb.md) — Move data sync to the local-first layer
+- [Generate a REST CLI from OpenAPI](generate-a-rest-cli.md) — Scaffold `terreno generate rest-cli` for an app API
 - [In-app notifications](in-app-notifications.md) — Register `NotificationsApp`, syncdb inbox, and UI bell
 - [Add organizations](add-organizations.md) — Opt into Membership-backed tenancy, RBAC, admin, and seeded examples
 - [Add a GPT chat mascot](add-gpt-chat-mascot.md) — Optional consumer-owned character on empty `GPTChat`

package/dist/docs/versioned/next/how-to/background-jobs.md

@@ -293,4 +293,4 @@ the insert when possible (`JobDispatchError`).
 - [Jobs reference](../reference/jobs.md)
 - [Environment variables — jobs](../reference/environment-variables.md#background-jobs)
 - [Import pre-built admins](admin-import-prebuilt.md)
-- Implementation plan: [job-queues.md](https://github.com/FlourishHealth/terreno/blob/master/docs/implementationPlans/job-queues.md)
+- Implementation plan: [job-queues.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/implementationPlans/job-queues.md)

package/dist/docs/versioned/next/how-to/build-for-web.md

@@ -66,4 +66,4 @@ Upload `dist/` to your host. **Client-side routing** requires the host to serve
 - [Deploy to GCP](deploy-to-gcp.md) — GCS + Cloud CDN (static web) + Cloud Run (backend)
 - Deployment baseline — [seven requirements](../explanation/deployment-baseline.md)
 
-For server-rendered web (future), see [Web SSR and admin SPA](https://github.com/FlourishHealth/terreno/blob/master/docs/implementationPlans/web-ssr-and-admin-spa.md).
+For server-rendered web (future), see [Web SSR and admin SPA](https://github.com/TerrenoLabs/terreno/blob/master/docs/implementationPlans/web-ssr-and-admin-spa.md).

package/dist/docs/versioned/next/how-to/call-external-apis.md

@@ -94,7 +94,7 @@ Note the hook's output classification also feeds the client's retry decision —
 
 - **Your own backend's routes** — use the generated `@terreno/rtk` SDK (frontend) or call the function directly (backend).
 - **SDK-managed transport** (Twilio, googleapis) — don't fight the SDK's HTTP layer; adopt only `normalizeApiError`/`withApiErrorHandling` for consistent failure handling.
-- **Webhook notifiers** — `sendSlackMessage`/`sendGoogleChatMessage`/`sendZoomMessage` already exist; see [Webhooks & Notifications](../reference/api.md#webhooks--notifications).
+- **Webhook notifiers** — `sendToSlack`/`sendToGoogleChat`/`sendToZoom` already exist; see [Webhooks & Notifications](../reference/api.md#webhooks--notifications). Slack @-mentions require a stored Slack member ID (`mentionUserIds` or `formatSlackUserMention`); names and emails in the text do not notify anyone.
 
 ## Related
 

package/dist/docs/versioned/next/how-to/circleci.md

@@ -9,7 +9,7 @@ CircleCI Netlify and GCP production/preview jobs, but those jobs **skip green**
 until `terreno-netlify` and `terreno-gcp` are filled. GitHub Actions still
 owns live Netlify/GCP deploys in this window. Do not leave both applying
 terraform once CircleCI GCP deploys succeed — set the GHA deploy workflows
-back to `on: []` in the same change. GitHub-native security, Cursor GitHub App
+back to `push.branches-ignore: ["**"]` in the same change. GitHub-native security, Cursor GitHub App
 checks (Approval / Security / Bugbot), and repository automation remain
 enabled. EAS PR updates and the fingerprint gate are temporarily disabled;
 manual EAS development dispatch remains available in CircleCI. Preview
@@ -18,7 +18,7 @@ CircleCI `run-preview-cleanup` parameter.
 
 ## Project setup (maintainers)
 
-1. Link `FlourishHealth/terreno` in CircleCI (GitHub App).
+1. Link `TerrenoLabs/terreno` in CircleCI (GitHub App).
 2. Default branch: `master`.
 3. Enable **dynamic config** / setup workflows for the project (required for
    `.circleci/config.yml` `setup: true`).
@@ -36,7 +36,7 @@ CircleCI `run-preview-cleanup` parameter.
 GitHub App org/project slug (API and CLI):
 `circleci/6UHiK7pThPXbhnNi3umQNe/W3HZeMJujyMB2sYiUXaQbs`.
 
-Do not query `gh/FlourishHealth/terreno` — that slug returns `404 Project not found`.
+Do not query `gh/TerrenoLabs/terreno` — that slug returns `404 Project not found`.
 Cloud agents use `CIRCLECI_TOKEN` (accepted alias of CircleCI's `CIRCLE_TOKEN`). Send
 it as the `Circle-Token` header. Confirm with `GET https://circleci.com/api/v2/me`, then
 list pipelines on the slug above.
@@ -48,6 +48,25 @@ list pipelines on the slug above.
 | `.circleci/config.yml` | Setup workflow + `path-filtering` (this is the live config) |
 | `.circleci/continue-config.yml` | Real jobs/workflows gated by those params |
 
+## Bun install is uncached
+
+`install_bun_and_deps` runs `bun install --frozen-lockfile` with
+`node/install-packages` `with-cache: false`. Do not restore `~/.bun/install/cache`.
+Measured on CircleCI (pipeline 1968 miss, 1969 exact lockfile hit, branch
+`chore/update-dependencies`):
+
+| Path | Restore | `bun install` | Save | Restore + install |
+| --- | --- | --- | --- | --- |
+| Cold (cache miss) | ~0.3s | ~11–21s (2488 packages) | ~17s on one job; others skip | **~12–21s** |
+| Warm (exact lockfile hit) | ~15–17s | ~6–7s | skip | **~21–24s** |
+| Stale fallback hit | ~22–73s | ~8–9s | skip | **~30–81s** |
+
+Cache restore costs more than it saves. First jobs on a branch miss because
+`include-branch-in-cache-key` was true. Parallel jobs cannot reuse a cache
+saved later in the same pipeline. GitHub Actions twins use
+`.github/actions/setup-bun-workspace` the same way (Bun pin + install, no
+package cache). Keep Playwright, Docusaurus, and fingerprint caches.
+
 Fork-only `dco` and PR `architectural-pr-review` always start on continuation
 (review skips before checkout when the agentic/GitHub contexts are empty).
 `rulesync-check` runs only when generated-rule sources change (`run-rulesync`).
@@ -163,11 +182,11 @@ applies to `gcp-cd-*` when `terreno-gcp` lacks WIF or SA emails, so GitHub
 `github.event.pull_request.head.repo.full_name == github.repository`.
 Terraform preview always describes the Infra Manager preview (state,
 `errorCode`, `errorLogs`) before delete, including when `previews create`
-fails. Fork PRs still present `repository: FlourishHealth/terreno` on the
+fails. Fork PRs still present `repository: TerrenoLabs/terreno` on the
 OIDC token, so
 WIF would accept them if those jobs ran. Netlify GHA jobs fail closed on
 forks (secrets withheld). After filling a context, confirm a CircleCI deploy
-URL, then set the matching GHA workflows to `on: []`. Turn off Netlify's
+URL, then set the matching GHA workflows to `push.branches-ignore: ["**"]`. Turn off Netlify's
 GitHub auto-build so only one system publishes.
 
 ## Contexts (create empty shells, then fill)
@@ -224,7 +243,7 @@ are included by that script. Published packages without a dedicated workflow
 the same commands through the parameterized `packages-ci` job, gated by
 `run-admin-backend`, `run-admin-frontend`, `run-api-health`,
 `run-feature-flags`, and `run-test-package`. The retained
-`.github/workflows/packages-ci.yml` matrix twin stays `on: []`.
+`.github/workflows/packages-ci.yml` matrix twin stays `push.branches-ignore: ["**"]`.
 
 | GHA job `name:` / workflow | CircleCI job |
 |----------------------------|--------------|
@@ -382,11 +401,11 @@ circleci config validate .circleci/continue-config.yml
 
 ## Disabled GitHub workflows
 
-Package CI, e2e, and npm tag workflows stay `on: []`. Netlify/GCP deploy
+Package CI, e2e, and npm tag workflows stay `push.branches-ignore: ["**"]`. Netlify/GCP deploy
 workflows are **re-enabled** until CircleCI contexts have the same secrets.
 After a successful CircleCI production or preview deploy, set
 `docs-deploy.yml`, `demo-deploy.yml`, `frontend-example-deploy.yml`, `cd.yml`,
-and `preview-cleanup.yml` back to `on: []` in the same PR. Never enable both
+and `preview-cleanup.yml` back to `push.branches-ignore: ["**"]` in the same PR. Never enable both
 npm tag publishers. Never leave both GCP terraform applies enabled.
 
 ## Cursor GitHub App checks

package/dist/docs/versioned/next/how-to/create-a-terreno-app.md

@@ -37,10 +37,10 @@ Optional flags:
 | `appName` (positional) | yes | — kebab-case directory and package name (`^[a-z][a-z0-9-]*$`) |
 | `--display-name` | unless `--yes` | derived from `appName` when `--yes` |
 | `--description` | no | empty |
-| `--mcp-server-url` | no | `https://mcp.terreno.flourish.health` |
+| `--mcp-server-url` | no | `https://mcp.terreno.app` |
 | `--yes` | no | off |
 
-The CLI creates `<cwd>/<appName>/`. Package source: [`create-terreno-app/`](https://github.com/FlourishHealth/terreno/tree/master/create-terreno-app) in the Terreno monorepo.
+The CLI creates `<cwd>/<appName>/`. Package source: [`create-terreno-app/`](https://github.com/TerrenoLabs/terreno/tree/master/create-terreno-app) in the Terreno monorepo.
 
 ## Non-empty targets
 
@@ -151,4 +151,4 @@ Cloud Run concepts and commands: [Deploy backend to Cloud Run](deploy-backend-to
 
 ## Monorepo examples (secondary)
 
-To explore Terreno itself without scaffolding a new app, clone the [Terreno monorepo](https://github.com/FlourishHealth/terreno) and use `example-backend` / `example-frontend`. See [Getting started](../tutorials/getting-started.md#explore-the-terreno-monorepo-examples).
+To explore Terreno itself without scaffolding a new app, clone the [Terreno monorepo](https://github.com/TerrenoLabs/terreno) and use `example-backend` / `example-frontend`. See [Getting started](../tutorials/getting-started.md#explore-the-terreno-monorepo-examples).

package/dist/docs/versioned/next/how-to/debug-with-mcp.md

@@ -0,0 +1,160 @@
+# Debug a Terreno app with MCP
+
+Start the backend and frontend, reproduce the failure once, then inspect the merged runtime evidence
+instead of copying logs into the agent chat.
+
+## 1. Read the latest error
+
+Call the local MCP tool:
+
+```json
+{"name":"last_error","arguments":{"sources":["backend","browser","metro","app"]}}
+```
+
+It returns the newest error-level JSONL/CDP entry. Use `read_logs` when the failure needs surrounding
+events:
+
+```json
+{
+  "name": "read_logs",
+  "arguments": {
+    "entries": 100,
+    "level": "error",
+    "sources": ["backend", "browser", "metro", "app"]
+  }
+}
+```
+
+`backend` and `browser` read durable JSONL; `metro` and `app` read in-memory rings populated from
+Metro `/events` and CDP. Connection status in the response explains when either live source is
+unavailable.
+
+CLI equivalents:
+
+```bash
+terreno logs last-error --sources backend,browser,metro,app
+terreno logs --entries 100 --level error --sources backend,browser,metro,app
+```
+
+## 2. Inspect client state
+
+Check authentication and non-synced RTK Query cache state:
+
+```json
+{"name":"get_rtk_state","arguments":{"slice":"rtk","query":"todos"}}
+```
+
+The tool reads `globalThis.__TERRENO_STORE__` registered by the app, using CDP when the MCP process
+cannot access the app heap directly. `slice: "auth"` prefers the Better Auth slice and falls back to
+legacy JWT auth; pass `betterAuth` to request that exact slice. The CLI equivalent is:
+
+Sensitive fields whose names include `password`, `token`, `secret`, `authorization`, or `cookie` are
+returned as `[REDACTED]`; use this summary to inspect cache state, never to retrieve credentials.
+
+```bash
+terreno state --slice rtk --query todos
+```
+
+## 3. Inspect and change SyncDB state
+
+Create the app client with `debug: true`, then inspect the same state that powers
+the SyncDB debugger:
+
+```json
+{"name":"get_syncdb_state","arguments":{"collection":"todos"}}
+```
+
+The result includes entities (including tombstones, seq/stream, and pending ids),
+decoded outbox rows, conflicts, cursors, known streams, repair markers, aggregate
+status, and debugger events. Sensitive fields are returned as `[REDACTED]`.
+
+Capture state before and after reproduction, then compare it:
+
+```json
+{"name":"syncdb_snapshot","arguments":{"action":"capture"}}
+{"name":"syncdb_snapshot","arguments":{"action":"capture"}}
+{"name":"syncdb_snapshot","arguments":{"action":"compare","snapshotId":"syncdb-...-1","otherSnapshotId":"syncdb-...-2"}}
+```
+
+Snapshots live in the local MCP process. Each capture privately retains the
+TinyBase mergeable content so `mergeSnapshot` can CRDT-merge it back later
+without wiping newer local rows (later HLCs win, including deletes). `get` and
+`compare` never return that merge payload. To restore a specific captured row,
+use `setLocalEntity` from `syncdb_snapshot` `get`.
+
+State changes require an explicit local opt-in:
+
+```bash
+TERRENO_MCP_EVAL=1 bunx terreno-mcp-local
+```
+
+Then use `syncdb_action`. Normal writes should use `mutate`; `flush` drains the
+outbox, and `reconcile` catches up from server snapshots:
+
+```json
+{"name":"syncdb_action","arguments":{"action":"mutate","collection":"todos","operation":"update","id":"todo-1","data":{"completed":true}}}
+{"name":"syncdb_action","arguments":{"action":"flush"}}
+{"name":"syncdb_action","arguments":{"action":"reconcile"}}
+```
+
+Other actions are `forceResync`, `resolveConflict`, `retryFailed`, `goOffline`,
+`goOnline`, `clearDebug`, `setLocalEntity`, `deleteLocalEntity`, and
+`mergeSnapshot`. Direct local edits bypass server validation and outbox
+semantics. `mergeSnapshot` CRDT-merges the captured TinyBase content into the
+live store (later HLCs win) instead of replacing it. Capture a baseline first
+and use these only for fault injection or repair.
+
+## 4. Prove the web fix
+
+Use Bun 1.4's built-in WebView through the local `browser` tool:
+
+```json
+{"name":"browser","arguments":{"action":"open","url":"http://localhost:8082"}}
+{"name":"browser","arguments":{"action":"wait","timeout":1000}}
+{"name":"browser","arguments":{"action":"click","selector":"[data-testid=save]"}}
+{"name":"browser","arguments":{"action":"snapshot"}}
+{"name":"browser","arguments":{"action":"screenshot","output":"/opt/cursor/artifacts/save-result.png"}}
+{"name":"browser","arguments":{"action":"close"}}
+```
+
+The session persists between MCP calls. `snapshot` returns visible text and up to 200 interactive
+elements so the agent can choose selectors and verify state without image guessing. `screenshot`
+saves the viewport for the PR or walkthrough.
+WebView console output is not added to `browser.log`; call `read_logs` alongside this flow when the
+running app posts browser logs to the backend collector. The collector accepts local-loopback
+traffic before login; devices or remote browsers must send the app's normal authentication.
+
+The equivalent one-process CLI sequence is:
+
+```bash
+terreno web http://localhost:8082 \
+  --action '{"action":"click","selector":"[data-testid=save]"}' \
+  --snapshot \
+  --screenshot /opt/cursor/artifacts/save-result.png
+```
+
+## 5. Verify the native fix in the running app
+
+Navigation and arbitrary evaluation are disabled by default. Opt in only for local debugging:
+
+```bash
+TERRENO_MCP_EVAL=1 bunx terreno-mcp-local
+```
+
+Then call `navigate` with `{"path":"/profile"}` or run:
+
+```bash
+TERRENO_MCP_EVAL=1 terreno navigate /profile
+```
+
+Confirm the target screen renders, then call `last_error` again. A successful fix has no new
+error-level entry after the navigation timestamp.
+
+## Connection problems
+
+- Upgrade to Bun 1.4 or newer when `Bun.WebView requires Bun 1.4 or newer` appears.
+- Set `BUN_CHROME_PATH` if WebView cannot discover Chrome, Chromium, or Edge on Linux or Windows.
+- Set `TERRENO_PROJECT_ROOT` if logs or package versions come from the wrong directory.
+- Set `TERRENO_METRO_URL` if Metro is not on the frontend script's `--port`.
+- Close React Native DevTools when Hermes reports another debugger connection.
+- Use only `backend,browser` sources when Metro is intentionally stopped.

package/dist/docs/versioned/next/how-to/deploy-to-gcp.md

@@ -20,7 +20,7 @@ Read the [deployment baseline](../explanation/deployment-baseline.md) — seven
 
 ## Scripts
 
-- [`scripts/setup-gcs-hosting.sh`](https://github.com/FlourishHealth/terreno/blob/master/scripts/setup-gcs-hosting.sh) — parameterized GCS + CDN provisioning for one site
+- [`scripts/setup-gcs-hosting.sh`](https://github.com/TerrenoLabs/terreno/blob/master/scripts/setup-gcs-hosting.sh) — parameterized GCS + CDN provisioning for one site
 
 ## Environment variables
 

package/dist/docs/versioned/next/how-to/deploy-web-to-gcs-cdn.md

@@ -174,7 +174,7 @@ gcloud compute url-maps invalidate-cdn-cache "${SITE_NAME}-url-map" \
 
 ## Static-only path
 
-This guide hosts the `expo export -p web` output as static files. Server-rendered web (SSR, API routes) requires Expo SDK ≥ 55 — see [Web SSR and admin SPA](https://github.com/FlourishHealth/terreno/blob/master/docs/implementationPlans/web-ssr-and-admin-spa.md).
+This guide hosts the `expo export -p web` output as static files. Server-rendered web (SSR, API routes) requires Expo SDK ≥ 55 — see [Web SSR and admin SPA](https://github.com/TerrenoLabs/terreno/blob/master/docs/implementationPlans/web-ssr-and-admin-spa.md).
 
 ## Related
 

package/dist/docs/versioned/next/how-to/generate-a-rest-cli.md

@@ -0,0 +1,34 @@
+# Generate a REST CLI from OpenAPI
+
+Run this from an app repo that already serves `/openapi.json` (Terreno `setupServer` does).
+
+1. Install the CLI: `bun add -g @terreno/cli` (or `bunx @terreno/cli`).
+2. Generate the wrapper:
+
+```bash
+terreno generate rest-cli \
+  --schema http://localhost:4000/openapi.json \
+  --out ./tools/app-cli \
+  --name myapp \
+  --base-url http://localhost:4000
+```
+
+3. Call the API:
+
+```bash
+cd tools/app-cli
+bun ./src/cli.ts list
+bun ./src/cli.ts call todo_list --param limit=10 --token "$TERRENO_TOKEN"
+bun ./src/cli.ts request GET /todos/{id} --param id=abc --json
+```
+
+Auth uses `--token` or `TERRENO_TOKEN`. Base URL uses `--base-url` or `TERRENO_API_URL`, then `servers[0].url` from the spec.
+
+To list or call without generating a package:
+
+```bash
+terreno api list --schema http://localhost:4000/openapi.json
+terreno api call todo_list --schema ./openapi.json --param limit=10
+```
+
+`generate rest-cli` writes `src/cli.ts` that imports `runAppRestCli` from `@terreno/cli`. Point that dependency at the published `@terreno/cli` version in apps outside this monorepo.

package/dist/docs/versioned/next/how-to/github-actions-ci.md

@@ -33,8 +33,8 @@ PR deploy preview.
 | `fingerprint-gate` | Master iOS/Android hashes cached per `pull_request.base.sha` (skips a second `bun run compile`) |
 | `maestro-e2e` | Demo export + static server only when `demo/`, `ui/`, or `.maestro/flows/demo/` change |
 | `example-backend-docker` | Buildx runs only when the image recipe changes (`Dockerfile`, lockfile, `package.json`). Source-only PRs skip; CD preview deploy still builds the image. `load: true` stays off. |
-| `cd` backend preview | Runs for every example-frontend PR preview, including frontend-only changes, so the Netlify build targets an isolated `pr-<number>` backend instead of production. The frontend deploy waits for that backend's healthy `/health` response before publishing to Netlify, and per-PR concurrency cancels duplicate deploys to the same alias. CD runs the built container against the configured Secret Manager values, including the Cloud Tasks `JOBS_*` env, and requires a healthy `/health` response before pushing or deploying. Preview Cloud Run uses `--memory=1Gi` and `--cpu-boost`, overwrites revision secrets, and binds `PORT` before MongoDB connect. Before deploy it rebuilds traffic with `--set-tags` / `--clear-tags` so a not-Ready tagged revision is omitted (`--remove-tags` leaves that revision in the spec and Cloud Run rejects the update). It then deploys `--no-traffic` without `--tag`, sets `--revision-suffix=pr<n>-<run_id>-<run_attempt>`, and tags the new Ready revision afterward. |
-| Bun install | `.github/actions/setup-bun-workspace` pins Bun `1.4.0` and caches `~/.bun/install/cache` without `github.ref` in the key |
+| `cd` Cloud Run deploys | Runs a local wrapper around `google-github-actions/deploy-cloudrun` that retries only the transient GitHub WIF subject-token timeout, up to three attempts; IAM, image, and configuration failures fail immediately. The backend preview runs for every example-frontend PR preview, including frontend-only changes, so the Netlify build targets an isolated `pr-<number>` backend instead of production. The frontend deploy waits for that backend's healthy `/health` response before publishing to Netlify, and per-PR concurrency cancels duplicate deploys to the same alias. CD runs the built container against the configured Secret Manager values, including the Cloud Tasks `JOBS_*` env, and requires a healthy `/health` response before pushing or deploying. Preview Cloud Run uses `--memory=1Gi` and `--cpu-boost`, overwrites revision secrets, and binds `PORT` before MongoDB connect. Before deploy it rebuilds traffic with `--set-tags` / `--clear-tags` so a not-Ready tagged revision is omitted (`--remove-tags` leaves that revision in the spec and Cloud Run rejects the update). It then deploys `--no-traffic` without `--tag`, sets `--revision-suffix=pr<n>-<run_id>-<run_attempt>`, and tags the new Ready revision afterward. |
+| Bun install | `.github/actions/setup-bun-workspace` pins Bun `1.4.0` and runs `bun install --frozen-lockfile` with no `~/.bun/install/cache`. CircleCI measurements: cache restore (~15–73s) exceeded the install savings (~9s). See [circleci.md](circleci.md#bun-install-is-uncached). |
 
 Playwright e2e on CircleCI groups specs into five shards (`e2e-auth`,
 `e2e-app`, `e2e-admin-core`, `e2e-admin-table`, `e2e-syncdb`). The retained GHA

package/dist/docs/versioned/next/how-to/github-issue-lifecycle.md

@@ -13,17 +13,17 @@ Two implementation paths:
 ## Create the issue
 
 1. Invoke `/create-github-issue` (or open
-   [Lifecycle work item](https://github.com/FlourishHealth/terreno/issues/new?template=work_item.yml)).
+   [Lifecycle work item](https://github.com/TerrenoLabs/terreno/issues/new?template=work_item.yml)).
 2. Fill **Affected package**, **Kind**, **Problem**, **Outcome**, **Current behavior**,
    **Non-scope**, **Acceptance**, and **Context**.
 3. Stop until the drafted title, body, and labels are approved. Then create.
 
-Existing [bug](https://github.com/FlourishHealth/terreno/issues/new?template=bug_report.yml),
-[feature](https://github.com/FlourishHealth/terreno/issues/new?template=feature_request.yml),
-and [docs](https://github.com/FlourishHealth/terreno/issues/new?template=docs_issue.yml)
+Existing [bug](https://github.com/TerrenoLabs/terreno/issues/new?template=bug_report.yml),
+[feature](https://github.com/TerrenoLabs/terreno/issues/new?template=feature_request.yml),
+and [docs](https://github.com/TerrenoLabs/terreno/issues/new?template=docs_issue.yml)
 forms still work. Prefer the lifecycle form when you want Roast-ready acceptance in
 the body. The canonical heading list is in the
-[`create-github-issue` skill](https://github.com/FlourishHealth/terreno/blob/master/.rulesync/skills/create-github-issue/references/issue-format.md).
+[`create-github-issue` skill](https://github.com/TerrenoLabs/terreno/blob/master/.rulesync/skills/create-github-issue/references/issue-format.md).
 
 `Affected package` must match a known value so issue triage can apply `area:*`.
 `Kind` on the lifecycle form is applied as `type:*` by the same triage job.
@@ -71,7 +71,7 @@ data-ownership decision. Those stay `status:needs-info` or go through `/work-git
 The unattended skill will assume implementation defaults; it will not invent those
 decisions.
 
-Labels live in [`.github/labels.yml`](https://github.com/FlourishHealth/terreno/blob/master/.github/labels.yml).
+Labels live in [`.github/labels.yml`](https://github.com/TerrenoLabs/terreno/blob/master/.github/labels.yml).
 Sync them with the existing roadmap labels workflow before expecting pickup.
 
 ## Related

package/dist/docs/versioned/next/how-to/install-agent-skills.md

@@ -3,8 +3,8 @@
 Install Terreno's agent skills into another repo or agent with the skills CLI.
 
 ```bash
-npx skills add FlourishHealth/terreno
-npx skills add FlourishHealth/terreno --skill terreno-1-grow
+npx skills add TerrenoLabs/terreno
+npx skills add TerrenoLabs/terreno --skill terreno-1-grow
 ```
 
 That copies the committed `skills/` tree: lifecycle stages (Grow, Pick, Roast, Brew,
@@ -30,36 +30,36 @@ goal running and heartbeats over the PRs it opens. See the
 
 ### Cursor
 
-Install `terreno-planning` from [`.cursor-plugin/marketplace.json`](https://github.com/FlourishHealth/terreno/blob/master/.cursor-plugin/marketplace.json), then invoke `/terreno-1-grow`.
+Install `terreno-planning` from [`.cursor-plugin/marketplace.json`](https://github.com/TerrenoLabs/terreno/blob/master/.cursor-plugin/marketplace.json), then invoke `/terreno-1-grow`.
 
 ### Codex
 
 ```text
-codex plugin marketplace add FlourishHealth/terreno
+codex plugin marketplace add TerrenoLabs/terreno
 codex plugin install terreno-planning --source terreno-plugins
 codex plugin install terreno-scan --source terreno-plugins
 $terreno-1-grow
 ```
 
-Marketplace: [`.agents/plugins/marketplace.json`](https://github.com/FlourishHealth/terreno/blob/master/.agents/plugins/marketplace.json).
+Marketplace: [`.agents/plugins/marketplace.json`](https://github.com/TerrenoLabs/terreno/blob/master/.agents/plugins/marketplace.json).
 Codex installs the canonical plugin at
-[`plugins/terreno-planning/`](https://github.com/FlourishHealth/terreno/tree/master/plugins/terreno-planning)
+[`plugins/terreno-planning/`](https://github.com/TerrenoLabs/terreno/tree/master/plugins/terreno-planning)
 (`.codex-plugin/plugin.json`). A clone of this repo already exposes that marketplace.
 
 ### Claude Code
 
 ```text
-/plugin marketplace add FlourishHealth/terreno
+/plugin marketplace add TerrenoLabs/terreno
 /plugin install terreno@terreno-plugins
 /plugin install terreno-scan@terreno-plugins
 /terreno:1-grow
 ```
 
-Marketplace: [`.claude-plugin/marketplace.json`](https://github.com/FlourishHealth/terreno/blob/master/.claude-plugin/marketplace.json).
+Marketplace: [`.claude-plugin/marketplace.json`](https://github.com/TerrenoLabs/terreno/blob/master/.claude-plugin/marketplace.json).
 Claude Code stages, app skills, and agents come from the generated copy at
-[`plugins/terreno-claude/`](https://github.com/FlourishHealth/terreno/tree/master/plugins/terreno-claude);
+[`plugins/terreno-claude/`](https://github.com/TerrenoLabs/terreno/tree/master/plugins/terreno-claude);
 scan stages come from
-[`plugins/terreno-scan-claude/`](https://github.com/FlourishHealth/terreno/tree/master/plugins/terreno-scan-claude).
+[`plugins/terreno-scan-claude/`](https://github.com/TerrenoLabs/terreno/tree/master/plugins/terreno-scan-claude).
 
 ## What you get
 
@@ -114,4 +114,4 @@ an agent finishes.
 Skills read architecture docs before changing code. After a user-visible or architectural
 change, update `docs/` in the same slice using `update-docs`. See
 [lifecycle plugin](../reference/lifecycle-plugin.md) and the
-[documentation contract](https://github.com/FlourishHealth/terreno/blob/master/plugins/terreno-planning/references/documentation-contract.md).
+[documentation contract](https://github.com/TerrenoLabs/terreno/blob/master/plugins/terreno-planning/references/documentation-contract.md).

package/dist/docs/versioned/next/how-to/migrate-rtk-to-syncdb.md

@@ -4,7 +4,7 @@ This guide is **AI-context-first**: it is written for an agent (or human) perfor
 
 `@terreno/syncdb` supersedes `@terreno/rtk` for **data synchronization** (CRUD reads/writes, offline queue, realtime convergence). It does not replace the generated OpenAPI SDK, Better Auth Redux wiring, or feature-flag infrastructure.
 
-`modelRouter` `realtime`, `realtimeList`, `realtimeDocument`, and `setRealtimeSocket` are **deprecated** and **will be removed in Terreno 58**. `RealtimeApp` stays as the socket host for syncdb. Removal checklist: [`docs/tasks/remove-legacy-realtime.md`](https://github.com/FlourishHealth/terreno/blob/master/docs/tasks/remove-legacy-realtime.md).
+`modelRouter` `realtime`, `realtimeList`, `realtimeDocument`, and `setRealtimeSocket` are **deprecated** and **will be removed in Terreno 58**. `RealtimeApp` stays as the socket host for syncdb. Removal checklist: [`docs/tasks/remove-legacy-realtime.md`](https://github.com/TerrenoLabs/terreno/blob/master/docs/tasks/remove-legacy-realtime.md).
 
 ## 1. Before you start
 
@@ -27,7 +27,7 @@ generated RTK hooks; admin RPC uses its host-bound fetch client.
 
 **Validation (Task 3.5):** The profile screen (`example-frontend/app/(tabs)/profile.tsx`) was reviewed against this guide. `useGetMeQuery` / `usePatchMeMutation` are **non-synced** custom SDK routes — the guide §8 explicitly says to keep them on RTK. No profile migration is required; the guide is sufficient for that case.
 
-Reference: [`docs/reference/syncdb.md`](../reference/syncdb.md), and the package [`syncdb/README.md`](https://github.com/flourishhealth/terreno/blob/release-56.0.0/syncdb/README.md).
+Reference: [`docs/reference/syncdb.md`](../reference/syncdb.md), and the package [`syncdb/README.md`](https://github.com/TerrenoLabs/terreno/blob/release-56.0.0/syncdb/README.md).
 
 ## 2. Install and configure
 
@@ -484,5 +484,5 @@ Before a collection can sync:
 ## Further reading
 
 - [`docs/reference/syncdb.md`](../reference/syncdb.md) — full API reference
-- [`syncdb/README.md`](https://github.com/flourishhealth/terreno/blob/release-56.0.0/syncdb/README.md) — architecture and protocol detail
+- [`syncdb/README.md`](https://github.com/TerrenoLabs/terreno/blob/release-56.0.0/syncdb/README.md) — architecture and protocol detail
 - [`docs/how-to/configure-better-auth.md`](configure-better-auth.md) — Better Auth setup

package/dist/docs/versioned/next/how-to/password-reset.md

@@ -20,6 +20,8 @@ Set `publicAppUrl` and `sendMail`. Forgot-password always returns 202.
 ```typescript
 authOptions: {
   publicAppUrl: process.env.FRONTEND_URL || "http://localhost:8082",
+  // Set false if the host already owns POST /resetPassword.
+  legacyResetPasswordRoute: false,
   sendMail: async (message) => {
     await getCommsService().sendMail(message);
   },
@@ -34,6 +36,11 @@ authOptions: {
 | Send verify | `POST /auth/sendVerification` | authenticated → 202 after delivery; 501 if `publicAppUrl` is missing |
 | Verify | `POST /auth/verifyEmail` | `{token}` |
 
+Recovery routes default on for compatibility. Set `authOptions.passwordReset: false` to omit
+both password-reset routes and forgot-password. Set `authOptions.emailVerification: false` to
+omit both verification routes. Set `authOptions.legacyResetPasswordRoute: false` when the host
+owns `POST /resetPassword`; `POST /auth/resetPassword` remains registered.
+
 Reset links: `${publicAppUrl}/resetPassword?token=...`. Verify links: `${publicAppUrl}/verifyEmail?token=...`.
 
 Set `requireEmailVerification: true` to return 403 `email-not-verified` on JWT login until verify succeeds. Signup still returns JWTs and sends the verify mail.

package/dist/docs/versioned/next/how-to/run-tests-locally.md

@@ -5,7 +5,7 @@ from the last CI run with these commands before pushing.
 
 Package unit tests use in-memory Mongo from `@terreno/test`. Playwright, Maestro, and
 the example-backend **dev** server need a replica-set `mongod` (see
-[AGENTS.md](https://github.com/FlourishHealth/terreno/blob/master/AGENTS.md) Cursor Cloud
+[AGENTS.md](https://github.com/TerrenoLabs/terreno/blob/master/AGENTS.md) Cursor Cloud
 section).
 
 ## Do now — package tests

package/dist/docs/versioned/next/how-to/set-up-terreno-mcp.md

@@ -0,0 +1,69 @@
+# Set up Terreno MCP
+
+Configure both Terreno servers: the hosted server supplies documentation and generators; the local
+stdio server inspects the app, database, logs, Metro, and Redux state.
+
+Install Bun 1.4 or newer to enable the local server's built-in WebView browser automation.
+
+## Cursor
+
+Add `.cursor/mcp.json` at the app repository root:
+
+```json
+{
+  "mcpServers": {
+    "terreno": {
+      "type": "http",
+      "url": "https://mcp.terreno.flourish.health/mcp"
+    },
+    "terreno-local": {
+      "command": "bunx",
+      "args": ["terreno-mcp-local"]
+    }
+  }
+}
+```
+
+## Claude Code
+
+Use the same project-scoped `.mcp.json`, or register the servers from the repository root:
+
+```bash
+claude mcp add --transport http terreno https://mcp.terreno.flourish.health/mcp
+claude mcp add terreno-local -- bunx terreno-mcp-local
+```
+
+## Configure local discovery
+
+Run the local server from the app root. It discovers bootstrap apps with `backend/` and `frontend/`,
+and this monorepo's `example-backend/` logs. Set these variables only when discovery needs help:
+
+| Variable | Use |
+| --- | --- |
+| `TERRENO_PROJECT_ROOT` | Absolute app/monorepo root |
+| `TERRENO_METRO_URL` | Metro origin when the frontend script does not expose `--port` |
+| `MONGO_URI` | MongoDB used by `database_schema` and read-only `database_query` |
+| `TERRENO_MCP_EVAL=1` | Explicitly enable `evaluate`, `navigate`, and SyncDB state changes |
+| `BUN_CHROME_PATH` | Chrome/Chromium/Edge binary when Bun cannot auto-discover one |
+
+Backend and browser JSONL normally live under `<backend cwd>/.terreno/logs/`. Keep Metro running to
+collect Metro `/events` and app console output over CDP. Hermes accepts one debugger connection, so
+close React Native DevTools if the local MCP reports that CDP is unavailable.
+
+## Verify
+
+Restart the editor's MCP clients, then ask it to call `application_info`. Confirm the result lists
+the app's installed `@terreno/*` versions. Next call `read_logs` with
+`{"sources":["backend","browser"]}`; an empty `entries` array is valid before the app logs anything.
+Call `browser` with `{"action":"open","url":"http://localhost:8082"}`, then `{"action":"snapshot"}`
+to confirm the agent can inspect the running web app. Finish with `{"action":"close"}`.
+If the app creates a SyncDB client with `debug: true`, call
+`get_syncdb_state` and confirm it returns the client name, status, collections,
+outbox, conflicts, cursors, and debug events.
+
+The CLI exposes the same local tools without MCP:
+
+```bash
+terreno info
+terreno logs --sources backend,browser
+```

package/dist/docs/versioned/next/how-to/upgrade-terreno.md

@@ -10,7 +10,7 @@ From the app root:
 bun pm ls --all | rg '@terreno/'
 ```
 
-Or call MCP `application_info` (`terreno-mcp-local`) and read each `package.json`. Record the lowest `@terreno/*` version as `fromVersion` and the target as `toVersion` (usually the latest tag on [GitHub Releases](https://github.com/FlourishHealth/terreno/releases)).
+Or call MCP `application_info` (`terreno-mcp-local`) and read each `package.json`. Record the lowest `@terreno/*` version as `fromVersion` and the target as `toVersion` (usually the latest tag on [GitHub Releases](https://github.com/TerrenoLabs/terreno/releases)).
 
 ## 2. Fetch notes for the range
 

package/dist/docs/versioned/next/implementationPlans/ModularAPI.md

@@ -1,6 +1,6 @@
 # Modular API Implementation Plan
 
-**Roadmap issue:** https://github.com/FlourishHealth/terreno/issues/1084  
+**Roadmap issue:** https://github.com/TerrenoLabs/terreno/issues/1084  
 **Status:** Complete
 
 ## Overview

package/dist/docs/versioned/next/implementationPlans/admin-improvements.md

@@ -4,7 +4,7 @@
 **Branch:** (implementation TBD)  
 **Owner:** Josh Gachnang  
 **Created:** 2026-06-01 (original); revised 2026-08-20 post–v2 gap analysis  
-**Roadmap issue:** https://github.com/FlourishHealth/terreno/issues/1099  
+**Roadmap issue:** https://github.com/TerrenoLabs/terreno/issues/1099  
 **Prerequisite:** [Admin UI v2 — Django-parity admin](./admin-ui-v2-django-parity.md) (**Complete**)  
 **Research:** [admin-improvements-research.md](./admin-improvements-research.md)
 ## Goal