@terreno/mcp 57.2.0 → 57.4.0

package/dist/docs/versioned/next/tasks/password-reset-and-email-verification.md

@@ -4,12 +4,12 @@ IP: [password-reset-and-email-verification](../implementationPlans/password-rese
 
 ## Phase 1 — Token infrastructure
 
-- [ ] **Task 1.1**: `AuthToken` model + issue/consume statics
+- [x] **Task 1.1**: `AuthToken` model + issue/consume statics
   - Description: hashed single-use tokens with TTL expiry per IP
   - Files: `api/src/authTokens.ts`, type files
   - Depends on: none
   - Acceptance: atomic single-use test (parallel consumes → one winner); expiry test
-- [ ] **Task 1.2**: `emailVerificationPlugin`
+- [x] **Task 1.2**: `emailVerificationPlugin`
   - Description: `emailVerified` field plugin for user schemas
   - Files: `api/src/plugins.ts`
   - Depends on: none
@@ -17,17 +17,17 @@ IP: [password-reset-and-email-verification](../implementationPlans/password-rese
 
 ## Phase 2 — JWT routes + mail
 
-- [ ] **Task 2.1**: forgot/reset routes
+- [x] **Task 2.1**: forgot/reset routes
   - Description: 202-always forgot; reset validates+consumes token, `setPassword`, invalidates refresh tokens; RTK client path/shape contract verified
   - Files: `api/src/authRecovery.ts`, `api/src/auth.ts`
   - Depends on: 1.1, comms-abstraction
   - Acceptance: enumeration-safety + happy-path supertest; RTK-shape test
-- [ ] **Task 2.2**: verification routes + `requireEmailVerification` option
+- [x] **Task 2.2**: verification routes + `requireEmailVerification` option
   - Description: sendVerification/verifyEmail; 403 `email-not-verified` gating on login when enabled
   - Files: `api/src/authRecovery.ts`, `api/src/auth.ts`
   - Depends on: 1.2, 2.1
   - Acceptance: gating on/off supertest
-- [ ] **Task 2.3**: Mail templates
+- [x] **Task 2.3**: Mail templates
   - Description: `resetPassword` + `verifyEmail` templates with app-override hook and `publicAppUrl` links
   - Files: `comms/src/templates.ts`
   - Depends on: comms-abstraction Phase 1
@@ -35,7 +35,7 @@ IP: [password-reset-and-email-verification](../implementationPlans/password-rese
 
 ## Phase 3 — Better Auth parity
 
-- [ ] **Task 3.1**: Better Auth hooks
+- [x] **Task 3.1**: Better Auth hooks
   - Description: `sendResetPassword`/`sendVerificationEmail` wired to the same templates
   - Files: `api/src/betterAuthSetup.ts`
   - Depends on: 2.3
@@ -43,17 +43,17 @@ IP: [password-reset-and-email-verification](../implementationPlans/password-rese
 
 ## Phase 4 — Client + docs
 
-- [ ] **Task 4.1**: example-frontend reset screen + verify banner
+- [x] **Task 4.1**: example-frontend reset screen + verify banner
   - Description: `/resetPassword` route + profile banner with re-send; SDK regen
   - Files: `example-frontend/app/resetPassword.tsx`, `app/(tabs)/profile.tsx`, `store/openApiSdk.ts`
   - Depends on: Phase 2
   - Acceptance: end-to-end flow with console adapter; UI verification evidence per verify-ui-changes
-- [ ] **Task 4.2**: `LoginScreen` forgot-password link prop
+- [x] **Task 4.2**: `LoginScreen` forgot-password link prop
   - Description: optional `onForgotPassword` on `@terreno/ui` LoginScreen
   - Files: `ui/src/login/LoginScreen.tsx` + tests + demo story
   - Depends on: none
   - Acceptance: renders only when provided; story added
-- [ ] **Task 4.3**: Docs
+- [x] **Task 4.3**: Docs
   - Description: how-to + env reference + rulesync
   - Files: `docs/how-to/password-reset.md`, `docs/reference/environment-variables.md`, `.rulesync/**`
   - Depends on: Phase 2

package/dist/docs/versioned/next/tasks/positioning-django-rails-universal.md

@@ -33,19 +33,19 @@ See: [`docs/implementationPlans/positioning-django-rails-universal.md`](../imple
 
 ## Phase 2: README restructure
 
-- [ ] **Task 2.1**: Restructure the README's opening
+- [x] **Task 2.1**: Restructure the README's opening
   - Description: Rewrite `README.md` above the packages list to this order: title with badges (preserve existing npm badges and the license badge from the governance IP), the `tagline` block as the subtitle, the `elevator` block, the three `pillars`, then a "Quickstart" section, then "Packages". Preserve the existing Vision and Philosophy content but fold it into the pillars rather than repeating it. Per IP question PO5, replace the "Where Terreno is headed" list with a two-line summary linking `ROADMAP.md`.
   - Files: `README.md`
   - Depends on: Task 1.1
   - Acceptance: "Django/Rails for TypeScript" appears within the first two sentences; the pillars appear in the IP's order; the roadmap section is two lines plus a link; no feature claimed that is not shipped.
 
-- [ ] **Task 2.2**: Move maintainer content out of the README
+- [x] **Task 2.2**: Move maintainer content out of the README
   - Description: Move these README sections to their correct homes: local development / bootstrap / linking instructions → `CONTRIBUTING.md`; the "Feature flags: OpenFeature migration" walkthrough → a new or existing page under `docs/how-to/` (check `docs/how-to/add-feature-flags.md` first — it may already cover this, in which case delete the README copy and link it); GCP project names, Cloud Run URLs, and Netlify hosts → `infra/flourish/README.md` (created by [`deploy-to-gcp`](../implementationPlans/deploy-to-gcp.md)) or a short "Live examples" list with URLs only and no infra detail; release instructions → `CONTRIBUTING.md`. After moving, grep the repo and `website/` for links to the removed anchors and fix them.
   - Files: `README.md`, `CONTRIBUTING.md`, `docs/how-to/add-feature-flags.md`, `infra/flourish/README.md`
   - Depends on: Task 2.1
   - Acceptance: `rg -i "flourish-terreno|a\.run\.app|Slack" README.md` returns nothing; no content was deleted without a new home; `bun run website:build` reports no new broken links.
 
-- [ ] **Task 2.3**: `[RTK]` Update the README architecture and package list
+- [x] **Task 2.3**: `[RTK]` Update the README architecture and package list
   - Description: Confirm the architecture diagram and published-package list reflect syncdb (this may already be done by `rtk-to-syncdb-migration-docs` Task 6.5 — check first and skip if so). Ensure every package in `publish-on-tag.yml` appears in the list exactly once with a one-line description matching its `package.json` description.
   - Files: `README.md`
   - Depends on: Task 2.2, `rtk-to-syncdb-migration-docs` Task 6.5
@@ -53,13 +53,13 @@ See: [`docs/implementationPlans/positioning-django-rails-universal.md`](../imple
 
 ## Phase 3: Docs site
 
-- [ ] **Task 3.1**: `[RTK]` Rewrite `docs/README.md`
+- [x] **Task 3.1**: `[RTK]` Rewrite `docs/README.md`
   - Description: Replace the opening line ("shared packages for full-stack applications with React Native and Express/Mongoose") with the `tagline` + `elevator` + `pillars` blocks. Keep the Diátaxis structure section. Rebuild the package table so it contains every published package including `@terreno/ai`, `@terreno/syncdb`, `@terreno/admin-spa`, and `@terreno/feature-flags`, with `rtk` under a Legacy heading. Update the Quick links section: remove the `.cursorrules` link if that file no longer exists, add `positioning.md`, `ROADMAP.md`, and `CONTRIBUTING.md`.
   - Files: `docs/README.md`
   - Depends on: Task 1.1, `rtk-to-syncdb-migration-docs` Task 2.3
   - Acceptance: tagline appears in the first two sentences; package table complete and matching `publish-on-tag.yml`; every Quick link resolves to an existing file.
 
-- [ ] **Task 3.2**: Update the docs site configuration
+- [x] **Task 3.2**: Update the docs site configuration
   - Description: In `website/docusaurus.config.ts`, set `tagline` to the canonical tagline and confirm `title`, `themeConfig.metadata` (og description), and navbar title read consistently. Check whether `website/src/pages/index.tsx` exists; if it does, update the hero to use the tagline, the three pillars, and one short code sample (a `modelRouter` registration plus the matching generated hook usage). If there is no custom landing page, note that in the PR body and skip the hero work.
   - Files: `website/docusaurus.config.ts`, `website/src/pages/index.tsx` (if present)
   - Depends on: Task 1.1
@@ -67,13 +67,13 @@ See: [`docs/implementationPlans/positioning-django-rails-universal.md`](../imple
 
 ## Phase 4: Agent surfaces
 
-- [ ] **Task 4.1**: `[RTK]` Update root agent context files
+- [x] **Task 4.1**: `[RTK]` Update root agent context files
   - Description: In `.rulesync/rules/00-root.md` (the source for `AGENTS.md`, `CLAUDE.md`, `.cursor/rules/00-root.mdc`, and the copilot instructions), replace the opening "A monorepo containing shared packages…" with the `tagline` + `elevator` + `pillars`. Keep all existing conventions content unchanged. Apply the same opening to `CLAUDE-consumer.md`. Then run `bun run rules` and commit every generated mirror. Note: `CLAUDE.local.md` appears to be a stale duplicate of `CLAUDE.md` — verify and either update or delete it, reporting which you chose and why.
   - Files: `.rulesync/rules/00-root.md`, `CLAUDE-consumer.md`, possibly `CLAUDE.local.md`, generated mirrors
   - Depends on: Task 1.1
   - Acceptance: `bun run rules:check` exits 0; `AGENTS.md` and `CLAUDE.md` both open with the positioning; no conventions content was lost (diff review); the `CLAUDE.local.md` decision is explained in the PR body.
 
-- [ ] **Task 4.2**: Update the MCP overview resource
+- [x] **Task 4.2**: Update the MCP overview resource
   - Description: Update `mcp-server/src/docs/resources/overview.md` to open with the positioning blocks so agents reading `terreno://docs/overview` describe Terreno consistently. Check the other resource bundles (`api`, `ui`, `rtk`/`syncdb`, `patterns`) for stale positioning language in their intros and fix those too.
   - Files: `mcp-server/src/docs/resources/*.md`
   - Depends on: Task 4.1
@@ -81,7 +81,7 @@ See: [`docs/implementationPlans/positioning-django-rails-universal.md`](../imple
 
 ## Phase 5: Metadata
 
-- [ ] **Task 5.1**: Standardize `package.json` descriptions
+- [x] **Task 5.1**: Standardize `package.json` descriptions
   - Description: For every package published by `publish-on-tag.yml`, set `description` to the pattern `<what it does> — part of Terreno, the batteries-included TypeScript framework for universal apps.` Keep the first clause specific and accurate per package (do not make them all identical). Also confirm `keywords`, `repository`, `homepage`, and `bugs` fields are present and correct on every published package — missing `repository` fields hurt npm discoverability.
   - Files: every published `package.json`
   - Depends on: Task 1.1
@@ -93,7 +93,7 @@ See: [`docs/implementationPlans/positioning-django-rails-universal.md`](../imple
   - Depends on: Task 1.1
   - Acceptance: the exact description string and full topic list are present and marked as a manual maintainer step.
 
-- [ ] **Task 5.3**: Consistency sweep
+- [x] **Task 5.3**: Consistency sweep
   - Description: Grep the repo for stale positioning language and fix every hit: `rg -n "monorepo containing shared packages"`, `rg -ni "cross-platform"` (should be "universal app" in prose; library-internal technical uses are fine — judge case by case), and `rg -n "88\+ components|90\+ components"` (component counts drift; either verify the number against `ui/src/index.tsx` exports or replace with "a large component library"). Report the count of fixes in the PR body.
   - Files: various
   - Depends on: Task 4.1, Task 3.1

package/dist/docs/versioned/next/tasks/rate-limiting.md

@@ -0,0 +1,70 @@
+# Tasks: API rate limiting
+
+IP: [rate-limiting.md](../implementationPlans/rate-limiting.md)  
+**Closes:** https://github.com/FlourishHealth/terreno/issues/1187
+
+**Feature profile:** false (full IP)
+
+## Phase 1 — Tracer (memory, TerrenoApp)
+
+- [x] **Task 1.1**: Rate-limit module + TerrenoApp mount
+  - Delivers: `rateLimit: {}` on `TerrenoApp` limits HTTP; omitted option is a no-op; `POST /auth/login` uses the auth bucket (20 / 15 min); modelRouter list uses `api` (600 / 15 min); skip `/health` and `/openapi.json`; 429 `APIError` `code: "rate-limit-exceeded"` with `Retry-After` and IETF `RateLimit` / `RateLimit-Policy`; memory store; `trust proxy` default `1` when enabled
+  - Files: `api/src/rateLimit/types.ts`, `api/src/rateLimit/store.ts`, `api/src/rateLimit/memoryStore.ts`, `api/src/rateLimit/policies.ts`, `api/src/rateLimit/middleware.ts`, `api/src/rateLimit/rateLimit.test.ts`, `api/src/terrenoApp.ts`, `api/src/index.ts`, `api/src/api.ts` (remove `TODO add rate limit`)
+  - Blocked by: none
+  - Skills: `terreno-backend-api`, `backend-test-env`, `update-docs`
+  - Docs: stub section in `docs/reference/api.md` (`rateLimit` option) so the tracer is documented when it lands
+  - Acceptance: bun tests — default off (burst login no 429); auth 20 then 429; 21st list GET still 200; 601st list 429; `/health` never 429; 429 body/headers; login classified auth
+
+## Phase 2 — Shared stores
+
+- [x] **Task 2.1**: Redis store
+  - Delivers: `store: "redis"` uses `VALKEY_URL` then `REDIS_URL`; missing URL fails startup with a clear `APIError`; consume contract matches memory
+  - Files: `api/src/rateLimit/redisStore.ts`, tests with a fake client; optional skip-if-no-redis integration
+  - Blocked by: 1.1
+  - Skills: `terreno-backend-api`
+  - Docs: store table in `docs/how-to/rate-limiting.md` (create page if 4.1 not started — Pick may write the Redis rows into the how-to started in 1.1/4.1)
+  - Acceptance: unit tests against the store interface; startup failure without URL
+
+- [x] **Task 2.2**: Mongo store
+  - Delivers: `store: "mongo"` uses the process mongoose connection and `rateLimitHits` with TTL expiry; same consume contract
+  - Files: `api/src/rateLimit/mongoStore.ts` (+ schema/types if a model is used), tests against in-memory Mongo via existing `@terreno/test` harness
+  - Blocked by: 1.1
+  - Skills: `mongoose-schema-safety` (if a Mongoose schema is added), `backend-test-env`
+  - Docs: Mongo collection / TTL note on the how-to
+  - Acceptance: two keys isolated; expiry/window reset; no public modelRouter for hits
+
+## Phase 3 — Paths and proxy
+
+- [x] **Task 3.1**: Auth path table + Better Auth / GitHub
+  - Delivers: GitHub OAuth start/callback on auth bucket; Better Auth `basePath` sign-in/sign-up/forget-password on auth; `/auth/me` on api; extra `skip` callback honored
+  - Files: `api/src/rateLimit/policies.ts`, tests
+  - Blocked by: 1.1
+  - Acceptance: supertest (or middleware unit tests with req.url) for each classified prefix
+
+- [x] **Task 3.2**: Trust-proxy keying
+  - Delivers: with `trustProxy: 1`, `X-Forwarded-For` client IP is the unauthenticated key; `trustProxy: false` ignores spoofed forwarded-for; override hop count works
+  - Files: `api/src/rateLimit/*.ts`, `api/src/terrenoApp.ts`, tests
+  - Blocked by: 1.1
+  - Acceptance: two tests (trust on vs off) with distinct `X-Forwarded-For` values
+
+## Phase 4 — Docs and example
+
+- [x] **Task 4.1**: Diátaxis + changelog + rules
+  - Delivers: operator how-to, reference, auth explanation, env reference (no enable env), replace misleading `RATE_LIMIT_*` snippet in configuration-system, Terreno 58 default-on note, `.rulesync/rules/api/00-api.mdc`, `CHANGELOG.md` Added
+  - Files: `docs/how-to/rate-limiting.md`, `docs/reference/api.md`, `docs/reference/environment-variables.md`, `docs/explanation/authentication.md`, `docs/explanation/configuration-system.md`, `.rulesync/rules/api/00-api.mdc`, `CHANGELOG.md`; `bun run rules` / `skills:sync` if required after rulesync
+  - Blocked by: 1.1 (content can land with 2.x/3.x; must match shipped stores)
+  - Skills: `update-docs`
+  - Acceptance: a stranger can enable Redis on Cloud Run from the how-to; 58 default-on is explicit; `bun run website:build` if docs site is in the slice
+
+- [x] **Task 4.2**: example-backend snippet (limiter stays off)
+  - Delivers: commented `rateLimit: process.env.RATE_LIMIT_ENABLED === "true" ? {store: "memory"} : undefined` (or equivalent) showing app-owned env
+  - Files: `example-backend/src/server.ts` (or `index`/`terrenoApp` bootstrap)
+  - Blocked by: 1.1
+  - Acceptance: default example server still has no limiter; comment compiles if uncommented
+
+- [x] **Task 4.3**: Roadmap seed + 58 upgrade stub
+  - Delivers: `docs/explanation/roadmap-seed-issues.md` `rate-limiting` section points at IP/task GitHub URLs and `IP=rate-limiting`; how-to or `mcp-server/src/docs/upgrades/` notes that Terreno 58 defaults the limiter on
+  - Files: `docs/explanation/roadmap-seed-issues.md`; upgrade note path named in how-to until 58 exists
+  - Blocked by: 4.1
+  - Skills: `update-docs`
+  - Acceptance: seed `Implementation plan` / `Tasks` links are not `*(not yet written)*`

package/dist/docs/versioned/next/tasks/remove-legacy-realtime.md

@@ -0,0 +1,59 @@
+# Task List: Remove legacy RTK realtime in Terreno 58
+
+See: [`docs/implementationPlans/remove-legacy-realtime.md`](../implementationPlans/remove-legacy-realtime.md)
+
+**Target:** Terreno **58.0.0**. Do not execute Phase 2 on the 57.x line.
+
+`RealtimeApp` is **not** in this deletion. It remains the Socket.io / change-stream host for `@terreno/syncdb`.
+
+## Phase 1: Deprecate on 57.x (current)
+
+- [x] **Task 1.1**: Runtime and JSDoc deprecation for `modelRouter` `realtime`
+  - Delivers: one-time `logger.warn` per model/path; `@deprecated` on `ModelRouterOptions.realtime`, `RealtimeConfig`, and `RealtimeEvent`
+  - Files: `api/src/realtime/deprecation.ts`, `api/src/api.ts`, `api/src/realtime/types.ts`, `api/src/realtime/deprecation.test.ts`
+  - Blocked by: none
+  - Acceptance: tests prove one warning per model/path; message names Terreno 58 and `@terreno/syncdb`
+
+- [x] **Task 1.2**: Runtime and JSDoc deprecation for RTK cache-patching helpers
+  - Delivers: one-time `console.warn`; `@deprecated` on `realtimeList`, `realtimeDocument`, `setRealtimeSocket`, `getRealtimeSocket`, `RealtimeEvent`
+  - Files: `rtk/src/realtime.ts`, `rtk/src/realtime.test.ts`
+  - Blocked by: none
+  - Acceptance: tests prove a single warning across the three helpers; message names Terreno 58 and `@terreno/syncdb`
+
+- [x] **Task 1.3**: Docs, changelog, and agent skills
+  - Delivers: consumers can find the sunset date and replacement without reading source
+  - Files: `docs/reference/api.md`, `docs/how-to/migrate-rtk-to-syncdb.md`, `docs/reference/legacy/rtk.md`, `changelog/unreleased/`, `.rulesync/skills/`
+  - Blocked by: Task 1.1, Task 1.2
+  - Acceptance: docs say `RealtimeApp` stays; `modelRouter` `realtime` and RTK helpers go away in 58
+
+## Phase 2: Delete in Terreno 58
+
+- [ ] **Task 2.1**: Remove `modelRouter` `realtime` registration
+  - Delivers: passing `realtime` is a type error; no `registerRealtime` from `modelRouter`
+  - Files: `api/src/api.ts`, `api/src/realtime/types.ts`, `api/src/realtime/deprecation.ts`, `api/src/index.ts`, `api/src/api.test.ts`
+  - Blocked by: Terreno 58 major
+  - Acceptance: TypeScript and tests fail if a router still passes `realtime`; `sync` registration is unchanged
+
+- [ ] **Task 2.2**: Stop emitting legacy `sync` (RTK) websocket events
+  - Delivers: change streams emit `sync:delta` only for synced models; no RTK `sync` payload
+  - Files: `api/src/realtime/changeStreamWatcher.ts`, `api/src/realtime/realtimeApp.ts`, `api/src/realtime/registry.ts`, related tests
+  - Blocked by: Task 2.1
+  - Acceptance: a model with only `sync` still emits `sync:delta`; no `sync` events for collection CRUD; `admin:model.changed` still works when `admin.realtime` is true
+
+- [ ] **Task 2.3**: Remove `@terreno/rtk` cache-patching helpers
+  - Delivers: `realtimeList`, `realtimeDocument`, `setRealtimeSocket`, `getRealtimeSocket` are gone from the package
+  - Files: `rtk/src/realtime.ts`, `rtk/src/realtime.test.ts`, `rtk/src/index.ts`, `rtk/README.md`
+  - Blocked by: Task 2.1
+  - Acceptance: package compile fails if those symbols are imported; `useSocketConnection` still exists
+
+- [ ] **Task 2.4**: Remove example and bootstrap usage
+  - Delivers: example-backend/example-frontend/MCP bootstrap do not configure RTK realtime
+  - Files: `example-backend/src/api/todos.ts`, `example-frontend/store/sdk.ts`, `example-frontend/app/_layout.tsx`, MCP bootstrap templates
+  - Blocked by: Task 2.3
+  - Acceptance: todos stay on `sync` + syncdb; `setRealtimeSocket` / `realtimeList` / `realtimeDocument` are gone; `RealtimeApp` remains registered
+
+- [ ] **Task 2.5**: Docs, skills, changelog, 58.0.0 upgrade note
+  - Delivers: upgrade note lists every removed symbol and the syncdb replacement
+  - Files: `docs/how-to/migrate-rtk-to-syncdb.md`, `docs/reference/api.md`, `.rulesync/skills/terreno-data-fetching/references/realtime.md`, `.rulesync/skills/terreno-backend-api/references/model-router.md`, `mcp-server/src/docs/upgrades/58.0.0.md`, changelog
+  - Blocked by: Task 2.4
+  - Acceptance: `bun run check:changelog` passes for 58.0.0; upgrade note exists; no skill tells agents to set `modelRouter` `realtime` for collection CRUD

package/dist/docs/versioned/next/tasks/ui-performance.md

@@ -0,0 +1,134 @@
+# Task List: UI Render and Startup Performance
+
+**Feature profile:** true
+
+## Durable contract
+
+- **Destination:** `@terreno/ui` avoids unnecessary render, parse, and layout work on common app
+  paths without changing visible output, interactions, accessibility, or public root imports.
+- **Completed foundation:** P0 primitives and theme work landed in PR #1131. P1 table-update,
+  icon-update, and package-subpath work is covered by `bun run performance:p1` and
+  `docs/reference/ui-performance.md`.
+- **Scope:** the remaining static-audit priorities below, in priority order. Each optimization must
+  add a representative example renderer or import workload, capture a same-machine baseline, and
+  add behavior regression coverage before production code changes.
+- **Non-goals:** visual redesigns, public API removals, root-barrel removal, or benchmark-driven
+  changes without a measured improvement.
+- **Decisions:** keep `@terreno/ui` root imports supported; use Luxon for date work; preserve
+  React Native Web; treat changed-prop/theme work as required behavior rather than overhead to hide.
+- **Tracer:** one real demo story and one benchmark workload per task, exercised before and after
+  the optimization.
+- **Verification seam:** focused Bun regressions, `bun run ui:test`, `bun run lint`,
+  `bun run compile`, the relevant performance script, and a running demo video.
+
+## Instructions for the implementing agent
+
+- Work one task per PR. Do not combine unrelated hot paths.
+- Add regression coverage and record the baseline before changing production code.
+- Report initial, equivalent-prop, and changed-prop medians. Startup tasks must use fresh-process or
+  bundle-graph measurements so module caches do not invalidate the comparison.
+- A faster result with changed output, lost keyboard behavior, stale theme data, or stale layout is
+  a failure.
+- Update `docs/reference/ui-performance.md` with the final same-machine measurements.
+
+### Phase 1: Finish omitted and deferred high-priority work
+
+- [x] **Task 1.1**: Stabilize `OpenAPIProvider` context values (leftover P0)
+  - Delivers: unrelated parent renders no longer fan out through unchanged OpenAPI model metadata.
+  - Files: `ui/src/OpenAPIContext.tsx`, focused regression tests, `ui/benchmarks/`, `ui/package.json`,
+    `docs/reference/ui-performance.md`
+  - Blocked by: none
+  - Acceptance: benchmark an example tree with many OpenAPI consumers; memoize provider actions and
+    value with complete dependencies; unchanged metadata skips consumer renders; replacing the spec
+    updates field lookups immediately; existing form/admin behavior and the full UI suite pass.
+
+- [x] **Task 1.2**: Virtualize large `DataTable` row sets without changing table behavior
+  - Delivers: initial mount cost and mounted row count scale with the viewport instead of total rows.
+  - Files: `ui/src/DataTable.tsx`, `ui/src/DataTable.test.tsx`, P1 regressions and benchmark,
+    `demo/stories/DataTable.stories.tsx`, `docs/reference/ui-performance.md`
+  - Blocked by: none
+  - Acceptance: benchmark at least 1,000 rows with pinned and unpinned columns; mounted rows remain
+    viewport-bounded; sorting, pagination, alternating/highlight colors, custom cells, row test IDs,
+    header/body scroll sync, pinned columns, and row-detail modals match current behavior on web and
+    native; changed rows render correctly after scrolling.
+
+- [ ] **Task 1.3**: Keep optional `DataTable` markdown off the default import path
+  - Delivers: tables without `infoModalText` do not parse or evaluate the markdown renderer.
+  - Files: `ui/src/DataTable.tsx`, a focused header-info component, tests, import benchmark,
+    `docs/reference/ui-performance.md`
+  - Blocked by: Task 1.2
+  - Acceptance: a fresh-process or bundle-graph measurement proves markdown is absent from the
+    default table path; opening header info still renders identical markdown with an explicit
+    loading/error state; table snapshots and interactions remain unchanged.
+
+- [x] **Task 1.4**: Measure and isolate remaining heavy root-import modules
+  - Delivers: startup guidance and lazy boundaries for heavy optional widgets while the root import
+    remains compatible.
+  - Files: `ui/src/index.tsx`, heavy components identified by the measurement, `ui/package.json`,
+    import benchmark, `docs/reference/ui.md`, `docs/reference/ui-performance.md`
+  - Blocked by: none
+  - Acceptance: compare fresh root and subpath imports by evaluated module count, output bytes, and
+    elapsed time; isolate only measured heavy optional paths; `import {Button} from "@terreno/ui"`
+    remains valid; every existing `@terreno/ui/*`, `src/*`, and `dist/*` path still resolves.
+
+- [ ] **Task 1.5**: Decide whether table chrome needs a smaller icon path
+  - Delivers: an evidence-based keep-or-change decision for FontAwesome table chrome.
+  - Files: `ui/src/Icon.tsx`, `ui/src/DataTable.tsx`, icon/import benchmarks, tests,
+    `docs/reference/ui-performance.md`
+  - Blocked by: Task 1.3
+  - Acceptance: measure current glyph import and render cost first; if a smaller path materially
+    improves it, preserve icon names, sizes, weights, colors, custom-icon precedence, font loading,
+    and accessibility; otherwise make no production change and record the measured no-change
+    decision.
+
+### Phase 2: P2 component hot paths
+
+- [ ] **Task 2.1**: Stabilize `DateTimeField` sheet identity and cold platform paths
+  - Delivers: rerenders retain the same sheet ref, and unused desktop/mobile date-picker paths stay
+    cold.
+  - Files: `ui/src/DateTimeField.tsx`, date-time sheet modules, tests, benchmark/example renderer,
+    `docs/reference/ui-performance.md`
+  - Blocked by: Task 1.4
+  - Acceptance: replace render-time `createRef` with a stable ref; benchmark closed and open states;
+    date, time, datetime, timezone, validation, open/close, and imperative behavior match on web and
+    native; first-open loading and import failures have tested states.
+
+- [ ] **Task 2.2**: Load emoji data only when `EmojiSelector` opens
+  - Delivers: apps that do not open the selector avoid parsing `emoji-datasource`.
+  - Files: `ui/src/EmojiSelector.tsx`, tests, import benchmark/example renderer,
+    `docs/reference/ui-performance.md`
+  - Blocked by: Task 1.4
+  - Acceptance: fresh-process or bundle-graph results prove emoji data is absent before open;
+    first open has tested loading/error states; search, categories, selection, skin-tone behavior,
+    reopen behavior, and web/native rendering remain unchanged.
+
+- [x] **Task 2.3**: Stabilize plain and confirmation `Button` render paths
+  - Delivers: debounce identity and plain-button renders stay stable without weakening duplicate
+    submission protection.
+  - Files: `ui/src/Button.tsx`, button tests, benchmark/example renderer,
+    `docs/reference/ui-performance.md`
+  - Blocked by: none
+  - Acceptance: equivalent props skip avoidable work; plain buttons do not allocate confirmation
+    state or load the modal path; rapid presses, delayed handlers, unmount cleanup, loading,
+    disabled, keyboard, haptic, and confirmation behavior match current tests and running stories.
+
+- [x] **Task 2.4**: Replace synchronous responsive dimension reads with reactive breakpoints
+  - Delivers: responsive `Box` props read one shared window state and update correctly on rotation
+    and resize.
+  - Files: `ui/src/MediaQuery.ts`, `ui/src/Box.tsx`, provider/hook files if needed, tests,
+    benchmark/example renderer, `docs/reference/ui-performance.md`
+  - Blocked by: none
+  - Acceptance: benchmark a large responsive `Box` tree; remove per-box synchronous
+    `Dimensions.get` calls; native `sm`/`md`/`lg`/`xl` (320/375/600/1024) and web `lg`/`xl`
+    (1024/1280) boundaries match the product spec; resize, rotation, SSR hydration, web, and
+    native behavior have regressions and running-demo proof.
+
+- [ ] **Task 2.5**: Close the measured hot-style allocation backlog
+  - Delivers: only proven hot leaves reuse style objects without stale theme values.
+  - Files: measured hotspots in `DataTable`, `Button`, `Modal`, `Filter`, `Text`, or `Box`; focused
+    tests and benchmarks; `docs/reference/ui-performance.md`
+  - Blocked by: Tasks 1.2, 2.3, 2.4
+  - Acceptance: profile first and list the selected hotspots; cache styles with every theme/layout
+    dependency represented; equivalent renders improve measurably; changed themes, dimensions,
+    highlights, disabled states, and animations remain visually identical; do not perform a
+    library-wide style rewrite.

package/dist/docs/versioned/next/tasks/unified-mutation-executors.md

@@ -0,0 +1,35 @@
+# Tasks: Unified mutation executors
+
+IP: [unified-mutation-executors.md](../implementationPlans/unified-mutation-executors.md)
+
+## Phase 1 — MCP create → `executeCreate`
+
+- [x] **Task 1.1**: MCP create uses `executeCreate`
+  - Delivers: `handleCreate` calls `executeCreate`; `model.create` gone from create path; MCP error mapping for `APIError`
+  - Files: `api/src/mcp/handlers.ts`, `api/src/mcp/integration.test.ts`, `api/src/sync/executors.test.ts` (only if a shared hook case is missing)
+  - Blocked by: none
+  - Docs: none yet (behavior still MCP-only on create)
+  - Skills: `backend-test-env` if tests touch `process.env`; `update-docs` not required until Phase 3
+  - Acceptance: existing MCP `handleCreate` tests pass; one test proves `preCreate` runs for MCP create; `rg "model.create" api/src/mcp/handlers.ts` is empty on the create path
+
+## Phase 2 — Update and delete
+
+- [x] **Task 2.1**: MCP update uses `executeUpdate`
+  - Delivers: `handleUpdate` adapter only
+  - Files: `api/src/mcp/handlers.ts`, `api/src/mcp/integration.test.ts`
+  - Blocked by: 1.1
+  - Acceptance: MCP update tests pass; no `doc.save()` in `handleUpdate`
+- [x] **Task 2.2**: MCP delete uses `executeDelete`
+  - Delivers: `handleDelete` adapter only (soft-delete semantics from executor)
+  - Files: `api/src/mcp/handlers.ts`, `api/src/mcp/integration.test.ts`
+  - Blocked by: 1.1
+  - Acceptance: MCP delete tests pass; persistence only inside executor
+
+## Phase 3 — Contract and docs
+
+- [x] **Task 3.1**: Docs + changelog
+  - Delivers: explanation/reference match the single write pipeline
+  - Files: `docs/explanation/model-router-actions.md`, `docs/reference/api.md`, `docs/implementationPlans/model-router-mcp.md` (pointer), changelog fragment
+  - Blocked by: 2.1, 2.2
+  - Skills: `update-docs`
+  - Acceptance: a stranger can find “MCP writes use executors” from docs without reading the PR

package/dist/docs/versioned/next/tasks/upgrade-guides-and-skill.md

@@ -13,25 +13,25 @@ See: [`docs/implementationPlans/upgrade-guides-and-skill.md`](../implementationP
 
 ## Phase 1: Note format and backfill
 
-- [ ] **Task 1.1**: Define the upgrade note format
+- [x] **Task 1.1**: Define the upgrade note format
   - Description: Create `mcp-server/src/docs/upgrades/README.md` documenting the required note format from the IP: frontmatter-style header (`Action required`, `Affected packages`) then `Summary`, `Breaking changes` (each with What changed / Why / Migration with before-and-after code), `Deprecations`, `New capabilities`, `Verification`. Explain that notes are concatenated by `terreno_get_upgrade_guide` across a version range, so each must be self-contained and must not assume the reader read an adjacent note. Include a copy-paste template. Read the existing `0.20.0.md` and `0.21.0.md` first and keep the format compatible with them.
   - Files: `mcp-server/src/docs/upgrades/README.md` (new)
   - Depends on: none
   - Acceptance: the format is compatible with the two existing notes; the template includes every required section; the self-contained requirement is stated with its reason.
 
-- [ ] **Task 1.2**: Research what changed between 0.21.0 and the current version
+- [x] **Task 1.2**: Research what changed between 0.21.0 and the current version
   - Description: For each release from 0.22.0 through the current version, run `gh release view <tag>` and `git log --oneline <prev>..<tag>`, and diff the public surface of each published package (`git diff <prev>..<tag> -- '*/src/index.ts'`). Identify actual breaking changes, deprecations, and notable additions. Record findings per version in the PR body. Pay particular attention to the OpenFeature feature-flag migration, which the README documents as requiring consumer action — that is a breaking change with no upgrade note.
   - Files: none (findings in the PR body)
   - Depends on: Task 1.1
   - Acceptance: every version from 0.22.0 to current is covered; each finding cites a commit or diff; the feature-flag migration is captured.
 
-- [ ] **Task 1.3**: Write the consolidated backfill note
+- [x] **Task 1.3**: Write the consolidated backfill note
   - Description: Per IP question U1, write a single consolidated note covering 0.21.0 → current (name it for the current version). Include everything from Task 1.2 that requires consumer action, organized by concern rather than by version. Open with an honest note that per-release notes were not maintained for this range and that this note consolidates them. Move the OpenFeature feature-flag migration content out of `README.md` into this note (or into `docs/how-to/add-feature-flags.md`) and link it, rather than leaving a migration guide in the README.
   - Files: `mcp-server/src/docs/upgrades/<current-version>.md` (new), `README.md`, `docs/how-to/add-feature-flags.md`
   - Depends on: Task 1.2
   - Acceptance: every action-requiring change from Task 1.2 appears; the feature-flag migration is no longer in `README.md`; `terreno_get_upgrade_guide` with the range 0.21.0 → current returns this note's content.
 
-- [ ] **Task 1.4**: Improve the empty-range response
+- [x] **Task 1.4**: Improve the empty-range response
   - Description: Update `terreno_get_upgrade_guide` in `mcp-server/src/tools.ts` so that a range with no recorded notes returns an explicit message naming the versions with no notes, rather than empty output — an agent seeing empty output concludes nothing changed, which is the opposite of the truth. Also have it list which versions in the range *did* have notes. Add tests for: range fully covered, range partially covered, range with no notes, and an invalid range.
   - Files: `mcp-server/src/tools.ts`, tests under `mcp-server/src/`
   - Depends on: Task 1.3
@@ -39,13 +39,13 @@ See: [`docs/implementationPlans/upgrade-guides-and-skill.md`](../implementationP
 
 ## Phase 2: Versioning policy
 
-- [ ] **Task 2.1**: Write `docs/explanation/versioning-policy.md`
+- [x] **Task 2.1**: Write `docs/explanation/versioning-policy.md`
   - Description: Document: what lockstep versioning means (all `@terreno/*` packages share a version; you upgrade them together and mixing versions is unsupported — verify this claim against `publish-on-tag.yml` and any peer-dependency constraints before asserting it); the pre-1.0 policy (breaking changes may land in minor releases, always with an upgrade note); the deprecation window from IP question U6 (minimum three minor releases, with the RTK deprecation as the worked example); where to find upgrade notes and the changelog; and what 1.0 will mean when it happens (link program question P9). Keep it short and concrete — this document is a promise, so every sentence must be one the team will keep.
   - Files: `docs/explanation/versioning-policy.md` (new), `docs/explanation/README.md`
   - Depends on: Task 1.3
   - Acceptance: the lockstep claim is verified against the publish workflow and peer deps; the deprecation window is a specific number; the RTK deprecation is used as the example; linked from the explanation index.
 
-- [ ] **Task 2.2**: `[RTK]` Write `docs/how-to/upgrade-terreno.md`
+- [x] **Task 2.2**: `[RTK]` Write `docs/how-to/upgrade-terreno.md`
   - Description: The human-facing upgrade guide. Cover: checking your current versions; finding the notes for your range (both via `terreno_get_upgrade_guide` and by browsing the notes directory); the correct ordering with the reasoning for each step (backend before frontend because the OpenAPI spec is the contract; Expo before Terreno frontend packages because `@terreno/ui` pins peers against Expo versions — verify both claims); the manual steps for each phase; verification; and rollback. Add a prominent section for the RTK → syncdb upgrade linking `docs/how-to/migrate-rtk-to-syncdb.md` as a larger, separate operation that should not be combined with a routine version bump.
   - Files: `docs/how-to/upgrade-terreno.md` (new), `docs/how-to/README.md`
   - Depends on: Task 2.1
@@ -53,31 +53,31 @@ See: [`docs/implementationPlans/upgrade-guides-and-skill.md`](../implementationP
 
 ## Phase 3: The skill
 
-- [ ] **Task 3.1**: Author the `upgrading-terreno` skill
+- [x] **Task 3.1**: Author the `upgrading-terreno` skill
   - Description: Create `.rulesync/skills/upgrading-terreno/SKILL.md`. Frontmatter: `name: upgrading-terreno`, a `description` naming trigger phrases ("upgrade Terreno", "bump @terreno packages", "update to the latest Terreno", "upgrade terreno version"), `targets: ['*']`. Body: Preconditions (clean git tree — refuse to start otherwise; on a branch, not the default branch; tests currently passing so failures are attributable); Determine versions (`application_info` from the local MCP server, or read `package.json` files); Fetch notes (`terreno_get_upgrade_guide`); **Plan and confirm** — print current version, target version, the notes found, the packages affected, and the ordered steps, then stop for confirmation; then the ten-step ordering from the IP with a verification gate between each phase; Expo delegation (invoke the `upgrading-expo` skill at step 6 rather than duplicating it); Failure handling (report what succeeded, what failed, and the rollback command; on a multi-version jump failure, retry version by version to isolate); and a final report. Include an explicit prohibition on continuing past a failed compile or test run.
   - Files: `.rulesync/skills/upgrading-terreno/SKILL.md` (new)
   - Depends on: Task 2.2
   - Acceptance: the clean-tree precondition is a hard refusal, not a warning; the confirmation gate precedes the first mutation; step 6 invokes `upgrading-expo` by name; the failure path names a rollback command; the ordering matches the how-to guide exactly.
 
-- [ ] **Task 3.2**: Add the ordering reference
+- [x] **Task 3.2**: Add the ordering reference
   - Description: Create `.rulesync/skills/upgrading-terreno/references/ordering.md` containing the dependency reasoning in detail: why backend precedes frontend, why the typed client is regenerated only after the backend is upgraded and running, why Expo precedes `@terreno/ui`, which packages are backend versus frontend (enumerate them from `publish-on-tag.yml`), and what breaks if the order is violated — with the specific symptom for each violation (for example: regenerating the client against an old backend produces a client missing the new routes, which fails at compile time in the consumer's screens).
   - Files: `.rulesync/skills/upgrading-terreno/references/ordering.md` (new)
   - Depends on: Task 3.1
   - Acceptance: every package is classified backend or frontend and the list matches `publish-on-tag.yml`; each ordering rule has a concrete violation symptom.
 
-- [ ] **Task 3.3**: `[RTK]` Add the syncdb migration branch
+- [x] **Task 3.3**: `[RTK]` Add the syncdb migration branch
   - Description: Add a section to the skill for the case where the upgrade range crosses the syncdb release. The skill must detect this (the range includes the syncdb version), stop, and tell the user that this is a platform migration rather than a version bump, pointing at `docs/how-to/migrate-rtk-to-syncdb.md` and offering to perform the routine version bump first and the migration as a separate operation. Do not attempt to automate the full migration inside a version-bump flow.
   - Files: `.rulesync/skills/upgrading-terreno/SKILL.md`
   - Depends on: Task 3.1, `rtk-to-syncdb-migration-docs` Phase 3
   - Acceptance: the skill detects a range crossing the syncdb version and stops with the two-option choice; it does not attempt the data-layer migration automatically.
 
-- [ ] **Task 3.4**: Wire the MCP prompt to the skill
+- [x] **Task 3.4**: Wire the MCP prompt to the skill
   - Description: Update the `terreno_upgrade` prompt in `mcp-server/src/prompts.ts` so it points at the `upgrading-terreno` skill as the executor, keeping the prompt as the discovery surface for agents without skill support. Ensure the prompt's ordering matches the skill's exactly so the two cannot drift into disagreement — ideally the prompt references the ordering rather than restating it.
   - Files: `mcp-server/src/prompts.ts`
   - Depends on: Task 3.1
   - Acceptance: the prompt names the skill; the two do not state conflicting orderings; `bun run mcp:build` succeeds.
 
-- [ ] **Task 3.5**: Generate skill mirrors
+- [x] **Task 3.5**: Generate skill mirrors
   - Description: Run `bun run rules` and commit all generated files.
   - Files: generated skill mirrors
   - Depends on: Task 3.1, Task 3.2, Task 3.3
@@ -85,19 +85,19 @@ See: [`docs/implementationPlans/upgrade-guides-and-skill.md`](../implementationP
 
 ## Phase 4: Enforcement
 
-- [ ] **Task 4.1**: Require upgrade notes in the release skill
+- [x] **Task 4.1**: Require upgrade notes in the release skill
   - Description: Add a required step to `.rulesync/skills/release/SKILL.md`: after assembling the changelog section for the release, if it contains a `Breaking`, `Deprecated`, `Removed`, or `Changed` entry, write `mcp-server/src/docs/upgrades/<version>.md` using the template from Task 1.1 before tagging. Reference the note from the changelog section. Regenerate mirrors.
   - Files: `.rulesync/skills/release/SKILL.md`, generated mirrors
   - Depends on: Task 1.1
   - Acceptance: the step lists the four triggering changelog headings; `bun run rules:check` exits 0.
 
-- [ ] **Task 4.2**: Add the CI enforcement check
+- [x] **Task 4.2**: Add the CI enforcement check
   - Description: Add a check (script plus a job in `.github/workflows/repo-policies.yml`, or a step in `publish-on-tag.yml` that runs before publishing) that reads the changelog section for the tag being released and fails if it contains a breaking/deprecated/removed/changed entry while `mcp-server/src/docs/upgrades/<version>.md` does not exist. Write it as a Bun TypeScript script with `const` arrow functions and explicit return types, following the repo's script conventions. Include tests for: note present and required, note missing and required, note not required.
   - Files: `scripts/check-upgrade-notes.ts` (new), `package.json`, `.github/workflows/repo-policies.yml` or `.github/workflows/publish-on-tag.yml`, tests
   - Depends on: Task 4.1
   - Acceptance: all three test cases pass; the check fails a simulated release with a breaking changelog entry and no note; `bun run lint` passes.
 
-- [ ] **Task 4.3**: Link notes from the changelog
+- [x] **Task 4.3**: Link notes from the changelog
   - Description: Update `CHANGELOG.md` so each version section with an upgrade note links it. Add a line to the changelog header explaining that upgrade notes live in `mcp-server/src/docs/upgrades/` and are also available through the MCP server's `terreno_get_upgrade_guide` tool.
   - Files: `CHANGELOG.md`
   - Depends on: Task 1.3
@@ -105,13 +105,13 @@ See: [`docs/implementationPlans/upgrade-guides-and-skill.md`](../implementationP
 
 ## Phase 5: Validation
 
-- [ ] **Task 5.1**: Perform a real multi-version upgrade with the skill
+- [x] **Task 5.1**: Perform a real multi-version upgrade with the skill
   - Description: Create a consumer app pinned to an older Terreno version (at least two minors behind current — scaffold with `terreno_bootstrap_app` from that version, or check out `example-frontend`/`example-backend` at the older tag into a scratch directory). Run the `upgrading-terreno` skill to bring it to current. Verify: the clean-tree precondition fires when the tree is dirty, the confirmation gate fires, each phase's verification runs, and the app compiles and runs afterward. Record every gap and fix the skill, the notes, or the how-to as appropriate. Capture the transcript and the running upgraded app to `/opt/cursor/artifacts/`.
   - Files: `.rulesync/skills/upgrading-terreno/SKILL.md`, `mcp-server/src/docs/upgrades/*`, `docs/how-to/upgrade-terreno.md`, generated mirrors
   - Depends on: Task 3.5, Task 1.3
   - Acceptance: the upgrade succeeds and the app runs; both gates observed firing; every gap fixed; artifacts captured; `bun run rules:check` exits 0.
 
-- [ ] **Task 5.2**: Verify the failure-isolation path
+- [x] **Task 5.2**: Verify the failure-isolation path
   - Description: Deliberately create a failing upgrade (for example by pinning a consumer file to an API removed in the range) and confirm the skill stops at the failing phase, names it, reports what succeeded, offers rollback, and — for a multi-version range — retries version by version to isolate the breaking version. Fix the skill if any of those behaviors is missing.
   - Files: `.rulesync/skills/upgrading-terreno/SKILL.md`, generated mirrors
   - Depends on: Task 5.1

package/dist/docs/versioned/next/tutorials/README.md

@@ -4,4 +4,4 @@ Learning-oriented, hands-on lessons. Start here if you are new to Terreno.
 
 ## Contents
 
-- [Getting started](getting-started.md) — Install, run the examples, and see the stack in action
+- [Getting started](getting-started.md) — Scaffold a new app with `create-terreno-app`, run it locally, or explore monorepo examples