@terreno/mcp 57.15.0 → 57.16.2

package/src/docs/versioned/57.15.0/explanation/roadmap-seed-issues.md

@@ -0,0 +1,1382 @@
+# Roadmap seed issues
+
+Ready-to-paste GitHub issue bodies for IPs on the public roadmap — the
+[OSS launch program](https://github.com/TerrenoLabs/terreno/blob/master/docs/implementationPlans/oss-launch-program.md) IPs plus other
+roadmap-tracked work. Open one tracking issue per IP when the IP reaches **Approved**, then
+add it to the **Terreno Roadmap** project with the field values below.
+
+Every entry also gets the `roadmap` label — `bun run roadmap:sync` adds it, so it is not
+repeated on the `**Labels:**` lines. That label is how roadmap items are filtered
+(`gh issue list --label roadmap`, or `label:roadmap` in the GitHub UI); titles carry no
+`[Roadmap]` prefix.
+
+---
+
+## oss-governance-baseline
+
+**Title:** `OSS governance baseline`
+
+**Labels:** `area:dx`, `type:chore`  
+**Project fields:** Area=`dx`, Target=`Released`, Impact=`Improvement`, IP=`oss-governance-baseline`, Status=`Shipped`
+
+Establishes the legal and community foundation required before Terreno can launch as a public
+open-source project. It adds a root MIT license, contribution and security policies, a
+changelog, GitHub community health files, and CI checks so every published npm package ships
+with correct licensing. Without this work, the repository cannot credibly invite outside
+contributors or consumers.
+
+- **Implementation plan:** [oss-governance-baseline.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/implementationPlans/oss-governance-baseline.md)
+- **Tasks:** [oss-governance-baseline.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/tasks/oss-governance-baseline.md)
+- **RTK flag:** None
+- **Depends on:** —
+
+---
+
+## public-roadmap-github
+
+**Title:** `Public roadmap on GitHub`
+
+**Labels:** `area:dx`, `type:feature`  
+**Project fields:** Area=`dx`, Target=`Released`, Impact=`Improvement`, IP=`public-roadmap-github`, Status=`Shipped`
+
+Runs Terreno's public roadmap on GitHub while keeping Linear as the internal execution
+tracker. It sets up GitHub Discussions categories, a Terreno Roadmap project board, label
+taxonomy, automated ROADMAP.md generation, and a one-way GitHub-to-Linear bridge for tracked
+issues. Outside contributors can see priorities and propose work without maintainers
+duplicating sprint planning.
+
+- **Implementation plan:** [public-roadmap-github.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/implementationPlans/public-roadmap-github.md)
+- **Tasks:** [public-roadmap-github.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/tasks/public-roadmap-github.md)
+- **RTK flag:** None
+- **Depends on:** oss-governance-baseline
+
+---
+
+## deploy-to-gcp
+
+**Title:** `Deploy to GCP (generalized)`
+
+**Labels:** `area:deploy`, `type:docs`  
+**Project fields:** Area=`deploy`, Target=`Next`, Impact=`Improvement`, IP=`deploy-to-gcp`, Status=`Planned`
+
+Turns Terreno's GCP deployment story from Flourish-specific infrastructure into a reusable
+guide any Terreno app can follow. It documents Cloud Run backend hosting, GCS plus CDN for
+static web export, a reusable Terraform module, parameterized scripts, and a deploy-gcp
+agent skill with confirmation gates. The guide covers websocket, replica-set, and
+session-affinity constraints that commonly break production Terreno deployments.
+
+- **Implementation plan:** [deploy-to-gcp.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/implementationPlans/deploy-to-gcp.md)
+- **Tasks:** [deploy-to-gcp.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/tasks/deploy-to-gcp.md)
+- **RTK flag:** None
+- **Depends on:** deployment-foundation
+
+---
+
+## agentic-sdlc-plugin
+
+**Title:** `Agentic SDLC plugin (/terreno-*)`
+
+**Labels:** `area:dx`, `type:feature`  
+**Project fields:** Area=`dx`, Target=`Released`, Impact=`Feature`, IP=`agentic-sdlc-plugin`, Status=`Shipped`
+
+Packages and documents Terreno's five-stage `/terreno-*` agentic SDLC pipeline as a portable,
+publicly installable Cursor plugin. The pipeline takes work from a raw request through
+planning, test-driven implementation, independent verification, submission with evidence,
+and a review loop until mergeable. Today the tooling exists inside the monorepo but is
+invisible and breaks in consumer apps.
+
+- **Implementation plan:** [agentic-sdlc-plugin.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/implementationPlans/agentic-sdlc-plugin.md)
+- **Tasks:** [agentic-sdlc-plugin.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/tasks/agentic-sdlc-plugin.md)
+- **RTK flag:** Partial
+- **Depends on:** positioning-django-rails-universal, oss-governance-baseline
+
+---
+
+## rtk-to-syncdb-migration-docs
+
+**Title:** `RTK deprecation and syncdb migration docs`
+
+**Labels:** `area:syncdb`, `type:docs`, `deprecation`, `status:blocked`  
+**Project fields:** Area=`syncdb`, Target=`Released`, Impact=`Improvement`, IP=`rtk-to-syncdb-migration-docs`, Status=`Shipped`
+
+> Blocked on PR #869. The Project **Status** field has no `Blocked` option, so gating is
+> tracked with the `status:blocked` issue label instead.
+
+Makes Better Auth plus `@terreno/syncdb` the documented, supported frontend platform and gives
+RTK Query consumers a tested migration path. It covers deprecation policy, a step-by-step
+migration guide, syncdb reference docs, auth repositioning, and updates to agent rules, MCP
+bootstrap output, and upgrade notes. Gates most Wave 1 launch documentation.
+
+- **Implementation plan:** [rtk-to-syncdb-migration-docs.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/implementationPlans/rtk-to-syncdb-migration-docs.md)
+- **Tasks:** [rtk-to-syncdb-migration-docs.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/tasks/rtk-to-syncdb-migration-docs.md)
+- **RTK flag:** Blocked (PR #869)
+- **Depends on:** PR #869
+
+---
+
+## positioning-django-rails-universal
+
+**Title:** `Positioning — Django/Rails for TypeScript`
+
+**Labels:** `area:docs`, `type:docs`  
+**Project fields:** Area=`docs`, Target=`Released`, Impact=`Improvement`, IP=`positioning-django-rails-universal`, Status=`Shipped`
+
+Aligns Terreno's messaging across README, docs site, agent context files, and npm package
+metadata under one positioning statement: Django/Rails for TypeScript with universal app
+support, organized around batteries included, universal by default, and AI-native pillars.
+
+- **Implementation plan:** [positioning-django-rails-universal.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/implementationPlans/positioning-django-rails-universal.md)
+- **Tasks:** [positioning-django-rails-universal.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/tasks/positioning-django-rails-universal.md)
+- **RTK flag:** Partial
+- **Depends on:** rtk-to-syncdb-migration-docs
+
+---
+
+## docs-reference-coverage
+
+**Title:** `Reference documentation coverage`
+
+**Labels:** `area:docs`, `type:docs`  
+**Project fields:** Area=`docs`, Target=`Released`, Impact=`Improvement`, IP=`docs-reference-coverage`, Status=`Shipped`
+
+Gives every published Terreno package a real README and a public docs/reference page instead
+of stubs. Adds missing reference pages, de-stubs package READMEs, sanitizes internal
+leakage, and extends docs-audit CI to catch drift.
+
+- **Implementation plan:** [docs-reference-coverage.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/implementationPlans/docs-reference-coverage.md)
+- **Tasks:** [docs-reference-coverage.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/tasks/docs-reference-coverage.md)
+- **RTK flag:** Blocked
+- **Depends on:** rtk-to-syncdb-migration-docs, positioning-django-rails-universal
+
+---
+
+## docs-tutorials-ai-first
+
+**Title:** `AI-first tutorials`
+
+**Labels:** `area:docs`, `type:docs`  
+**Project fields:** Area=`docs`, Target=`Next`, Impact=`Feature`, IP=`docs-tutorials-ai-first`, Status=`Planned`
+
+Replaces Terreno's thin getting-started page with a full tutorial path where the
+AI-assisted workflow is the default. Six tutorials cover examples, first app, MCP, AI
+features, admin panel, and production deploy — all on syncdb + Better Auth.
+
+- **Implementation plan:** [docs-tutorials-ai-first.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/implementationPlans/docs-tutorials-ai-first.md)
+- **Tasks:** [docs-tutorials-ai-first.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/tasks/docs-tutorials-ai-first.md)
+- **RTK flag:** Blocked
+- **Depends on:** docs-reference-coverage, ai-dev-loop-boost, deployment-foundation
+
+---
+
+## deployment-foundation
+
+**Title:** `Deployment foundation`
+
+**Labels:** `area:deploy`, `type:docs`  
+**Project fields:** Area=`deploy`, Target=`Released`, Impact=`Improvement`, IP=`deployment-foundation`, Status=`Shipped`
+
+Defines the provider-agnostic deployment baseline every Terreno production app needs: core
+requirements, environment-variable reference, Expo web output modes, and a canonical
+example-backend Dockerfile with CI validation.
+
+- **Implementation plan:** [deployment-foundation.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/implementationPlans/deployment-foundation.md)
+- **Tasks:** [deployment-foundation.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/tasks/deployment-foundation.md)
+- **RTK flag:** Partial
+- **Depends on:** —
+
+---
+
+## deploy-to-vercel
+
+**Title:** `Deploy to Vercel`
+
+**Labels:** `area:deploy`, `type:docs`  
+**Project fields:** Area=`deploy`, Target=`Next`, Impact=`Improvement`, IP=`deploy-to-vercel`, Status=`Planned`
+
+Documents Expo web export on Vercel, preview-deployment CORS and Better Auth origin handling,
+Vercel Functions WebSockets (Public Beta) operator docs, and a deploy-vercel skill with
+websocket verification. Requires a spike on backend hosting options.
+
+- **Implementation plan:** [deploy-to-vercel.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/implementationPlans/deploy-to-vercel.md)
+- **Tasks:** [deploy-to-vercel.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/tasks/deploy-to-vercel.md)
+- **RTK flag:** Partial
+- **Depends on:** deployment-foundation
+
+---
+
+## upgrade-guides-and-skill
+
+**Title:** `Upgrade guides and upgrading-terreno skill`
+
+**Labels:** `area:mcp`, `type:docs`  
+**Project fields:** Area=`mcp`, Target=`Released`, Impact=`Improvement`, IP=`upgrade-guides-and-skill`, Status=`Shipped`
+
+Makes upgrading Terreno across lockstep-published packages a documented, repeatable process.
+Backfills upgrade notes, adds versioning policy, ships an upgrading-terreno skill, and
+enforces upgrade-note requirements in release CI.
+
+- **Implementation plan:** [upgrade-guides-and-skill.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/implementationPlans/upgrade-guides-and-skill.md)
+- **Tasks:** [upgrade-guides-and-skill.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/tasks/upgrade-guides-and-skill.md)
+- **RTK flag:** Blocked
+- **Depends on:** rtk-to-syncdb-migration-docs, oss-governance-baseline
+
+---
+
+## ai-dev-loop-boost
+
+**Title:** `AI development loop (MCP Boost)`
+
+**Labels:** `area:mcp`, `type:feature`  
+**Project fields:** Area=`mcp`, Target=`Next`, Impact=`Feature`, IP=`ai-dev-loop-boost`, Status=`Planned`
+
+Documents Terreno's AI-native development loop: search docs, generate code, run the app,
+observe merged logs and client state, then fix and iterate. Builds on MCP Boost parity (PR
+#802).
+
+- **Implementation plan:** [ai-dev-loop-boost.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/implementationPlans/ai-dev-loop-boost.md)
+- **Tasks:** [ai-dev-loop-boost.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/tasks/ai-dev-loop-boost.md)
+- **RTK flag:** Partial
+- **Depends on:** PR #802
+
+---
+
+## build-terreno-app-validation
+
+**Title:** `Dogfooding run and launch blog post`
+
+**Labels:** `area:docs`, `type:chore`  
+**Project fields:** Area=`docs`, Target=`Next`, Impact=`Improvement`, IP=`build-terreno-app-validation`, Status=`Planned`
+
+Executes the OSS launch acceptance test: an agent builds and deploys a real universal app
+using only public docs and skills, then publishes a friction log and blog post.
+
+- **Implementation plan:** [build-terreno-app-validation.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/implementationPlans/build-terreno-app-validation.md)
+- **Tasks:** [build-terreno-app-validation.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/tasks/build-terreno-app-validation.md)
+- **RTK flag:** Blocked
+- **Depends on:** docs-tutorials-ai-first, ai-dev-loop-boost, deploy-to-vercel, docs-reference-coverage
+
+---
+
+## examples-demo-coverage
+
+**Title:** `Examples, demo, and test coverage`
+
+**Labels:** `area:examples`, `type:chore`  
+**Project fields:** Area=`examples`, Target=`Released`, Impact=`Improvement`, IP=`examples-demo-coverage`, Status=`Shipped`
+
+Closes credibility gaps in examples, the UI demo app, and CI coverage gates. Adds missing demo
+stories, extends coverage enforcement, and publishes an example-app feature matrix.
+
+- **Implementation plan:** [examples-demo-coverage.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/implementationPlans/examples-demo-coverage.md)
+- **Tasks:** [examples-demo-coverage.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/tasks/examples-demo-coverage.md)
+- **RTK flag:** Partial
+- **Depends on:** docs-reference-coverage
+
+---
+
+## web-ssr-and-admin-spa
+
+**Title:** `Web SSR and admin SPA`
+
+**Labels:** `area:ui`, `type:feature`  
+**Project fields:** Area=`ui`, Target=`Future`, Impact=`Feature`, IP=`web-ssr-and-admin-spa`, Status=`Planned`
+
+Adds real server-side rendering for Terreno web apps so routes can be indexed and paint
+meaningful HTML before JavaScript loads. Starts with static output and admin-spa as proving
+ground; SSR is opt-in and depends on Expo SDK 55+.
+
+- **Implementation plan:** [web-ssr-and-admin-spa.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/implementationPlans/web-ssr-and-admin-spa.md)
+- **Tasks:** [web-ssr-and-admin-spa.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/tasks/web-ssr-and-admin-spa.md)
+- **RTK flag:** Partial
+- **Depends on:** Expo SDK ≥ 55 (PR #779), deployment-foundation
+
+---
+
+## infra-mcp
+
+*Outside the OSS launch program.*
+
+**Title:** `Infrastructure MCP server (@terreno/infra-mcp)`
+
+**Labels:** `area:mcp`, `type:feature`, `status:blocked`  
+**Project fields:** Area=`mcp`, Target=`Future`, Impact=`Feature`, IP=`infra-mcp`, Status=`Planned`
+
+> Blocked on the RBAC permissions module. The Project **Status** field has no `Blocked`
+> option, so gating is tracked with the `status:blocked` issue label instead.
+
+Puts privileged infrastructure tooling — GCP, Sentry, MongoDB, and later Expo/EAS and Vercel —
+behind one deployable MCP server with per-user OAuth 2.1 authentication, RBAC-driven read and
+write tiers, per-call confirmation on write tools, and an audit trail. Read-only access covers
+log digging without handing anyone production credentials, and the server runs on its own Cloud
+Run runtime service account so injected service-account keys can be retired.
+
+- **Implementation plan:** [infra-mcp.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/implementationPlans/infra-mcp.md)
+- **Tasks:** [infra-mcp.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/tasks/infra-mcp.md)
+- **RTK flag:** None
+- **Depends on:** rbac-permissions
+
+---
+
+# B2B platform program
+
+Ready-to-paste GitHub issue bodies for the
+[B2B platform program](https://github.com/TerrenoLabs/terreno/blob/master/docs/implementationPlans/b2b-platform-program.md).
+Items marked *(IP pending)* are drafted ahead of their IP by maintainer decision; open the
+issue with `Status=Planned` and fill the IP field when the IP lands.
+
+---
+
+## comms-abstraction
+
+**Title:** `Pluggable communications layer (@terreno/comms)`
+
+**Labels:** `area:api`, `type:feature`
+**Project fields:** Area=`api`, Target=`Released`, Impact=`Feature`, IP=`comms-abstraction`, Status=`Shipped`
+
+Terreno backends have no way to send email, SMS, or push notifications today. This adds a
+new `@terreno/comms` package with provider interfaces for mail, SMS, push, and OTP
+verification, a `CommsApp` plugin that registers them on a Terreno app, push-token
+registration routes, a delivery log model, and console adapters for local development.
+Concrete providers (Twilio, SendGrid, Expo push) ship as separate adapters, each with its own
+roadmap item, so apps only install the SDKs they use.
+
+- **Implementation plan:** [comms-abstraction.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/implementationPlans/comms-abstraction.md)
+- **Tasks:** [comms-abstraction.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/tasks/comms-abstraction.md)
+- **RTK flag:** None
+- **Depends on:** —
+
+---
+
+## comms-adapter-expo-push
+
+**Title:** `Comms adapter — Expo push notifications`
+
+**Labels:** `area:api`, `type:feature`
+**Project fields:** Area=`api`, Target=`Released`, Impact=`Feature`, IP=`comms-adapter-expo-push`, Status=`Shipped`
+
+Implements the `@terreno/comms` push provider on Expo's push service using
+`expo-server-sdk` (already a dependency of `@terreno/api`, currently unused). Covers token
+chunking, receipt polling, and automatic deactivation of dead device tokens. The client
+half — `getExpoPushTokenAsync` registration — already exists in example-frontend.
+
+- **Implementation plan:** [comms-adapter-expo-push.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/implementationPlans/comms-adapter-expo-push.md)
+- **Tasks:** [comms-adapter-expo-push.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/tasks/comms-adapter-expo-push.md)
+- **RTK flag:** None
+- **Depends on:** comms-abstraction
+
+---
+
+## comms-adapter-twilio-sms
+
+**Title:** `Comms adapter — Twilio SMS`
+
+**Labels:** `area:api`, `type:feature`
+**Project fields:** Area=`api`, Target=`Next`, Impact=`Feature`, IP=`comms-adapter-twilio-sms`, Status=`In progress`
+
+Implements the `@terreno/comms` SMS provider on Twilio Programmable Messaging: send via
+messaging service or from-number, delivery status callbacks through the inbound-webhook
+framework, and E.164 validation using the `libphonenumber-js` dependency already in the
+catalog.
+
+- **Implementation plan:** [comms-adapter-twilio-sms.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/implementationPlans/comms-adapter-twilio-sms.md)
+- **Tasks:** [comms-adapter-twilio-sms.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/tasks/comms-adapter-twilio-sms.md)
+- **RTK flag:** None
+- **Depends on:** comms-abstraction; inbound-webhooks (status callbacks phase only)
+
+---
+
+## comms-adapter-twilio-verify
+
+**Title:** `Comms adapter — Twilio Verify (OTP)`
+
+**Labels:** `area:api`, `type:feature`
+**Project fields:** Area=`api`, Target=`Released`, Impact=`Feature`, IP=`comms-adapter-twilio-verify`, Status=`Shipped`
+
+Implements the `@terreno/comms` verification provider on Twilio Verify for SMS and email
+one-time codes. This is the delivery channel for phone verification and for the future MFA
+step-up work, without Terreno storing or rate-limiting codes itself.
+
+- **Implementation plan:** [comms-adapter-twilio-verify.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/implementationPlans/comms-adapter-twilio-verify.md)
+- **Tasks:** [comms-adapter-twilio-verify.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/tasks/comms-adapter-twilio-verify.md)
+- **RTK flag:** None
+- **Depends on:** comms-abstraction
+
+---
+
+## comms-adapter-sendgrid
+
+**Title:** `Comms adapter — transactional email (SendGrid)`
+
+**Labels:** `area:api`, `type:feature`
+**Project fields:** Area=`api`, Target=`Next`, Impact=`Feature`, IP=`comms-adapter-sendgrid`, Status=`In progress`
+
+Implements the first `@terreno/comms` mail provider on Twilio SendGrid so Terreno apps can
+send transactional email (password resets, invitations, verification), sharing the Twilio
+account story with the SMS and Verify adapters (decision D2). Other providers (Resend,
+SES, SMTP) get their own items when demand appears.
+
+- **Implementation plan:** [comms-adapter-sendgrid.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/implementationPlans/comms-adapter-sendgrid.md)
+- **Tasks:** [comms-adapter-sendgrid.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/tasks/comms-adapter-sendgrid.md)
+- **RTK flag:** None
+- **Depends on:** comms-abstraction
+
+---
+
+## comms-admin-dashboard
+
+**Title:** `Comms admin dashboard (errors, retries, log digging)`
+
+**Labels:** `area:admin`, `type:feature`
+**Project fields:** Area=`admin`, Target=`Released`, Impact=`Feature`, IP=`comms-admin-dashboard`, Status=`Shipped`
+
+Makes the admin panel the operations surface for the `@terreno/comms` layer: filterable
+delivery logs (channel, provider, status, error code/class, recipient, date range, free
+text), a message detail view with per-attempt history and raw provider metadata for log
+digging, one-click and bulk retry of failed sends, and a stats endpoint for failure-rate
+cards. Builds on the error taxonomy, lifecycle hooks, and payload retention added to the
+comms abstraction.
+
+- **Implementation plan:** [comms-admin-dashboard.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/implementationPlans/comms-admin-dashboard.md)
+- **Tasks:** [comms-admin-dashboard.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/tasks/comms-admin-dashboard.md)
+- **RTK flag:** Partial — screens use the generated SDK; migrate with syncdb like other admin screens
+- **Depends on:** comms-abstraction
+
+---
+
+## password-reset-and-email-verification
+
+**Title:** `Password reset and email verification`
+
+**Labels:** `area:auth`, `type:feature`
+**Project fields:** Area=`auth`, Target=`Released`, Impact=`Feature`, IP=`password-reset-and-email-verification`, Status=`Shipped`
+
+Closes a functional hole: the `@terreno/rtk` client already exposes a `resetPassword`
+endpoint but no backend route implements it, and there is no email verification flow.
+Adds token-issuing reset and verification routes to the JWT auth path, wires Better Auth's
+equivalents, and sends the emails through `@terreno/comms`.
+
+- **Implementation plan:** [password-reset-and-email-verification.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/implementationPlans/password-reset-and-email-verification.md)
+- **Tasks:** [password-reset-and-email-verification.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/tasks/password-reset-and-email-verification.md)
+- **RTK flag:** None
+- **Depends on:** comms-abstraction, comms-adapter-sendgrid
+
+---
+
+## inbound-webhooks
+
+**Title:** `Inbound webhook framework`
+
+**Labels:** `area:api`, `type:feature`
+**Project fields:** Area=`api`, Target=`Released`, Impact=`Feature`, IP=`inbound-webhooks`, Status=`Shipped`
+
+**GitHub:** https://github.com/TerrenoLabs/terreno/issues/1172
+
+Terreno has outbound notifiers (Slack, Google Chat, Zoom) but no framework for receiving
+webhooks from external services. Adds a plugin for registering webhook endpoints with
+signature verification, raw-body handling, idempotency/replay protection, and event
+dispatch — required by Stripe billing and by Twilio/SendGrid delivery status callbacks
+(Expo push polls receipts and does not use this plugin).
+
+- **Implementation plan:** [inbound-webhooks.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/implementationPlans/inbound-webhooks.md)
+- **Tasks:** [inbound-webhooks.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/tasks/inbound-webhooks.md)
+- **RTK flag:** None
+- **Depends on:** —
+
+---
+
+## orgs-and-teams
+
+**Title:** `Organizations, teams, and multi-tenant scoping`
+
+**Labels:** `area:api`, `type:feature`
+**Project fields:** Area=`api`, Target=`Next`, Impact=`Feature`, IP=`orgs-and-teams`, Status=`Declined`
+
+Superseded by `org-management-ui` (native orgs + RBAC + admin UI). Do not open new work
+from this item.
+
+- **Implementation plan:** [orgs-and-teams.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/implementationPlans/orgs-and-teams.md) (superseded)
+- **Canonical IP:** [org-management-ui.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/implementationPlans/org-management-ui.md)
+- **Tasks:** [org-management-ui.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/tasks/org-management-ui.md)
+- **RTK flag:** None
+- **Depends on:** —
+
+---
+
+## rbac-permissions
+
+**Title:** `Role-based access control`
+
+**Labels:** `area:api`, `type:feature`
+**Project fields:** Area=`api`, Target=`Released`, Impact=`Feature`, IP=`rbac-permissions`, Status=`Shipped`
+
+Replaces the binary `admin` flag + owner checks with a first-class RBAC module: a typed
+permission vocabulary on Better Auth's access-control engine, DB-backed roles editable in
+the admin panel, document-level scopes, field-level views, and one `can()` check enforced
+across REST, websockets, MCP tools, and admin. An API design draft already exists;
+`org-management-ui` extends it with org-scoped membership grants (`org-admin` / `member`).
+
+- **Implementation plan:** [rbac-permissions.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/implementationPlans/rbac-permissions.md)
+- **Tasks:** *(TBD — design doc predates task split)*
+- **RTK flag:** None
+- **Depends on:** —
+
+---
+
+## invitations-and-seats
+
+**Title:** `Invitations and seat management`
+
+**Labels:** `area:api`, `type:feature`
+**Project fields:** Area=`api`, Target=`Next`, Impact=`Feature`, IP=*(not yet written)*, Status=`Planned`
+
+Lets an org admin invite teammates by email: invite tokens with expiry, accept/decline
+flows for existing and new users, role assignment on acceptance, and seat counting that
+billing can later enforce. Emails go through `@terreno/comms`.
+
+- **Implementation plan:** *(not yet written)*
+- **Tasks:** *(not yet written)*
+- **RTK flag:** None
+- **Depends on:** org-management-ui, comms-abstraction, comms-adapter-sendgrid
+
+---
+
+## org-management-ui
+
+**Title:** `Organizations as a first-class primitive (admin UI + RBAC)`
+
+**Labels:** `area:api`, `type:feature`
+**Project fields:** Area=`api`, Target=`Released`, Impact=`Feature`, IP=`org-management-ui`, Status=`Shipped`
+
+Native Organization and Membership models, RBAC (`org-admin`, `operator`, `superadmin`),
+and admin-panel directory / switcher / members / settings. Operators manage all orgs;
+org-admins manage only the current org. Invites and billing are design-only placeholders.
+
+- **Implementation plan:** [org-management-ui.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/implementationPlans/org-management-ui.md)
+- **Tasks:** [org-management-ui.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/tasks/org-management-ui.md)
+- **RTK flag:** Partial — custom non-synced routes use the generated SDK;
+  ObjectId admin compatibility may use `useAdminApi` in Terreno 57, while
+  eligible String-`_id` CRUD uses windowed syncdb
+- **Depends on:** rbac-permissions
+
+---
+
+## billing-stripe
+
+**Title:** `Stripe billing and subscriptions`
+
+**Labels:** `area:api`, `type:feature`
+**Project fields:** Area=`api`, Target=`Next`, Impact=`Feature`, IP=`billing-stripe`, Status=`Planned`
+
+Adds a billing plugin on Stripe (web-first, decision D1): customers mapped to
+organizations, subscription and plan models, checkout/portal session routes,
+webhook-driven entitlement sync, and plan gating that plugs into the existing feature-flag
+layer. Includes basic plan-picker and billing settings screens. Mobile in-app purchases
+are a separate item.
+
+- **Implementation plan:** [billing-stripe.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/implementationPlans/billing-stripe.md)
+- **Tasks:** [billing-stripe.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/tasks/billing-stripe.md)
+- **RTK flag:** None
+- **Depends on:** org-management-ui, inbound-webhooks
+
+---
+
+## native-module-baseline
+
+**Title:** `Native module baseline for the next major release`
+
+**Labels:** `area:ui`, `type:chore`, `breaking`
+**Project fields:** Area=`ui`, Target=`Next`, Impact=`Breaking`, IP=`native-module-baseline`, Status=`Shaping`
+
+Adding a native module to a Terreno app forces a new dev-client/store binary, so every
+native dependency the B2B program needs lands in one major release: Stripe payment sheet,
+RevenueCat purchases, `expo-device`, `expo-crypto`, `expo-local-authentication`,
+`expo-system-ui`, and `react-native-otp-verify`, plus config plugins and refreshed EAS
+builds. After this release, the rest of the program ships as JS/OTA updates against the
+same binary. Manifest finalized 2026-08-09 (decisions D1/D3/D7); TenTap excluded
+(markdown stays).
+
+- **Implementation plan:** [native-module-baseline.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/implementationPlans/native-module-baseline.md)
+- **Tasks:** [native-module-baseline.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/tasks/native-module-baseline.md)
+- **RTK flag:** None
+- **Depends on:** —
+
+---
+
+## create-terreno-app
+
+**Title:** `create-terreno-app scaffolding CLI`
+
+**Labels:** `area:dx`, `type:feature`
+**Project fields:** Area=`dx`, Target=`Next`, Impact=`Feature`, IP=`create-terreno-app`, Status=`In progress`
+
+Today the MCP bootstrap tool returns markdown instructions and writes no files. This ships
+a real `create-terreno-app` CLI (or template repo) that produces a running, deployable app
+— backend, Expo app, env files, seeded auth — in one command, with the MCP bootstrap
+delegating to it.
+
+- **Implementation plan:** [create-terreno-app.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/implementationPlans/create-terreno-app.md)
+- **Tasks:** [create-terreno-app.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/tasks/create-terreno-app.md)
+- **RTK flag:** Partial — scaffold output follows the syncdb + Better Auth direction
+- **Depends on:** deployment-foundation
+
+---
+
+## charts-and-dashboards
+
+**Title:** `Charts and dashboard primitives`
+
+**Labels:** `area:ui`, `type:feature`
+**Project fields:** Area=`ui`, Target=`Next`, Impact=`Feature`, IP=`charts-and-dashboards`, Status=`In progress`
+
+`@terreno/ui` ships themed `LineChart`, `BarChart`, `AreaChart`, `DonutChart` on owned
+`react-native-svg` (not `victory-native`) plus `DashboardGrid`. Demo stories and Diátaxis
+docs are the proof; comms admin stats consume these primitives later.
+
+- **Implementation plan:** [charts-and-dashboards.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/implementationPlans/charts-and-dashboards.md)
+- **Tasks:** [charts-and-dashboards.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/tasks/charts-and-dashboards.md)
+- **RTK flag:** None
+- **Depends on:** —
+
+---
+
+## dashboard-chart-parity
+
+**Title:** `Ops dashboard chart parity`
+
+**Labels:** `area:ui`, `type:feature`
+**Project fields:** Area=`ui`, Target=`Next`, Impact=`Feature`, IP=`dashboard-chart-parity`, Status=`Planned`
+
+Follow-up to charts-and-dashboards: scorecards with comparison sparklines, `ChartCard`
+period badges, additive multi-series facades, donut hole labels, spanning `DashboardGrid`
+items, and DataTable period headers / totals / range status so apps can compose a
+“How’s it going?”-class ops dashboard. Terreno theme defaults; no Looker preset. Grammar
+not required.
+
+- **Implementation plan:** [dashboard-chart-parity.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/implementationPlans/dashboard-chart-parity.md)
+- **Tasks:** [dashboard-chart-parity.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/tasks/dashboard-chart-parity.md)
+- **RTK flag:** None
+- **Depends on:** charts-and-dashboards
+
+---
+
+## dark-mode-theme
+
+**Title:** `First-class dark mode`
+
+**Labels:** `area:ui`, `type:feature`
+**Project fields:** Area=`ui`, Target=`Next`, Impact=`Feature`, IP=*(not yet written)*, Status=`Planned`
+
+The theming system has three layers but no built-in dark theme; the example app fakes one
+by swapping primitives behind a feature flag. Ships a maintained dark palette, a
+`colorScheme` API on `TerrenoProvider` (system/light/dark), and `expo-system-ui` wiring so
+root views and system chrome follow the scheme.
+
+- **Implementation plan:** *(not yet written)*
+- **Tasks:** *(not yet written)*
+- **RTK flag:** None
+- **Depends on:** native-module-baseline (`expo-system-ui`)
+
+---
+
+## data-grid-server-filters
+
+**Title:** `DataTable server-side filtering and search`
+
+**Labels:** `area:ui`, `type:feature`
+**Project fields:** Area=`ui`, Target=`Released`, Impact=`Feature`, IP=`datatable-server-side-filtering`, Status=`Shipped`
+
+DataTable sorts and paginates but has no filter UI. Adds per-column filter controls and a
+search box that emit modelRouter-compatible query params (`queryFields`, `$and`/`$or`), so
+list screens get server-side filtering without custom plumbing. Admin tables adopt it.
+
+- **Implementation plan:** [datatable-server-side-filtering.md](../implementationPlans/datatable-server-side-filtering.md)
+- **Tasks:** [datatable-server-side-filtering.md](../tasks/datatable-server-side-filtering.md)
+- **RTK flag:** Partial — query wiring examples depend on the frontend data layer
+- **Depends on:** —
+
+---
+
+## mobile-iap-revenuecat
+
+**Title:** `Mobile in-app purchases (RevenueCat)`
+
+**Labels:** `area:api`, `type:feature`
+**Project fields:** Area=`api`, Target=`Future`, Impact=`Feature`, IP=*(not yet written)*, Status=`Planned`
+
+Store-compliant mobile subscriptions via RevenueCat (`react-native-purchases`): entitlement
+sync into the billing models through webhooks, paywall UI, and unified entitlements with
+Stripe web billing (decision D1: web-first, mobile IAP later). The native SDK ships in the
+native module baseline regardless, so this lands as a JS/OTA feature when scheduled.
+
+- **Implementation plan:** *(not yet written)*
+- **Tasks:** *(not yet written)*
+- **RTK flag:** None
+- **Depends on:** billing-stripe, native-module-baseline, inbound-webhooks
+
+---
+
+## notification-center
+
+**Title:** `In-app notification center`
+
+**Labels:** `area:ui`, `type:feature`
+**Project fields:** Area=`ui`, Target=`Released`, Impact=`Feature`, IP=`notification-center` (Approved), Status=`Shipped`
+
+Adds a Notification model with per-user preferences, realtime delivery over the existing
+change-stream socket layer, and a bell/inbox UI in `@terreno/ui` with read/unread state —
+the in-app channel beside `@terreno/comms` mail/SMS/push.
+
+- **Implementation plan:** [notification-center.md](../implementationPlans/notification-center.md)
+- **Tasks:** [notification-center.md](../tasks/notification-center.md)
+- **RTK flag:** Partial — inbox screens target the syncdb data layer where available
+- **Depends on:** comms-abstraction
+
+---
+
+## command-palette
+
+**Title:** `Command palette (⌘K)`
+
+**Labels:** `area:ui`, `type:feature`
+**Project fields:** Area=`ui`, Target=`Future`, Impact=`Feature`, IP=*(not yet written)*, Status=`Planned`
+
+A themable ⌘K palette component for web (with a native fallback surface): registerable
+actions, navigation targets, and async search sources. Admin panel adopts it first.
+
+- **Implementation plan:** *(not yet written)*
+- **Tasks:** *(not yet written)*
+- **RTK flag:** None
+- **Depends on:** —
+
+---
+
+## wizard-stepper
+
+**Title:** `Generic multi-step wizard component`
+
+**Labels:** `area:ui`, `type:feature`
+**Project fields:** Area=`ui`, Target=`Future`, Impact=`Feature`, IP=*(not yet written)*, Status=`Planned`
+
+Extracts the multi-step patterns hand-rolled in signup and consent flows into a generic
+wizard/stepper: step state, validation gates, progress indicator, and per-step persistence
+— the building block for onboarding and setup flows.
+
+- **Implementation plan:** *(not yet written)*
+- **Tasks:** *(not yet written)*
+- **RTK flag:** None
+- **Depends on:** —
+
+---
+
+## wysiwyg-editor
+
+**Title:** `Rich text (WYSIWYG) editor`
+
+**Labels:** `area:ui`, `type:feature`
+**Project fields:** Area=`ui`, Target=`Future`, Impact=`Feature`, IP=*(not yet written)*, Status=`Planned`
+
+Terreno's rich text today is markdown-only (`MarkdownEditor`), and decision D3 keeps it
+that way for now. This item tracks a future adoption of a true WYSIWYG editor (candidate:
+TenTap, Tiptap-based). Because TenTap requires a native module that is **not** in the
+native module baseline, adopting it means waiting for a later major release.
+
+- **Implementation plan:** *(not yet written)*
+- **Tasks:** *(not yet written)*
+- **RTK flag:** None
+- **Depends on:** a future major release (native module not in the current baseline)
+
+---
+
+## global-search
+
+**Title:** `Global search across entities`
+
+**Labels:** `area:api`, `type:feature`
+**Project fields:** Area=`api`, Target=`Future`, Impact=`Feature`, IP=*(not yet written)*, Status=`Planned`
+
+A search framework for modelRouter models: per-model searchable-field registration, a
+cross-model search endpoint with permission-aware results, Mongo text/Atlas Search backends,
+and a search UI hook — feeding the command palette and app-level search bars.
+
+- **Implementation plan:** *(not yet written)*
+- **Tasks:** *(not yet written)*
+- **RTK flag:** None
+- **Depends on:** —
+
+---
+
+## enterprise-sso
+
+**Title:** `Enterprise SSO (SAML / OIDC)`
+
+**Labels:** `area:auth`, `type:feature`
+**Project fields:** Area=`auth`, Target=`Future`, Impact=`Feature`, IP=*(not yet written)*, Status=`Planned`
+
+Org-level single sign-on: SAML and OIDC via Better Auth's SSO tooling, per-organization
+IdP configuration, JIT user provisioning into org memberships, and domain-based login
+routing. The mobile flow uses `expo-auth-session` + `expo-crypto` (PKCE) from the native
+baseline.
+
+- **Implementation plan:** *(not yet written)*
+- **Tasks:** *(not yet written)*
+- **RTK flag:** None
+- **Depends on:** org-management-ui, native-module-baseline
+
+---
+
+## mfa-step-up-auth
+
+**Title:** `MFA and biometric step-up auth`
+
+**Labels:** `area:auth`, `type:feature`
+**Project fields:** Area=`auth`, Target=`Future`, Impact=`Feature`, IP=*(not yet written)*, Status=`Planned`
+
+Second-factor support: TOTP enrollment, SMS/email OTP via the Twilio Verify adapter, and
+biometric step-up on native (`expo-local-authentication`) for sensitive actions, with
+enforcement hooks in the permission layer.
+
+- **Implementation plan:** *(not yet written)*
+- **Tasks:** *(not yet written)*
+- **RTK flag:** None
+- **Depends on:** comms-adapter-twilio-verify, native-module-baseline
+
+---
+
+## framework-audit-log
+
+**Title:** `Framework-level audit log`
+
+**Labels:** `area:api`, `type:feature`
+**Project fields:** Area=`api`, Target=`Released`, Impact=`Feature`, IP=`framework-audit-log`, Status=`Shipped`
+
+Generalizes the admin/consent audit patterns into a first-class audit log: an AuditEvent
+model, modelRouter hooks that record who changed what (with before/after diffs), org
+scoping, retention policy, and an admin viewer — a hard requirement for compliance-minded
+B2B customers.
+
+Shipping this work **closes** https://github.com/TerrenoLabs/terreno/issues/1186.
+
+- **Implementation plan:** [framework-audit-log.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/implementationPlans/framework-audit-log.md)
+- **Tasks:** [framework-audit-log.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/tasks/framework-audit-log.md)
+- **How-to:** [audit-log.md](../how-to/audit-log.md)
+- **RTK flag:** None
+- **Depends on:** — (optional `organizationId` now; org-admin list filter waits on org-management-ui)
+
+---
+
+## rate-limiting
+
+**Title:** `API rate limiting`
+
+**Labels:** `area:api`, `type:feature`
+**Project fields:** Area=`api`, Target=`Released`, Impact=`Feature`, IP=`rate-limiting`, Status=`Shipped`
+
+Adds opt-in HTTP rate limiting to `@terreno/api`: per-user or per-IP keys, stricter
+auth/OTP buckets (including login), memory Redis or Mongo stores, and 429 rate-limit
+headers. Default is off until Terreno 58. Sync mutation nacks stay a separate limiter.
+
+Shipping this work **closes** https://github.com/TerrenoLabs/terreno/issues/1187.
+
+- **Implementation plan:** [rate-limiting.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/implementationPlans/rate-limiting.md)
+- **Tasks:** [rate-limiting.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/tasks/rate-limiting.md)
+- **How-to:** [rate-limiting.md](../how-to/rate-limiting.md)
+- **RTK flag:** None
+- **Depends on:** —
+
+---
+
+## job-queues
+
+**Title:** `Durable background jobs`
+
+**Labels:** `area:api`, `type:feature`
+**Project fields:** Area=`api`, Target=`Released`, Impact=`Feature`, IP=`job-queues`, Status=`Shipped`
+
+Adds `@terreno/jobs`: Mongo-recorded jobs with retries, schedules, dead-lettering, in-process or
+standalone workers, and pluggable runners (Mongo, GCP Cloud Tasks, Vercel Queues, custom).
+Email/webhook/billing consumers enqueue later; this item ships the queue.
+
+Shipping this work **closes** https://github.com/TerrenoLabs/terreno/issues/1188.
+
+- **Implementation plan:** [job-queues.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/implementationPlans/job-queues.md)
+- **Tasks:** [job-queues.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/tasks/job-queues.md)
+- **How-to:** [background-jobs.md](../how-to/background-jobs.md)
+- **Reference:** [jobs.md](../reference/jobs.md)
+- **RTK flag:** Partial — admin screens use generated SDK
+- **Depends on:** —
+
+---
+
+## mongo-migrations
+
+**Title:** `MongoDB migrations tooling`
+
+**Labels:** `area:api`, `type:feature`  
+**Project fields:** Area=`api`, Target=`Released`, Impact=`Feature`, IP=`mongodb-migrations-tooling`, Status=`Shipped`
+
+A migrations runner for Terreno apps: versioned migration files, up/down with a lock
+collection, CI checks, CLI generate-from-schema-diff, optional boot apply, and an admin
+Migrations page — replacing ad-hoc backfill scripts for once-per-environment schema changes.
+
+Shipping this work **closes** https://github.com/TerrenoLabs/terreno/issues/1189.
+
+- **Implementation plan:** [mongodb-migrations-tooling.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/implementationPlans/mongodb-migrations-tooling.md)
+- **Tasks:** [mongodb-migrations-tooling.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/tasks/mongodb-migrations-tooling.md)
+- **RTK flag:** None
+- **Depends on:** —
+
+---
+
+# API architecture
+
+Internal seams in `@terreno/api` that several roadmap items depend on. They ship no new
+product surface on their own; they remove the duplicated write, permission, registry, and
+schema-walking paths that every later API feature would otherwise have to fork.
+
+## unified-mutation-executors
+
+**Title:** `[Roadmap] Unified mutation executors (MCP to executors)`
+
+**Labels:** `area:api`, `type:chore`
+**Project fields:** Area=`api`, Target=`Released`, Impact=`Improvement`, IP=`unified-mutation-executors`, Status=`Shipped`
+
+Gives create, update, and delete a single write pipeline. REST and Sync already call
+`executeCreate` / `executeUpdate` / `executeDelete`; MCP's write handlers still run their own
+permissions, transformers, hooks, and saves. Pointing MCP at the shared executors means a
+permission, hook, field-view, or soft-delete fix lands once instead of twice.
+
+- **Implementation plan:** [unified-mutation-executors.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/implementationPlans/unified-mutation-executors.md)
+- **Tasks:** [unified-mutation-executors.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/tasks/unified-mutation-executors.md)
+- **RTK flag:** None
+- **Depends on:** —
+
+---
+
+## collection-registry
+
+**Title:** `[Roadmap] One collection registry`
+
+**Labels:** `area:api`, `type:chore`
+**Project fields:** Area=`api`, Target=`Released`, Impact=`Improvement`, IP=`collection-registry`, Status=`Shipped`
+
+Registers a `modelRouter` collection once. MCP, realtime, and Sync each keep a process-global
+array plus an `update*RegistryOptions` call today, so every RBAC or MCP change has to touch
+three registries. A single `CollectionRegistry` keyed by route path holds `{path, model,
+options, surfaces}` and the existing per-surface lookups become views over it.
+
+- **Implementation plan:** [collection-registry.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/implementationPlans/collection-registry.md)
+- **Tasks:** [collection-registry.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/tasks/collection-registry.md)
+- **RTK flag:** None
+- **Depends on:** unified-mutation-executors
+
+---
+
+## can-as-permission-seam
+
+**Title:** `[Roadmap] can() as the permission seam`
+
+**Labels:** `area:api`, `type:chore`
+**Project fields:** Area=`api`, Target=`Released`, Impact=`Improvement`, IP=`can-as-permission-seam`, Status=`Shipped`
+
+Finishes the RBAC work by making `accessControl.can()` the enforcement engine wherever a
+router declares `access`. Today RBAC roles and statements are compiled down into legacy
+`PermissionMethod[]` arrays and `checkPermissions` remains the real decision point, so apps
+must pass both `access` and `permissions` and the two can disagree.
+
+- **Implementation plan:** [can-as-permission-seam.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/implementationPlans/can-as-permission-seam.md)
+- **Tasks:** [can-as-permission-seam.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/tasks/can-as-permission-seam.md)
+- **RTK flag:** None
+- **Depends on:** unified-mutation-executors, rbac-permissions
+
+---
+
+## describe-model-schema
+
+**Title:** `[Roadmap] describeModel() schema metadata`
+
+**Labels:** `area:api`, `type:chore`
+**Project fields:** Area=`api`, Target=`Released`, Impact=`Improvement`, IP=`describe-model-schema`, Status=`Shipped`
+
+Walks each Mongoose schema once into a shared `ModelDescription`. OpenAPI generation, the
+admin field-widget extractor, and the MCP Zod tool generator each re-interpret `schema.paths`
+their own way today, so a field type that renders correctly in admin can still be wrong in
+MCP or the OpenAPI spec.
+
+- **Implementation plan:** [describe-model-schema.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/implementationPlans/describe-model-schema.md)
+- **Tasks:** [describe-model-schema.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/tasks/describe-model-schema.md)
+- **RTK flag:** None
+- **Depends on:** —
+
+---
+
+## pluggable-database-sqlite
+
+**Title:** `[Roadmap] Pluggable database layer and SQLite adapter`
+
+**Labels:** `area:api`, `type:feature`
+**Project fields:** Area=`api`, Target=`Future`, Impact=`Feature`, IP=`pluggable-database-sqlite`, Status=`Planned`
+
+Extracts a `DatabaseAdapter` seam under `modelRouter`, keeps Mongoose/MongoDB as the default
+adapter behind it with no behavior change, and ships a SQLite adapter (`@terreno/db-sqlite`)
+covering CRUD, permissions, population, OpenAPI, and admin. Apps keep authoring models as
+Mongoose schemas on either database; Mongo-only capabilities (change streams, Atlas search)
+stay gated behind capability flags.
+
+- **Implementation plan:** [pluggable-database-sqlite.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/implementationPlans/pluggable-database-sqlite.md)
+- **Tasks:** [pluggable-database-sqlite.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/tasks/pluggable-database-sqlite.md)
+- **RTK flag:** None
+- **Depends on:** describe-model-schema
+
+---
+
+## mcp-doc-sync-off-compile-path
+
+**Title:** `Move mcp-server doc-sync off the compile path`
+
+**Labels:** `area:dx`, `type:chore`  
+**Project fields:** Area=`dx`, Target=`Released`, Impact=`Improvement`, IP=`mcp-doc-sync-off-compile-path`, Status=`Shipped`
+
+Take the three doc-sync scripts and the `cp` off mcp-server's `compile` script so a normal `bun run compile` type-checks only. This removes ~5s of fixed I/O from every cold build and — critically — eliminates a Bun `cpSync` race in `sync-versioned-docs` that intermittently fails the full concurrent build (observed 1/3 runs once Slice B raises build concurrency).
+
+- **Implementation plan:** [mcp-doc-sync-off-compile-path.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/implementationPlans/mcp-doc-sync-off-compile-path.md)
+- **Tasks:** [mcp-doc-sync-off-compile-path.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/tasks/mcp-doc-sync-off-compile-path.md)
+
+---
+
+## admin-scripts-durable-jobs
+
+**Title:** `Admin scripts via durable jobs`
+
+**Labels:** `area:admin`, `type:chore`  
+**Project fields:** Area=`admin`, Target=`Released`, Impact=`Improvement`, IP=`admin-scripts-durable-jobs`, Status=`Shipped`
+
+Admin HTTP script runs (`POST /admin/scripts/:name/run`) enqueue `@terreno/jobs` job `admin/script` when `JobsApp` is registered, while the Scripts UI keeps polling `BackgroundTask` by `taskId`.
+
+- **Implementation plan:** [admin-scripts-durable-jobs.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/implementationPlans/admin-scripts-durable-jobs.md)
+- **Tasks:** [admin-scripts-durable-jobs.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/tasks/admin-scripts-durable-jobs.md)
+
+---
+
+## announcements
+
+**Title:** `Product Update Announcements — In-App Core Feature`
+
+**Labels:** `area:api`, `type:feature`  
+**Project fields:** Area=`api`, Target=`Released`, Impact=`Feature`, IP=`announcements`, Status=`Shipped`
+
+Ship a **core Terreno feature** for admin-managed, in-app product update announcements — similar in scope to feature flags and consent forms. Admins create markdown announcements with scheduling, targeting metadata, and lifecycle controls. Authenticated users see a **priority-ordered modal queue** (one at a time) and can browse a **changelog feed**. Consumers (e.g. Flourish) configure audience matching and acknowledgement policy without forking the package.
+
+- **Implementation plan:** [announcements.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/implementationPlans/announcements.md)
+- **Tasks:** [announcements.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/tasks/announcements.md)
+
+---
+
+## gpt-chat-mascot
+
+**Title:** `GPTChat optional mascot`
+
+**Labels:** `area:ui`, `type:feature`  
+**Project fields:** Area=`ui`, Target=`Released`, Impact=`Feature`, IP=`gpt-chat-mascot`, Status=`Shipped`
+
+Let consuming apps brand the GPT screen with their own mascot. Terreno does not ship a default character.
+
+- **Implementation plan:** [gpt-chat-mascot.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/implementationPlans/gpt-chat-mascot.md)
+- **Tasks:** [gpt-chat-mascot.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/tasks/gpt-chat-mascot.md)
+
+---
+
+## knip-cleanup
+
+**Title:** `Remove the Knip baseline`
+
+**Labels:** `area:dx`, `type:chore`  
+**Project fields:** Area=`dx`, Target=`Released`, Impact=`Improvement`, IP=`knip-cleanup`, Status=`Shipped`
+
+`bun run analyze:full` stays green and Knip has no baseline file. Every finding that existed on 2026-09-08 (~1076 fingerprints: 529 default + 547 production) is either **gone from the live Knip report** (fixed) or **declared in `knip.jsonc` with a one-line reason** (disabled).
+
+- **Implementation plan:** [knip-cleanup.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/implementationPlans/knip-cleanup.md)
+- **Tasks:** [knip-cleanup.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/tasks/knip-cleanup.md)
+
+---
+
+## agent-ui-blocks
+
+**Title:** `Agent UI Blocks — a strict YAML DSL for agent-rendered Terreno components`
+
+**Labels:** `area:ai`, `type:feature`  
+**Project fields:** Area=`ai`, Target=`Next`, Impact=`Feature`, IP=`agent-ui-blocks`, Status=`Planned`
+
+Let an agent answer with **components, not just prose**. When UI blocks are enabled for a chat, **every assistant reply is one YAML document**: a short, ordered list of **blocks** (heading, text, metric, chart, table, actions, columns, card, …) plus named **datasets** that charts and tables bind to. Prose is a `text` block. Terreno owns the grammar, the validator, and the renderer, so the agent can only ever produce `@terreno/ui` components painted from the app theme — never HTML, JSX, or hex colors.
+
+- **Implementation plan:** [agent-ui-blocks.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/implementationPlans/agent-ui-blocks.md)
+- **Tasks:** [agent-ui-blocks.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/tasks/agent-ui-blocks.md)
+
+---
+
+## app-mcp-server
+
+**Title:** `App MCP server`
+
+**Labels:** `area:mcp`, `type:feature`  
+**Project fields:** Area=`mcp`, Target=`Future`, Impact=`Feature`, IP=`app-mcp-server`, Status=`Shaping`
+
+A Terreno backend exposes a complete MCP product surface — tools, prompts, resources, named HTTP servers, OAuth 2.1 for remote clients, Inspector/test DX, a Streamable HTTP client, and hosted generators for those primitives — without giving up generated CRUD tools that stay aligned with `modelRouter` permissions.
+
+- **Implementation plan:** [app-mcp-server.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/implementationPlans/app-mcp-server.md)
+- **Tasks:** [app-mcp-server.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/tasks/app-mcp-server.md)
+
+---
+
+## migrate-admin-to-syncdb
+
+**Title:** `Migrate built-in admin to syncdb`
+
+**Labels:** `area:admin`, `type:chore`  
+**Project fields:** Area=`admin`, Target=`Released`, Impact=`Improvement`, IP=`migrate-admin-to-syncdb`, Status=`Shipped`
+
+Move **built-in admin model list/read/create/update/delete** for collections that already use **String `_id`** onto **windowed local-first syncdb**, with **REST remaining the membership source** (search, sort, pagination, RBAC). Remaining admin RPC (config, scripts, roles, comms, AI, consent, documents, version-config, background-tasks) leaves RTK `injectEndpoints` for a **tiny native `fetch` wrapper** with **host-injected auth**.
+
+- **Implementation plan:** [migrate-admin-to-syncdb.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/implementationPlans/migrate-admin-to-syncdb.md)
+- **Tasks:** [migrate-admin-to-syncdb.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/tasks/migrate-admin-to-syncdb.md)
+
+---
+
+## remove-legacy-realtime
+
+**Title:** `Remove legacy RTK realtime in Terreno 58`
+
+**Labels:** `area:api`, `type:feature`  
+**Project fields:** Area=`api`, Target=`58`, Impact=`Breaking`, IP=`remove-legacy-realtime`, Status=`Planned`
+
+Delete the **legacy RTK cache-patching realtime path** in Terreno 58. Collection live updates go through `@terreno/syncdb` (`sync` on `modelRouter` + `sync:delta`). This IP does **not** remove `RealtimeApp`: that plugin still hosts Socket.io, change streams, and the syncdb socket channel.
+
+- **Implementation plan:** [remove-legacy-realtime.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/implementationPlans/remove-legacy-realtime.md)
+- **Tasks:** [remove-legacy-realtime.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/tasks/remove-legacy-realtime.md)
+
+---
+
+## ai-observability
+
+**Title:** `AI observability (Langfuse-light, pluggable)`
+
+**Labels:** `area:ai`, `type:feature`  
+**Project fields:** Area=`ai`, Target=`Future`, Impact=`Feature`, IP=`ai-observability`, Status=`Planned`
+
+Ship **Langfuse-like** prompt versioning, nested traces (user / session / cost), multidimensional evaluators (LLM-as-judge + structured I/O), datasets, experiments, and a **local human review queue** — **inside Terreno**, as **plugins on `@terreno/ai`**, with an operator UI in **`admin-frontend` only**.
+
+- **Implementation plan:** [ai-observability.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/implementationPlans/ai-observability.md)
+- **Tasks:** [ai-observability.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/tasks/ai-observability.md)
+
+---
+
+## better-auth-strict-oauth-provider
+
+**Title:** `Better Auth sync omits unset oauthProvider`
+
+**Labels:** `area:auth`, `type:bug`  
+**Project fields:** Area=`auth`, Target=`Released`, Impact=`Fix`, IP=`better-auth-strict-oauth-provider`, Status=`Shipped`
+
+Email/password Better Auth users sync into a consumer `User` model that uses `strict: "throw"` and does **not** declare `oauthProvider`. The first authenticated `modelRouter` request after sign-up populates `req.user` (not 401).
+
+- **Implementation plan:** [better-auth-strict-oauth-provider.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/implementationPlans/better-auth-strict-oauth-provider.md)
+- **Tasks:** [better-auth-strict-oauth-provider.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/tasks/better-auth-strict-oauth-provider.md)
+
+---
+
+## mcp-service-tokens
+
+**Title:** `MCP service tokens`
+
+**Labels:** `area:mcp`, `type:feature`  
+**Project fields:** Area=`mcp`, Target=`Released`, Impact=`Feature`, IP=`mcp-service-tokens`, Status=`Shipped`
+
+Authenticated users mint **personal MCP service tokens** that act as that user on the consumer app's `POST /mcp` endpoint only. They copy an **MCP URL** plus a **Bearer `mcp_…` key** into external clients (Perplexity custom connectors, Claude Code, Cursor, Inspector) without pasting a session JWT. Admins list and revoke any user's tokens from the admin panel.
+
+- **Implementation plan:** [mcp-service-tokens.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/implementationPlans/mcp-service-tokens.md)
+- **Tasks:** [mcp-service-tokens.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/tasks/mcp-service-tokens.md)
+
+---
+
+## compile-pipeline-dedup
+
+**Title:** `Compile pipeline dedup (remove redundant recompiles)`
+
+**Labels:** `area:dx`, `type:chore`  
+**Project fields:** Area=`dx`, Target=`Released`, Impact=`Improvement`, IP=`compile-pipeline-dedup`, Status=`Shipped`
+
+Make each `@terreno/*` package compile **exactly once** per cold `bun run compile` by relying on Bun's built-in workspace dependency ordering, instead of the current pipeline that recompiles shared packages many times. Target contribution to the scan goal: ~60–90s.
+
+- **Implementation plan:** [compile-pipeline-dedup.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/implementationPlans/compile-pipeline-dedup.md)
+- **Tasks:** [compile-pipeline-dedup.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/tasks/compile-pipeline-dedup.md)
+
+---
+
+## support-agent
+
+**Title:** `Support answering agent (@terreno/support)`
+
+**Labels:** `area:ai`, `type:feature`  
+**Project fields:** Area=`ai`, Target=`Future`, Impact=`Feature`, IP=`support-agent`, Status=`Shaping`
+
+Ship `@terreno/support`, a `TerrenoPlugin` that:
+
+1. **Ingests knowledge** from pluggable `KnowledgeSource` adapters into a Mongo-backed,
+   chunked, searchable index. Built in: announcements, markdown docs folder, and a generic
+   Mongoose-model adapter.
+2. **Answers support questions** with `@terreno/ai`'s `AIService`, grounded only in
+   retrieved chunks, returning `answer`, `sources`, `confidence`, and `shouldEscalate`.
+3. **Exposes the agent as MCP tools** on the app's existing `/mcp` server
+   (`support_ask`, `support_search`, `support_get_document`, `support_list_sources`) and
+   as REST `modelRouter` actions, so ChatGPT, Claude, Cursor, an in-app widget, or a
+   human-support tool can all call the same agent.
+4. **Closes the loop for AI authors**: a `support/kb/` docs convention, a
+   `write-support-docs` skill, a `terreno-support check` validator, and a
+   "knowledge gaps" report (low-confidence / thumbs-down questions) that tells agents which
+   doc to write next.
+
+- **Implementation plan:** [support-agent.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/implementationPlans/support-agent.md)
+- **Tasks:** [support-agent.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/tasks/support-agent.md)
+
+---
+
+## ai-agents-and-failover
+
+**Title:** `AI agents and provider failover`
+
+**Labels:** `area:ai`, `type:feature`  
+**Project fields:** Area=`ai`, Target=`Future`, Impact=`Feature`, IP=`ai-agents-and-failover`, Status=`Shaping`
+
+Add two additive library seams to `@terreno/ai` so app code can:
+
+1. Define a reusable **Agent** (`name`, `instructions`, `tools`, optional `schema`, optional `middleware`) that runs through existing `AIService` logging.
+2. Wrap one or more Vercel AI SDK `LanguageModel`s in **`createFailoverModel`** so 429/502/503/overloaded failures try the next model. Every `AIService` method inherits failover without per-method changes.
+
+- **Implementation plan:** [ai-agents-and-failover.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/implementationPlans/ai-agents-and-failover.md)
+- **Tasks:** [ai-agents-and-failover.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/tasks/ai-agents-and-failover.md)
+
+---
+
+## terreno-58
+
+**Title:** `Terreno 58`
+
+**Labels:** `area:dx`, `type:chore`, `breaking`  
+**Project fields:** Area=`dx`, Target=`58`, Impact=`Breaking`, IP=*(not yet written)*, Status=`Planned`
+
+Umbrella for the Terreno 58 / Expo SDK 58 major release: every breaking change that was
+deprecated during 57.x lands together so consumers upgrade once. Each change keeps its own
+IP and tracking issue; this entry is the release checklist, not a plan.
+
+- Remove legacy RTK realtime (`modelRouter` `realtime`, RTK cache patching) — [remove-legacy-realtime](https://github.com/TerrenoLabs/terreno/blob/master/docs/implementationPlans/remove-legacy-realtime.md)
+- Remove admin `api` / `injectEndpoints` and `useAdminApi`; admin runs on syncdb — follow-up to [migrate-admin-to-syncdb](https://github.com/TerrenoLabs/terreno/blob/master/docs/implementationPlans/migrate-admin-to-syncdb.md)
+- Native module baseline (new dev-client binary) — [native-module-baseline](https://github.com/TerrenoLabs/terreno/blob/master/docs/implementationPlans/native-module-baseline.md)
+- HTTP rate limiting on by default — [rate-limiting](https://github.com/TerrenoLabs/terreno/blob/master/docs/implementationPlans/rate-limiting.md)
+- Expo SDK 58 upgrade — release PR [#1310](https://github.com/TerrenoLabs/terreno/pull/1310)
+- **RTK flag:** Breaking
+- **Depends on:** remove-legacy-realtime, migrate-admin-to-syncdb, native-module-baseline
+
+---
+
+## demo-workshop
+
+**Title:** `Demo workshop`
+
+**Labels:** `area:dx`, `type:feature`  
+**Project fields:** Area=`dx`, Target=`Next`, Impact=`Feature`, IP=`demo-workshop`, Status=`Planned`
+
+Turn the Expo demo into the workshop for `@terreno/ui`: a person can find a component, copy a usage snippet, change theme and viewport from the URL, and see whether every stable story passes interaction, accessibility, and visual checks on web and Android.
+
+- **Implementation plan:** [demo-workshop.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/implementationPlans/demo-workshop.md)
+- **Tasks:** [demo-workshop.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/tasks/demo-workshop.md)
+
+---
+
+## agent-ui-asks
+
+**Title:** `Agent UI Asks — agents ask the user for a typed answer inside the chat`
+
+**Labels:** `area:ai`, `type:feature`  
+**Project fields:** Area=`ai`, Target=`Next`, Impact=`Feature`, IP=`agent-ui-asks`, Status=`In progress`
+
+Let an agent **ask the user something and get a typed answer back in the same turn**. The agent calls an ask tool: pick one, pick many, upload images or files, edit a markdown draft, confirm an action, or fill a short form. `GPTChat` renders the matching `@terreno/ui` control inline. The user answers. The answer returns to the agent as a validated tool result and the turn continues from where it paused.
+
+- **Implementation plan:** [agent-ui-asks.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/implementationPlans/agent-ui-asks.md)
+- **Tasks:** [agent-ui-asks.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/tasks/agent-ui-asks.md)
+
+---
+
+## durable-agent-harness
+
+**Title:** `Durable agent harness (@terreno/ai/harness)`
+
+**Labels:** `area:ai`, `type:feature`  
+**Project fields:** Area=`ai`, Target=`Next`, Impact=`Feature`, IP=`durable-agent-harness`, Status=`Planned`
+
+One easy-to-use harness inside `@terreno/ai` that runs long-lived agentic work durably: deterministic multi-phase workflows, LLM agent loops, tools, subagents, human approvals, retries, and crash recovery — all audited. It must be strong enough to build an OpenClaw/Hermes-class personal agent, a coding agent, and a regulated clinical automation on the same primitives.
+
+- **Implementation plan:** [durable-agent-harness.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/implementationPlans/durable-agent-harness.md)
+- **Tasks:** [durable-agent-harness.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/tasks/durable-agent-harness.md)
+
+---
+
+## agent-ui-rich-replies
+
+**Title:** `Agent UI Rich Replies: steppers, checklists, galleries, and copy`
+
+**Labels:** `area:dx`, `type:feature`  
+**Project fields:** Area=`dx`, Target=`Next`, Impact=`Feature`, IP=`agent-ui-rich-replies`, Status=`Planned`
+
+- **Implementation plan:** [agent-ui-rich-replies.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/implementationPlans/agent-ui-rich-replies.md)
+- **Tasks:** [agent-ui-rich-replies.md](https://github.com/TerrenoLabs/terreno/blob/master/docs/tasks/agent-ui-rich-replies.md)
+
+---
+
+# Shipped, umbrella, and declined IPs
+
+Tracking issues created for IPs that previously lacked a `**Roadmap issue:**` header.
+`bun run roadmap:sync` reads this table directly — every column is a board field
+value, so a row here is the whole record for that item. Values must come from
+[`.github/roadmap-fields.yml`](https://github.com/TerrenoLabs/terreno/blob/master/.github/roadmap-fields.yml)
+(`Status`, `Target`, `Impact`) and from the `area:*` labels in
+[`.github/labels.yml`](https://github.com/TerrenoLabs/terreno/blob/master/.github/labels.yml)
+(`Area`). Already-shipped work uses `Target = Released`.
+
+When a slug also has a `##` section above, the section supplies the field values and
+this table supplies only the issue number.
+
+| IP slug | GitHub issue | Status | Area | Target | Impact | Type |
+|---------|--------------|--------|------|--------|--------|------|
+| `admin-only` | https://github.com/TerrenoLabs/terreno/issues/1075 | `Shipped` | `admin` | `Released` | `Feature` | `type:feature` |
+| `admin-ui-v2-django-parity` | https://github.com/TerrenoLabs/terreno/issues/1076 | `Shipped` | `admin` | `Released` | `Feature` | `type:feature` |
+| `admin-script-runner` | https://github.com/TerrenoLabs/terreno/issues/1077 | `Shipped` | `admin` | `Released` | `Feature` | `type:feature` |
+| `consent-forms` | https://github.com/TerrenoLabs/terreno/issues/1078 | `Shipped` | `ui` | `Released` | `Feature` | `type:feature` |
+| `upgrade-banner` | https://github.com/TerrenoLabs/terreno/issues/1079 | `Shipped` | `ui` | `Released` | `Feature` | `type:feature` |
+| `apierror-standard-error-redesign` | https://github.com/TerrenoLabs/terreno/issues/1080 | `Shipped` | `api` | `Released` | `Breaking` | `type:feature` |
+| `syncdb-local-first` | https://github.com/TerrenoLabs/terreno/issues/1081 | `Shipped` | `syncdb` | `Released` | `Feature` | `type:feature` |
+| `feature-flags-openfeature` | https://github.com/TerrenoLabs/terreno/issues/1082 | `Shipped` | `api` | `Released` | `Feature` | `type:feature` |
+| `design-blend-skill` | https://github.com/TerrenoLabs/terreno/issues/1083 | `Shipped` | `dx` | `Released` | `Feature` | `type:feature` |
+| `ModularAPI` | https://github.com/TerrenoLabs/terreno/issues/1084 | `Shipped` | `api` | `Released` | `Feature` | `type:feature` |
+| `mcp-boost-parity` | https://github.com/TerrenoLabs/terreno/issues/1085 | `In progress` | `mcp` | `Next` | `Feature` | `type:feature` |
+| `docs-site-and-versioning` | https://github.com/TerrenoLabs/terreno/issues/1086 | `Shipped` | `docs` | `Released` | `Feature` | `type:docs` |
+| `syncdb-codegen` | https://github.com/TerrenoLabs/terreno/issues/1110 | `Shipped` | `syncdb` | `Released` | `Feature` | `type:feature` |
+| `migrate-cicd-to-circleci` | https://github.com/TerrenoLabs/terreno/issues/1088 | `In progress` | `dx` | `Next` | `Improvement` | `type:chore` |
+| `rbac-permissions` | https://github.com/TerrenoLabs/terreno/issues/1089 | `Shipped` | `api` | `Released` | `Feature` | `type:feature` |
+| `infra-mcp` | https://github.com/TerrenoLabs/terreno/issues/1090 | `Planned` | `mcp` | `Future` | `Feature` | `type:feature` |
+| `comms-admin-dashboard` | https://github.com/TerrenoLabs/terreno/issues/1091 | `Shipped` | `admin` | `Released` | `Feature` | `type:feature` |
+| `model-router-mcp` | https://github.com/TerrenoLabs/terreno/issues/1092 | `Shipped` | `mcp` | `Released` | `Feature` | `type:feature` |
+| `terreno-langfuse-integration` | https://github.com/TerrenoLabs/terreno/issues/1093 | `Shipped` | `ai` | `Released` | `Feature` | `type:feature` |
+| `oss-launch-program` | https://github.com/TerrenoLabs/terreno/issues/1094 | `In progress` | `dx` | `Next` | `Improvement` | `type:chore` |
+| `b2b-platform-program` | https://github.com/TerrenoLabs/terreno/issues/1095 | `Planned` | `api` | `Next` | `Feature` | `type:feature` |
+| `offline-mode` | https://github.com/TerrenoLabs/terreno/issues/1096 | `Declined` | `syncdb` | `Future` | `Feature` | `type:feature` |
+| `model-router-actions` | https://github.com/TerrenoLabs/terreno/issues/1097 | `Declined` | `api` | `Future` | `Feature` | `type:feature` |
+| `feature-flags` | https://github.com/TerrenoLabs/terreno/issues/1098 | `Declined` | `api` | `Future` | `Feature` | `type:feature` |
+| `admin-improvements` | https://github.com/TerrenoLabs/terreno/issues/1099 | `Declined` | `admin` | `Future` | `Improvement` | `type:feature` |
+| `better-auth-strict-oauth-provider` | https://github.com/TerrenoLabs/terreno/issues/1218 | `Shipped` | `auth` | `Released` | `Fix` | `type:bug` |
+
+**Duplicate to retire:** [#1087](https://github.com/TerrenoLabs/terreno/issues/1087)
+covers the same `syncdb-codegen` IP as [#1110](https://github.com/TerrenoLabs/terreno/issues/1110).
+#1110 carries the fuller description and is the one on the board; close #1087 as a duplicate.
+
+Research and design sub-documents share the parent IP's issue: `admin-only-research` →
+#1075; `infra-mcp-research` → #1090; `migrate-cicd-to-circleci-research` → #1088;
+`syncdb-phase-c-design`, `terreno-syncdb-2`, and `syncdb-api-inventory` → #1081.