@terreno/mcp 56.0.0-beta.0 → 56.0.0-beta.2

package/dist/docs/versioned/next/tasks/oss-governance-baseline.md

@@ -14,37 +14,37 @@ See: [`docs/implementationPlans/oss-governance-baseline.md`](../implementationPl
 
 ## Phase 1: Legal baseline
 
-- [ ] **Task 1.1**: Add root `LICENSE` and `NOTICE`
+- [x] **Task 1.1**: Add root `LICENSE` and `NOTICE`
   - Description: Copy the MIT License text to a new root `LICENSE` (use the standard MIT template; `mcp-server` already ships MIT). Create `NOTICE` containing the project name, the copyright line `Copyright 2026 Flourish Health, Inc.`, and a one-line statement that the project is licensed under MIT. Include acknowledgement of vendored `api/src/vendor/wesleytodd-openapi/` with a pointer to its own `LICENSE`.
   - Files: `LICENSE` (new), `NOTICE` (new)
   - Depends on: none
   - Acceptance: `LICENSE` exists at repo root with standard MIT text; `NOTICE` mentions the vendored openapi code. Do not compare against `api/LICENSE` or `ui/LICENSE` — those remain Apache-2.0 until Task 1.4.
 
-- [ ] **Task 1.2**: Audit license coverage across published packages
+- [x] **Task 1.2**: Audit license coverage across published packages
   - Description: Read `.github/workflows/publish-on-tag.yml` and list every package it publishes. For each one, record in a scratch table: whether a `LICENSE` file exists, whether `package.json` has a `files` array, whether `LICENSE` is included in that array, and the `license` field value. Write the findings as a markdown table in the PR description. Do not fix anything in this task.
   - Files: none (findings go in the PR body)
   - Depends on: none
   - Acceptance: PR body contains a table with one row per published package and the four columns above; the table is derived from the actual repo, not copied from the IP.
 
-- [ ] **Task 1.3**: Add `LICENSE` to every published package
+- [x] **Task 1.3**: Add `LICENSE` to every published package
   - Description: For each package identified in Task 1.2 that lacks a `LICENSE`, create one by copying the root `LICENSE`. Packages to cover: `rtk`, `ai`, `admin-backend`, `admin-frontend`, `admin-spa`, `api-health`, `feature-flags`, `mcp-server`, `test`. Do not create `LICENSE` files in non-published directories (`demo`, `example-frontend`, `example-backend`, `website`, `terraform`).
   - Files: `rtk/LICENSE`, `ai/LICENSE`, `admin-backend/LICENSE`, `admin-frontend/LICENSE`, `admin-spa/LICENSE`, `api-health/LICENSE`, `feature-flags/LICENSE`, `mcp-server/LICENSE`, `test/LICENSE` (all new)
   - Depends on: Task 1.1, Task 1.2
   - Acceptance: every published package directory contains a `LICENSE` identical to the root `LICENSE`.
 
-- [ ] **Task 1.4**: Align `license` fields and `files` arrays
+- [x] **Task 1.4**: Align `license` fields and `files` arrays
   - Description: Set `"license": "MIT"` in the root `package.json` and in every published package's `package.json` (relicense `api`/`ui` from Apache-2.0). For every package that has an explicit `files` array, add `"LICENSE"` to it (`ui`, `rtk`, `admin-frontend`, `admin-spa`, `mcp-server` at minimum — confirm against Task 1.2 findings). Do not otherwise reorder or reformat `package.json`.
   - Files: `package.json`, `ui/package.json`, `rtk/package.json`, `admin-frontend/package.json`, `admin-spa/package.json`, `mcp-server/package.json`, plus any others found in Task 1.2
   - Depends on: Task 1.3
   - Acceptance: `bun pm pack --dry-run` run inside each published package lists `LICENSE` among the packed files; no `package.json` declares a license other than `MIT`.
 
-- [ ] **Task 1.5**: Verify relicensing consent for `api` and `ui`
+- [x] **Task 1.5**: Verify relicensing consent for `api` and `ui`
   - Description: Run `git log --format='%an <%ae>' -- api/ ui/ | sort -u` and list every distinct author. Report the list in the PR body, flagging any address that is not a `@flourish.health` address or a known bot. Do **not** proceed to merge the Apache-2.0 → MIT change for `api`/`ui` if a non-Flourish human contributor appears; instead leave a `TODO` note in the PR body requesting sign-off. (`mcp-server` is already MIT.)
   - Files: none (findings go in the PR body)
   - Depends on: Task 1.4
   - Acceptance: PR body lists all `api`/`ui` authors and explicitly states either "all Flourish/bot — safe to relicense" or names the contributors needing sign-off.
 
-- [ ] **Task 1.6**: Add a license-coverage CI check
+- [x] **Task 1.6**: Add a license-coverage CI check
   - Description: Create `scripts/check-license-coverage.ts` (Bun, TypeScript, `const` arrow functions, explicit return types). It should: read the list of published packages from `.github/workflows/publish-on-tag.yml` (parse job names or a hardcoded list with a comment pointing at the workflow), then for each assert (a) `LICENSE` exists, (b) `package.json` `license` equals the root `package.json` `license`, (c) if a `files` array exists it contains `LICENSE`. Print one line per failure and `process.exit(1)` when any check fails. Add a `check:licenses` script to the root `package.json` and a job to `.github/workflows/repo-policies.yml` that runs it.
   - Files: `scripts/check-license-coverage.ts` (new), `package.json`, `.github/workflows/repo-policies.yml`
   - Depends on: Task 1.4
@@ -52,25 +52,25 @@ See: [`docs/implementationPlans/oss-governance-baseline.md`](../implementationPl
 
 ## Phase 2: Contribution process
 
-- [ ] **Task 2.1**: Write `CONTRIBUTING.md`
+- [x] **Task 2.1**: Write `CONTRIBUTING.md`
   - Description: Create `CONTRIBUTING.md` covering, in this order: (1) Code of Conduct link; (2) ways to contribute (issue, discussion, docs fix, code); (3) development setup — `bun run bootstrap`, Bun version requirement, MongoDB replica-set requirement for `example-backend` (single-node replset is enough, change streams need it), the seeded users `test@example.com` / `superuser@example.com` with password `testpassword123`; (4) per-package commands table pulled from the root `package.json` scripts (`bun run api:test`, `bun run ui:test`, `bun run lint`, `bun run compile`); (5) code style pointers — link `AGENTS.md`, call out the no-barrel-imports rule and `bun run check:no-barrel-imports`, the Luxon requirement, and the logging conventions; (6) test expectations — new features ship with tests, coverage must not drop; (7) the IP process — link `docs/implementationPlans/README.md` and `IP_TEMPLATE.md`, explain when an IP is required (new package, new public API, cross-package change) versus not (bug fix, docs); (8) DCO sign-off instructions (`git commit -s`); (9) PR expectations — draft by default, CI green, screenshots for UI changes.
   - Files: `CONTRIBUTING.md` (new)
   - Depends on: none
   - Acceptance: every command shown in `CONTRIBUTING.md` exists in a `package.json` `scripts` block; the seeded credentials match `example-backend/src/scripts/`; no reference to `.claude/` or other agent-private paths.
 
-- [ ] **Task 2.2**: Add `CODE_OF_CONDUCT.md`
+- [x] **Task 2.2**: Add `CODE_OF_CONDUCT.md`
   - Description: Add Contributor Covenant 2.1 verbatim, with the enforcement contact set to `conduct@terreno.app`. Do not modify the covenant text other than the contact line and the project name.
   - Files: `CODE_OF_CONDUCT.md` (new)
   - Depends on: none
   - Acceptance: file states "Contributor Covenant" and version 2.1; contact address is present and is not a placeholder.
 
-- [ ] **Task 2.3**: Add `SECURITY.md`
+- [x] **Task 2.3**: Add `SECURITY.md`
   - Description: Create `SECURITY.md` with: a supported-versions table (current minor supported; previous minor receives security fixes only), reporting instructions naming GitHub private vulnerability reporting as the primary channel and `security@terreno.app` as fallback, a 5-business-day acknowledgement commitment, a statement that reporters should not open public issues for vulnerabilities, and a note that CodeQL runs on the repo (`.github/workflows/codeql-analysis.yml`).
   - Files: `SECURITY.md` (new)
   - Depends on: none
   - Acceptance: file exists at repo root so GitHub surfaces it under Security → Policy; both reporting channels are named.
 
-- [ ] **Task 2.4**: Add a DCO check for external PRs
+- [x] **Task 2.4**: Add a DCO check for external PRs
   - Description: Add a workflow job (either in `repo-policies.yml` or a new `.github/workflows/dco.yml`) that, for pull requests whose head repository differs from the base repository, verifies every commit message contains a `Signed-off-by:` line matching the commit author. Skip the check for PRs from the same repo and for bot authors (`dependabot[bot]`, `cursor[bot]`). Follow the repo's existing convention of validating required inputs before use.
   - Files: `.github/workflows/dco.yml` (new) or `.github/workflows/repo-policies.yml`
   - Depends on: Task 2.1
@@ -78,19 +78,19 @@ See: [`docs/implementationPlans/oss-governance-baseline.md`](../implementationPl
 
 ## Phase 3: Changelog
 
-- [ ] **Task 3.1**: Create the root `CHANGELOG.md` and backfill releases
+- [x] **Task 3.1**: Create the root `CHANGELOG.md` and backfill releases
   - Description: Create `CHANGELOG.md` in Keep-a-Changelog format with an `## [Unreleased]` section at the top, then one section per released version, newest first. Source the content from `gh release list --limit 40` and `gh release view <tag>` for each release from 0.20.0 to the current version. Group each entry under `Added` / `Changed` / `Fixed` / `Deprecated` / `Removed`. Include a header note that all `@terreno/*` packages are versioned in lockstep and a link to `docs/implementationPlans/oss-launch-program.md` is **not** needed here. Do not invent entries — if a release has no notes, write `- No published release notes.` under that version.
   - Files: `CHANGELOG.md` (new)
   - Depends on: none
   - Acceptance: every version tag returned by `gh release list` between 0.20.0 and current has a section; no section is empty; the file states the lockstep versioning rule.
 
-- [ ] **Task 3.2**: Reduce `api/CHANGELOG.md` to a pointer
+- [x] **Task 3.2**: Reduce `api/CHANGELOG.md` to a pointer
   - Description: Replace the contents of `api/CHANGELOG.md` with a short note that the changelog moved to the repo root, linking `../CHANGELOG.md`. Preserve the historical entries by moving them into the corresponding root `CHANGELOG.md` sections first if they contain detail the GitHub releases lack.
   - Files: `api/CHANGELOG.md`, `CHANGELOG.md`
   - Depends on: Task 3.1
   - Acceptance: `api/CHANGELOG.md` is under 10 lines and links to the root changelog; no historical detail was lost.
 
-- [ ] **Task 3.3**: Make changelog updates part of the release process
+- [x] **Task 3.3**: Make changelog updates part of the release process
   - Description: Edit `.rulesync/skills/release/SKILL.md` to add a required step: before tagging, move `## [Unreleased]` content into a new version section in the root `CHANGELOG.md` with today's date (via Luxon-formatted ISO date), and confirm the section is non-empty. Then run `bun run rules` to regenerate the mirrored skill files under `.cursor/`, `.claude/`, `.devin/`, `.github/`, and `.agents/`.
   - Files: `.rulesync/skills/release/SKILL.md`, plus generated mirrors
   - Depends on: Task 3.1
@@ -98,31 +98,31 @@ See: [`docs/implementationPlans/oss-governance-baseline.md`](../implementationPl
 
 ## Phase 4: GitHub templates
 
-- [ ] **Task 4.1**: Add issue forms
+- [x] **Task 4.1**: Add issue forms
   - Description: Create three GitHub issue forms. `bug_report.yml`: fields for affected package (dropdown listing all published `@terreno/*` packages plus `docs`, `examples`, `mcp`), version, platform (dropdown: iOS / Android / Web / Backend / N/A), reproduction steps (required textarea), expected vs actual, and a checkbox confirming the reporter searched existing issues. `feature_request.yml`: problem statement (required), proposed solution, alternatives considered, and a checkbox asking whether the requester is willing to open a PR. `docs_issue.yml`: page URL, what is wrong or missing, and suggested fix. Add `config.yml` with `blank_issues_enabled: false` and contact links to Discussions (Q&A and Ideas categories) and `SECURITY.md`.
   - Files: `.github/ISSUE_TEMPLATE/bug_report.yml`, `.github/ISSUE_TEMPLATE/feature_request.yml`, `.github/ISSUE_TEMPLATE/docs_issue.yml`, `.github/ISSUE_TEMPLATE/config.yml` (all new)
   - Depends on: Task 2.3
   - Acceptance: all four files parse as valid YAML; the package dropdown in `bug_report.yml` matches the packages published by `publish-on-tag.yml`; `config.yml` disables blank issues.
 
-- [ ] **Task 4.2**: Add a PR template
+- [x] **Task 4.2**: Add a PR template
   - Description: Create `.github/PULL_REQUEST_TEMPLATE.md` with sections: Summary; Related IP or issue; Type of change (checkboxes); Testing performed (with a reminder that frontend changes require screenshots or video per `AGENTS.md`); Checklist (tests added, `bun run lint` passes, `bun run compile` passes, docs updated, changelog `Unreleased` entry added for user-facing changes, DCO signed off). Keep it short enough that contributors actually fill it in — under 40 lines.
   - Files: `.github/PULL_REQUEST_TEMPLATE.md` (new)
   - Depends on: Task 2.1, Task 3.1
   - Acceptance: template is under 40 lines; references the changelog and the frontend-verification requirement.
 
-- [ ] **Task 4.3**: Add `CODEOWNERS`
+- [x] **Task 4.3**: Add `CODEOWNERS`
   - Description: Create `.github/CODEOWNERS` mapping each package directory to its owning team or maintainer, plus a catch-all root owner. Use GitHub team handles if they exist; otherwise use individual maintainer usernames. Include entries for `docs/`, `.github/`, `.rulesync/`, and `terraform/`.
   - Files: `.github/CODEOWNERS` (new)
   - Depends on: none
   - Acceptance: every top-level package directory has an owner; the file has a catch-all `*` line; GitHub's CODEOWNERS validation (visible in repo settings) reports no errors.
 
-- [ ] **Task 4.4**: Document required repository settings
+- [x] **Task 4.4**: Document required repository settings
   - Description: Add a short section to `CONTRIBUTING.md` (or a new `docs/explanation/repository-settings.md` if it exceeds 30 lines) listing the GitHub settings a maintainer must enable manually because they cannot be committed: Discussions enabled with the categories from [`public-roadmap-github.md`](../implementationPlans/public-roadmap-github.md), private vulnerability reporting enabled, branch protection on `master` requiring the CI checks, "Allow squash merging" only, and auto-delete of merged branches.
   - Files: `CONTRIBUTING.md` or `docs/explanation/repository-settings.md`
   - Depends on: Task 2.1
   - Acceptance: the list names each setting and where to find it in the GitHub UI; no setting is described as already enabled unless verified.
 
-- [ ] **Task 4.5**: Append the governance section to `README.md`
+- [x] **Task 4.5**: Append the governance section to `README.md`
   - Description: Add a `## License` section and a `## Contributing` section near the end of `README.md`, plus a license badge next to the existing npm badges. Link `LICENSE`, `CONTRIBUTING.md`, `CODE_OF_CONDUCT.md`, and `SECURITY.md`. Do not modify any other README content — positioning changes belong to a different IP.
   - Files: `README.md`
   - Depends on: Task 1.1, Task 2.1, Task 2.2, Task 2.3

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

@@ -0,0 +1,60 @@
+# Tasks: Password reset and email verification
+
+IP: [password-reset-and-email-verification](../implementationPlans/password-reset-and-email-verification.md)
+
+## Phase 1 — Token infrastructure
+
+- [ ] **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`
+  - Description: `emailVerified` field plugin for user schemas
+  - Files: `api/src/plugins.ts`
+  - Depends on: none
+  - Acceptance: plugin test; example User adopts it
+
+## Phase 2 — JWT routes + mail
+
+- [ ] **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
+  - 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
+  - Description: `resetPassword` + `verifyEmail` templates with app-override hook and `publicAppUrl` links
+  - Files: `comms/src/templates.ts`
+  - Depends on: comms-abstraction Phase 1
+  - Acceptance: rendered output snapshot tests
+
+## Phase 3 — Better Auth parity
+
+- [ ] **Task 3.1**: Better Auth hooks
+  - Description: `sendResetPassword`/`sendVerificationEmail` wired to the same templates
+  - Files: `api/src/betterAuthSetup.ts`
+  - Depends on: 2.3
+  - Acceptance: parity test asserting identical template usage
+
+## Phase 4 — Client + docs
+
+- [ ] **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
+  - 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
+  - Description: how-to + env reference + rulesync
+  - Files: `docs/how-to/password-reset.md`, `docs/reference/environment-variables.md`, `.rulesync/**`
+  - Depends on: Phase 2
+  - Acceptance: `bun run rules:check` passes

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

@@ -13,19 +13,19 @@ See: [`docs/implementationPlans/positioning-django-rails-universal.md`](../imple
 
 ## Phase 1: Canonical copy
 
-- [ ] **Task 1.1**: Write `docs/explanation/positioning.md`
+- [x] **Task 1.1**: Write `docs/explanation/positioning.md`
   - Description: New explainer containing five clearly-labeled copy blocks in fenced code blocks (so they can be copied verbatim without markdown rendering surprises): `tagline` (one line), `elevator` (2–3 sentences), `pillars` (three bullets, in the order batteries-included / universal-by-default / AI-native), `aiPillar` (2–3 sentences naming both AI layers per IP question PO7 — the MCP tool layer and the `/terreno-*` SDLC pipeline process layer), and `pitch` (~150 words). Then a "Why the Django/Rails analogy" section, then the honest comparison table from the IP. Then a "Language rules" section restating the four rules from the program doc (lead with the analogy, say "universal app", never claim unshipped features, keep superlatives off reference pages) plus a fifth: never describe one AI layer without the other.
   - Files: `docs/explanation/positioning.md` (new)
   - Depends on: none
   - Acceptance: five fenced copy blocks present and labeled; the `aiPillar` block names both the MCP tools and the `/terreno-*` pipeline; comparison table has at least eight rows including at least three honest gaps with IP links; language rules section has all five rules.
 
-- [ ] **Task 1.2**: Verify every claim in the comparison table
+- [x] **Task 1.2**: Verify every claim in the comparison table
   - Description: For each row of the comparison table, confirm the Terreno side exists by finding it in source: `modelRouter` in `api/src/api.ts`, admin packages, `Permissions` in `api/src/permissions.ts`, Better Auth in `api/src/betterAuth*.ts`, MCP tools in `mcp-server/src/tools.ts`, and the SDLC pipeline in `plugins/terreno-planning/skills/`. For each "not shipped" row (background jobs, SSR, RBAC), confirm it is genuinely absent and link the IP or roadmap item tracking it. Correct any row that turns out to be wrong.
   - Files: `docs/explanation/positioning.md`
   - Depends on: Task 1.1
   - Acceptance: every "shipped" row cites a source path; the generator row cites both `mcp-server/src/tools.ts` and `plugins/terreno-planning/`; every "not shipped" row links an IP file that exists in `docs/implementationPlans/`.
 
-- [ ] **Task 1.3**: Gate the pipeline claim on its portability work
+- [x] **Task 1.3**: Gate the pipeline claim on its portability work
   - Description: The `/terreno-*` pipeline currently only runs inside this monorepo (see [`agentic-sdlc-plugin`](../implementationPlans/agentic-sdlc-plugin.md), "It only works here"). Do not publish positioning copy that implies consumers can use it until that IP's Phase 2 is complete. Check the state of `agentic-sdlc-plugin` Task 2.5 before writing the `aiPillar` block; if portability is not done, write the block describing the tool layer only and add a `TODO` in the IP to revisit, rather than making a claim that fails on first use.
   - Files: `docs/explanation/positioning.md`
   - Depends on: Task 1.1
@@ -87,7 +87,7 @@ See: [`docs/implementationPlans/positioning-django-rails-universal.md`](../imple
   - Depends on: Task 1.1
   - Acceptance: every published package has a `description` matching the pattern, plus `repository`, `homepage`, and `bugs` fields; `bun install` still resolves cleanly.
 
-- [ ] **Task 5.2**: Document the GitHub repository metadata
+- [x] **Task 5.2**: Document the GitHub repository metadata
   - Description: The repo description and topics cannot be set from a commit. Add a "Repository metadata" subsection to `docs/explanation/positioning.md` giving the exact description string (the short tagline variant from PO1 option C) and the exact topic list to set: `typescript`, `react-native`, `expo`, `express`, `mongoose`, `framework`, `mcp`, `ai`, `universal-apps`, `full-stack`. Mark it as a maintainer action.
   - Files: `docs/explanation/positioning.md`
   - Depends on: Task 1.1

package/dist/docs/versioned/next/tasks/public-roadmap-github.md

@@ -13,19 +13,19 @@ See: [`docs/implementationPlans/public-roadmap-github.md`](../implementationPlan
 
 ## Phase 1: Discussions
 
-- [ ] **Task 1.1**: Document Discussion category setup
+- [x] **Task 1.1**: Document Discussion category setup
   - Description: Create `docs/explanation/roadmap-process.md`. Start with a "Maintainer setup" section listing the seven Discussion categories from the IP with their exact names, formats (Announcement / Question-Answer / Open-ended), descriptions, and display order. For each, include the description text to paste into the GitHub UI (one to two sentences, written for outside users). Note that Discussions must first be enabled in Settings → General → Features.
   - Files: `docs/explanation/roadmap-process.md` (new)
   - Depends on: none
   - Acceptance: all seven categories are listed with name, format, description, and order; the Announcements category is marked maintainers-only.
 
-- [ ] **Task 1.2**: Write the pinned intro posts
+- [x] **Task 1.2**: Write the pinned intro posts
   - Description: In `docs/explanation/roadmap-process.md`, add a "Pinned posts" section containing the full markdown body for one pinned post per category. Each should say what belongs there, what does not, and where to go instead. The Ideas post must explain that ideas are the intake funnel and that maintainers promote them to issues. The Agents & AI post must point at the MCP setup docs and the skills directory. The Q&A post must link `docs/how-to/` and note that recurring questions become how-to guides.
   - Files: `docs/explanation/roadmap-process.md`
   - Depends on: Task 1.1
   - Acceptance: seven post bodies exist, each under 200 words, each naming an alternative destination for off-topic content.
 
-- [ ] **Task 1.3**: Add Discussion templates
+- [x] **Task 1.3**: Add Discussion templates
   - Description: Create `.github/DISCUSSION_TEMPLATE/rfc.yml` with fields: title guidance, Summary (required), Motivation (required), Detailed design (required), Alternatives considered (required), Drawbacks, Unresolved questions, and a checkbox acknowledging that accepted RFCs become IPs in `docs/implementationPlans/`. Create `.github/DISCUSSION_TEMPLATE/ideas.yml` with: Problem you are hitting (required), What you tried, Rough idea for a solution, and Would you be willing to help implement. Both must set the correct `labels:` and target the right category via the filename convention.
   - Files: `.github/DISCUSSION_TEMPLATE/rfc.yml` (new), `.github/DISCUSSION_TEMPLATE/ideas.yml` (new)
   - Depends on: Task 1.1
@@ -33,13 +33,13 @@ See: [`docs/implementationPlans/public-roadmap-github.md`](../implementationPlan
 
 ## Phase 2: Project board
 
-- [ ] **Task 2.1**: Document Project board setup
+- [x] **Task 2.1**: Document Project board setup
   - Description: Add a "Project board" section to `docs/explanation/roadmap-process.md` specifying: the Project name (`Terreno Roadmap`), whether it is repo- or org-level, the six fields with their exact types and option values from the IP, and the four views with their layout, grouping, and filters. Include the `gh project` commands a maintainer can run for the parts the CLI supports, and mark the rest as UI-only.
   - Files: `docs/explanation/roadmap-process.md`
   - Depends on: Task 1.1
   - Acceptance: all six fields and four views are specified precisely enough to recreate without further decisions; option values match the IP tables exactly.
 
-- [ ] **Task 2.2**: Write the tracking-issue bodies for this program's IPs
+- [x] **Task 2.2**: Write the tracking-issue bodies for this program's IPs
   - Description: Create `docs/explanation/roadmap-seed-issues.md` containing one ready-to-paste issue body per IP listed in `docs/implementationPlans/oss-launch-program.md`. Each body must include: a one-paragraph summary written for an outside reader (not internal shorthand), a link to the IP file, a link to the task file, the RTK deprecation flag, the dependencies, and the labels and Project field values to set (`Area`, `Target`, `Impact`, `IP`). Read each IP file to write its summary — do not paraphrase from the program index alone.
   - Files: `docs/explanation/roadmap-seed-issues.md` (new)
   - Depends on: Task 2.1
@@ -47,19 +47,19 @@ See: [`docs/implementationPlans/public-roadmap-github.md`](../implementationPlan
 
 ## Phase 3: Labels and triage
 
-- [ ] **Task 3.1**: Define the label set as data
+- [x] **Task 3.1**: Define the label set as data
   - Description: Create `.github/labels.yml` listing every label from the IP taxonomy with `name`, `color`, and `description`. Use a consistent color family per prefix (for example one hue for `area:`, another for `type:`, another for `status:`, and distinct colors for the bare labels). Add a "Labels" section to `docs/explanation/roadmap-process.md` explaining that `.github/labels.yml` is the source of truth and how to apply it (`gh label create` loop or a label-sync action), plus which GitHub default labels to delete.
   - Files: `.github/labels.yml` (new), `docs/explanation/roadmap-process.md`
   - Depends on: Task 1.1
   - Acceptance: `.github/labels.yml` parses as valid YAML and contains every label in the IP taxonomy table with no duplicates; colors are valid six-digit hex without `#`.
 
-- [ ] **Task 3.2**: Add the triage workflow
+- [x] **Task 3.2**: Add the triage workflow
   - Description: Create `.github/workflows/triage.yml`. On `issues: [opened]`, add the `status:needs-triage` label. Then read the issue body for the package dropdown value rendered by the issue forms and map it to the matching `area:*` label (for example `@terreno/api` → `area:api`, `docs` → `area:docs`). Implement the mapping in an inline `actions/github-script` step with an explicit lookup object; if no match is found, add no area label and leave a comment asking the reporter to specify. Validate required inputs before use per the repo convention.
   - Files: `.github/workflows/triage.yml` (new)
   - Depends on: Task 3.1
   - Acceptance: workflow parses as valid YAML; the mapping object covers every option in `bug_report.yml`'s package dropdown; the no-match path does not throw.
 
-- [ ] **Task 3.3**: Document the backfill triage pass
+- [x] **Task 3.3**: Document the backfill triage pass
   - Description: Add a "One-time backfill" section to `docs/explanation/roadmap-process.md` describing how to triage existing open issues and PRs onto the new taxonomy: run `gh issue list --state open --limit 200 --json number,title,labels`, assign one `area:` and one `type:` label each, add anything still relevant to the board with `Status = Inbox`, and close or label `status:wontfix` anything stale beyond six months. Include the read-only `gh` commands for producing the working list.
   - Files: `docs/explanation/roadmap-process.md`
   - Depends on: Task 3.1
@@ -67,25 +67,25 @@ See: [`docs/implementationPlans/public-roadmap-github.md`](../implementationPlan
 
 ## Phase 4: Roadmap generation
 
-- [ ] **Task 4.1**: Write the roadmap generator
+- [x] **Task 4.1**: Write the roadmap generator
   - Description: Create `scripts/generate-roadmap.ts` (Bun, TypeScript, `const` arrow functions with explicit return types, no new dependencies). It queries the GitHub GraphQL API for the `Terreno Roadmap` ProjectV2 items and their field values, then writes `ROADMAP.md`: a header explaining that the board is the source of truth and that no dates are promised, then sections grouped by `Target` (current release first, then `Next`, then `Future`), and within each, subsections by `Area`. Each item renders as a bullet with its title, issue link, `Impact`, and an IP link when the `IP` field is set. Exclude items with `Status` of `Declined`. Read the token from `GITHUB_TOKEN` and the project number from `TERRENO_PROJECT_NUMBER`; fail with a clear message listing missing variables when either is absent. Use Luxon for the generated-at timestamp.
   - Files: `scripts/generate-roadmap.ts` (new), `package.json` (add a `roadmap:generate` script)
   - Depends on: Task 2.1
   - Acceptance: running with both env vars unset prints an error naming both and exits non-zero; with a valid token it writes a `ROADMAP.md` matching the described structure; `bun run lint` passes.
 
-- [ ] **Task 4.2**: Add the roadmap workflow
+- [x] **Task 4.2**: Add the roadmap workflow
   - Description: Create `.github/workflows/roadmap-generate.yml` running on `schedule` (daily) and `workflow_dispatch`. Validate `GITHUB_TOKEN`/PAT and `TERRENO_PROJECT_NUMBER` at job start with the repo's fail-fast pattern. Run `bun run roadmap:generate`, then commit and push `ROADMAP.md` only if `git diff --quiet` reports changes. Use a bot identity for the commit.
   - Files: `.github/workflows/roadmap-generate.yml` (new)
   - Depends on: Task 4.1
   - Acceptance: workflow parses as valid YAML; the secret-validation step lists every required variable; the commit step is conditional on a real diff.
 
-- [ ] **Task 4.3**: Seed `ROADMAP.md` and link it
+- [x] **Task 4.3**: Seed `ROADMAP.md` and link it
   - Description: Commit an initial hand-written `ROADMAP.md` (the generator will overwrite it later) built from the IPs in `docs/implementationPlans/oss-launch-program.md` plus the active plans in `PLAN_INDEX.md`. Add a note at the top that it is generated from the Project board. Link it from `README.md` and add it to the docs site sidebar in `website/docusaurus.config.ts` (or the sidebars file if navigation is defined there — check both).
   - Files: `ROADMAP.md` (new), `README.md`, `website/docusaurus.config.ts` or `website/sidebars.ts`
   - Depends on: Task 4.1
   - Acceptance: `ROADMAP.md` lists every IP in the program with a `Target`; the docs site builds (`bun run website:build`) with the new nav entry; the README links it.
 
-- [ ] **Task 4.4**: Add the docs feedback footer link
+- [x] **Task 4.4**: Add the docs feedback footer link
   - Description: In `website/docusaurus.config.ts`, add a footer link (or theme config item) pointing at the Docs feedback Discussions category. If Docusaurus's `editUrl` mechanism is the better fit for per-page feedback, add the discussion link alongside the existing `editUrl` rather than replacing it.
   - Files: `website/docusaurus.config.ts`
   - Depends on: Task 1.1
@@ -93,19 +93,19 @@ See: [`docs/implementationPlans/public-roadmap-github.md`](../implementationPlan
 
 ## Phase 5: Linear bridge
 
-- [ ] **Task 5.1**: Document the Linear bridge rules
+- [x] **Task 5.1**: Document the Linear bridge rules
   - Description: Add a "Linear bridge" section to `docs/explanation/roadmap-process.md` covering: which artifacts live where (GitHub = public discussion, issues, roadmap state; Linear = sprint execution; `docs/implementationPlans/` = design), the one-way GitHub → Linear intake triggered by the `tracked` label, the rule that Linear status is not synced back and that GitHub state changes via `Fixes #NNN` on merge, how internally-originated public work gets a manual GitHub issue, and an explicit statement that internal-only Linear work is never mirrored. Explain *why* status is not two-way synced.
   - Files: `docs/explanation/roadmap-process.md`
   - Depends on: Task 3.1
   - Acceptance: the section states the direction of every sync, names the trigger label, and gives the reason two-way status sync was rejected.
 
-- [ ] **Task 5.2**: Document the intake flow in `CONTRIBUTING.md`
+- [x] **Task 5.2**: Document the intake flow in `CONTRIBUTING.md`
   - Description: Add a "How work gets planned" section to `CONTRIBUTING.md`, under 30 lines: file an Ideas discussion → maintainer promotes to an issue → issue is triaged onto the roadmap board → substantial work gets an IP → implementation. Add the RFC path for public API changes and new packages. Link `ROADMAP.md`, the Discussions categories, and `docs/implementationPlans/README.md`.
   - Files: `CONTRIBUTING.md`
   - Depends on: Task 5.1
   - Acceptance: the section is under 30 lines, links all three destinations, and matches the flow diagram in the IP.
 
-- [ ] **Task 5.3**: Add the release announcement step
+- [x] **Task 5.3**: Add the release announcement step
   - Description: Edit `.rulesync/skills/release/SKILL.md` to add a step: after publishing a release that includes breaking changes or deprecations, post a discussion in the Announcements category summarizing the change, linking the changelog section and the relevant upgrade note in `mcp-server/src/docs/upgrades/`. Regenerate mirrors with `bun run rules`.
   - Files: `.rulesync/skills/release/SKILL.md` plus generated mirrors
   - Depends on: Task 1.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@terreno/mcp",
-  "version": "56.0.0-beta.0",
+  "version": "56.0.0-beta.2",
   "description": "MCP server for Terreno - provides documentation, tools, and prompts for building full-stack apps",
   "type": "module",
   "main": "dist/index.js",
@@ -27,9 +27,9 @@
   "dependencies": {
     "@modelcontextprotocol/sdk": "^1.27.0",
     "@sentry/bun": "^10.39.0",
-    "@terreno/api": "56.0.0-beta.0",
+    "@terreno/api": "56.0.0-beta.2",
     "minisearch": "^7.2.0",
-    "mongoose": "8.23.0"
+    "mongoose": "9.7.4"
   },
   "devDependencies": {
     "@biomejs/biome": "^2.3.6",
@@ -38,6 +38,7 @@
     "typescript": "~6.0.3"
   },
   "files": [
+    "LICENSE",
     "dist",
     "src/docs"
   ],

package/src/docs/templates/bootstrap/backend/types/models/userTypes.template.md

@@ -1,16 +1,17 @@
-/// <reference types="passport-local-mongoose" />
 import type {APIErrorConstructor} from "@terreno/api";
 import type mongoose from "mongoose";
-import type {Document, FilterQuery, Model} from "mongoose";
+import type {Document, Model} from "mongoose";
+
+type ModelQuery<T> = Partial<Record<keyof T, unknown>> & Record<string, unknown>;
 
 export interface DefaultStatics<T> {
   findOneOrNone(
-    query: FilterQuery<T>,
+    query: ModelQuery<T>,
     errorArgs?: Partial<APIErrorConstructor>
   ): Promise<(Document & T) | null>;
 
   findExactlyOne(
-    query: FilterQuery<T>,
+    query: ModelQuery<T>,
     errorArgs?: Partial<APIErrorConstructor>
   ): Promise<Document & T>;
 }

package/src/docs/templates/tools/model.template.md

@@ -5,9 +5,11 @@ interface {{Name}}Document extends mongoose.Document {
 {{interfaceFields}}
 }
 
+type ModelQuery<T> = Partial<Record<keyof T, unknown>> & Record<string, unknown>;
+
 interface {{Name}}Model extends mongoose.Model<{{Name}}Document> {
-  findOneOrNone(query: mongoose.FilterQuery<{{Name}}Document>): Promise<{{Name}}Document | null>;
-  findExactlyOne(query: mongoose.FilterQuery<{{Name}}Document>): Promise<{{Name}}Document>;
+  findOneOrNone(query: ModelQuery<{{Name}}Document>): Promise<{{Name}}Document | null>;
+  findExactlyOne(query: ModelQuery<{{Name}}Document>): Promise<{{Name}}Document>;
 }
 
 const {{lowerName}}Schema = new mongoose.Schema<{{Name}}Document, {{Name}}Model>(

package/src/docs/upgrades/0.31.0.md

@@ -0,0 +1,60 @@
+# 0.31.0
+
+Terreno packages move in lockstep. Nothing in this release removes or renames a public
+export, so most apps upgrade by bumping the `@terreno/*` versions and running:
+
+- `bun run compile` and `bun run lint` at the repo root
+- `cd <your frontend> && bun run sdk` after any `@terreno/api` route or model surface change
+
+## Mongoose 9 is now supported (Mongoose 8 still works)
+
+Every published package that talks to Mongoose (`api`, `test`, `admin-backend`, `ai`,
+`feature-flags`) widened its peer dependency to `^8.0.0 || ^9.0.0`. Terreno itself
+develops against Mongoose 9.7.4.
+
+You can stay on Mongoose 8 with no changes. If you upgrade your app to Mongoose 9, the
+changes that mattered inside Terreno will most likely matter in your code too:
+
+```typescript
+// Before (Mongoose 8)
+await Model.findOneAndUpdate(filter, update, {new: true});
+
+// After (Mongoose 9)
+await Model.findOneAndUpdate(filter, update, {returnDocument: "after"});
+```
+
+- Aggregation-pipeline updates must pass `updatePipeline: true` to `updateMany`.
+- Query middleware no longer takes the legacy `next()` callback — use the async form.
+- Array schema paths expose `getEmbeddedSchemaType()`; the private `caster` property is gone.
+- Mongoose 9 ships its own types, so `@types/mongodb` and
+  `@types/passport-local-mongoose` should be removed from your dev dependencies.
+- Pin `bson` to `7.2.0` if your lockfile resolves an older copy alongside Mongoose 9.
+
+Mongoose 9 requires Node >= 20.19.0. Terreno's root `package.json` now declares that
+engine range for local development.
+
+## `@terreno/api` type changes
+
+Both changes widen or relax types; they are source-compatible for normal usage, but
+explicit annotations may need updating:
+
+- `modelRouter` now accepts `Model<T, any, any, any, any, any>` instead of `Model<T>`,
+  so models with custom query helpers, methods, or virtuals no longer need a cast.
+- `findOneOrNoneFor(model, query)` takes `ModelQuery<T>` (a partial record keyed by the
+  document fields) instead of Mongoose's `FilterQuery<T>`. If you were building a
+  `FilterQuery<T>` value to pass in, it still works; if you were annotating the variable
+  as `FilterQuery<T>` and relying on operator typing, switch to `ModelQuery<T>`.
+
+## `@terreno/admin-backend` array field metadata
+
+`GET /admin/config` derives array item metadata (`itemType`, `itemRef`, `itemEnum`) from
+Mongoose's public `getEmbeddedSchemaType()` when available, falling back to the Mongoose 8
+`caster` shape. `itemEnum` is only emitted when the embedded enum is an array, so an enum
+declared as an object map no longer produces a malformed `itemEnum`. Admin clients that
+read `itemEnum` should treat it as optional.
+
+## License changed from Apache-2.0 to MIT
+
+All published `@terreno/*` packages are now MIT licensed and ship a `LICENSE` file in the
+package tarball. No code change is required; update any license inventory or attribution
+list that pinned Terreno as Apache-2.0.

package/src/docs/upgrades/56.0.0-beta.2.md

@@ -0,0 +1,59 @@
+# 56.0.0-beta.2
+
+Second beta of the Expo SDK 56 line. Packages publish under the npm `beta` dist-tag;
+`npm install @terreno/ui` (no tag) still resolves to the stable `0.x` release.
+
+```bash
+bun add @terreno/ui@beta @terreno/api@beta @terreno/rtk@beta
+# optional local-first data layer
+bun add @terreno/syncdb@beta
+```
+
+## Upgrade Expo before Terreno
+
+This line targets Expo SDK 56. Upgrade the app first, then install Terreno betas:
+
+| Package | Version |
+|---------|---------|
+| `expo` | `~56.0.12` |
+| `react-native` | `0.85.3` |
+| `react` | `19.2.3` |
+| `typescript` | `~6.0.3` |
+
+Follow Expo's SDK 56 upgrade guide, then bump `@terreno/*` to `56.0.0-beta.2` (or `@beta`).
+Run `bun run compile` / `bun run lint` at the app root and regenerate the OpenAPI SDK after
+any `@terreno/api` surface change (`bun run sdk` in the frontend).
+
+Terreno's version major now tracks the Expo SDK major. Stay on the latest `0.x` packages
+until you are ready to move the app to Expo 56.
+
+## New package: `@terreno/syncdb`
+
+Optional local-first layer (TinyBase MergeableStore, durable outbox, websocket delta sync,
+encrypted web persistence). Install as `@terreno/syncdb@beta` (or the exact version). See:
+
+- [`docs/how-to/migrate-rtk-to-syncdb.md`](https://github.com/FlourishHealth/terreno/blob/master/docs/how-to/migrate-rtk-to-syncdb.md)
+- [`docs/reference/syncdb.md`](https://github.com/FlourishHealth/terreno/blob/master/docs/reference/syncdb.md)
+
+`@terreno/syncdb` does not replace the generated OpenAPI SDK, Better Auth wiring, or
+feature flags — only collection sync/CRUD offline paths.
+
+## `excludeArchivedPlugin` now filters `findOne`
+
+`excludeArchivedPlugin` applies the same archived filter to `findOne` that it already
+applied to `find`, matching `isDeletedPlugin`. Code that relied on `findOne` returning
+archived documents must query with an explicit archived override or a different plugin
+configuration.
+
+## Sync / REST error codes
+
+Sync and REST CRUD executors preserve kebab-case error `code` values
+(`create-not-allowed`, `update-not-allowed`, `delete-not-allowed`, `invalid-request-body`)
+and status-specific error names on hook-rejection paths. Clients that matched on older
+code strings should update.
+
+## From `56.0.0-beta.0`
+
+`beta.0` was cut from `release-56.0.0`. This beta is cut from `master` after that branch
+merged (`#976`), and also includes `@terreno/comms` plus the sync/Mongoose 9 fixes listed
+in `CHANGELOG.md` for this version.

package/src/docs/versioned/next/README.md

@@ -21,6 +21,7 @@ Documentation for the Terreno monorepo: shared packages for full-stack applicati
 | [@terreno/admin-backend](reference/admin-backend.md) | Admin panel backend plugin |
 | [@terreno/admin-frontend](reference/admin-frontend.md) | Admin panel frontend screens |
 | [@terreno/api-health](reference/api-health.md) | Health check endpoint plugin |
+| [@terreno/comms](reference/comms.md) | Pluggable communications providers and delivery logging |
 | [@terreno/mcp](reference/mcp-server.md) | AI coding assistant integration (MCP) |
 
 ## Quick links

package/src/docs/versioned/next/explanation/README.md

@@ -2,13 +2,19 @@
 
 Understanding-oriented documentation: concepts, architecture, and context.
 
+## Deployment
+
+- [Deployment baseline](deployment-baseline.md) — seven requirements for production Terreno apps
+- [GCP deployment architecture](deployment-architecture-gcp.md) — Cloud Run + GCS/CDN topology and tradeoffs
+- [GCP hosting architecture](gcp-hosting-architecture.md) — static site hosting with GCS and Cloud CDN (legacy detail)
+
 ## Contents
 
 - [AI-powered workflows](ai-workflows.md) — Autonomous documentation, testing, and maintenance workflows
 - [Authentication architecture](authentication.md) — How JWT, OAuth, and token refresh work
 - [Configuration system](configuration-system.md) — Runtime configuration with database persistence
 - [Dependency management](dependency-management.md) — Dependabot, auto-merge, and security practices
-- [GCP hosting architecture](gcp-hosting-architecture.md) — Static site hosting with GCS and Cloud CDN
 - [Modular API design](modular-api-design.md) — 🚧 Why TerrenoApp replaces setupServer
 - [modelRouter actions](model-router-actions.md) — Named collection and instance operations on modelRouter
 - [No barrel imports](no-barrel-imports.md) — Import concrete modules, not `index` re-export barrels
+- [Positioning](positioning.md) — Canonical copy blocks and the honest Django/Rails comparison