@terreno/mcp 57.4.0 → 57.6.1

package/src/docs/versioned/57.2.0/tasks/docs-reference-coverage.md

@@ -8,7 +8,7 @@ See: [`docs/implementationPlans/docs-reference-coverage.md`](../implementationPl
 
 - **Do not write documentation from scratch.** The content already exists in `.cursor/rules/*/00-*.mdc` files. Your job is to convert prescriptive agent rules into descriptive public reference prose, verify every claim against source, and remove anything internal.
 - Verify every exported symbol you document by grepping the package's `src/index.ts`. If a rule file documents something that no longer exists, drop it and note the drift in the PR body.
-- READMEs are rendered on npmjs.com where relative links break. Use absolute `https://github.com/flourishhealth/terreno/...` or docs-site URLs in every README.
+- READMEs are rendered on npmjs.com where relative links break. Use absolute `https://github.com/TerrenoLabs/terreno/...` or docs-site URLs in every README.
 - Match the section ordering of `docs/reference/api.md` for new reference pages. Read it first.
 - Run `bun run website:build` before each commit that adds or moves a docs page.
 

package/src/docs/versioned/57.2.0/tasks/migrate-cicd-to-circleci.md

@@ -15,7 +15,7 @@ Research: [`docs/implementationPlans/migrate-cicd-to-circleci-research.md`](../i
 ## Phase 0: Prerequisites
 
 - [ ] **Task 0.1**: Confirm CircleCI org/plan and project link
-  - Description: Verify the requester-created CircleCI organization, plan, and that `FlourishHealth/terreno` is connected with permission to report GitHub checks. Enable **dynamic config** / setup workflows for the project. Record org slug + project slug in the IP header or how-to doc.
+  - Description: Verify the requester-created CircleCI organization, plan, and that `TerrenoLabs/terreno` is connected with permission to report GitHub checks. Enable **dynamic config** / setup workflows for the project. Record org slug + project slug in the IP header or how-to doc.
   - Files: `docs/how-to/circleci.md` (stub OK)
   - Depends on: none (human prerequisite)
   - Acceptance: a manual “hello” pipeline can be triggered from the project; dynamic config is enabled.

package/src/docs/versioned/57.2.0/tasks/web-ssr-and-admin-spa.md

@@ -4,7 +4,7 @@ See: [`docs/implementationPlans/web-ssr-and-admin-spa.md`](../implementationPlan
 
 **RTK deprecation flag:** **Partial.** Phase 0 must run after PR #869 merges, because whether the local-first client can be kept out of the server render path is the main feasibility question. Tasks marked `[RTK]` touch the data layer directly.
 
-**Prerequisite:** Expo SDK ≥ 55. The repo catalog is on `~54.0.29`; PR [#779](https://github.com/flourishhealth/terreno/pull/779) upgrades to SDK 56. Verify the merged Expo version before starting and stop if it is below 55.
+**Prerequisite:** Expo SDK ≥ 55. The repo catalog is on `~54.0.29`; PR [#779](https://github.com/TerrenoLabs/terreno/pull/779) upgrades to SDK 56. Verify the merged Expo version before starting and stop if it is below 55.
 
 ## Instructions for the implementing agent
 

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

@@ -45,6 +45,7 @@ Canonical copy, language rules, and the Django/Rails comparison:
 | [@terreno/comms](reference/comms.md) | Pluggable communications providers |
 | [@terreno/feature-flags](reference/feature-flags.md) | Feature flags and A/B testing plugin for `@terreno/api` |
 | [@terreno/mcp](reference/mcp-server.md) | MCP server that gives coding agents Terreno docs, codegen tools, and prompts |
+| [@terreno/cli](reference/cli.md) | `terreno` CLI for docs, codegen, bootstrap, and OpenAPI REST |
 | [create-terreno-app](reference/create-terreno-app.md) | CLI to scaffold a deployable full-stack Terreno app (`bunx create-terreno-app`) |
 
 ### Legacy
@@ -58,6 +59,8 @@ Canonical copy, language rules, and the Django/Rails comparison:
 ## Quick links
 
 - [Getting started](tutorials/getting-started.md)
+- [Set up Terreno MCP](how-to/set-up-terreno-mcp.md)
+- [Debug with MCP](how-to/debug-with-mcp.md)
 - [Create a Terreno app](how-to/create-a-terreno-app.md)
 - [Positioning](explanation/positioning.md)
 - [How admin interfaces are shaped](explanation/admin-interface.md)

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

@@ -14,7 +14,7 @@ Understanding-oriented documentation: concepts, architecture, and context.
 - [Planning plugins](planning-plugins.md) — How the lifecycle and scan plugins divide discovery from delivery
 - [Loop engineering](loop-engineering.md) — Fresh-invocation lifecycle, state, evidence, and orchestration boundaries
 - [GitHub issue lifecycle](../how-to/github-issue-lifecycle.md) — Pick-ready issues and plan comments for Pick/Roast
-- [Install agent skills](../how-to/install-agent-skills.md) — `npx skills add FlourishHealth/terreno`
+- [Install agent skills](../how-to/install-agent-skills.md) — `npx skills add TerrenoLabs/terreno`
 - [AI-powered workflows](ai-workflows.md) — Autonomous documentation, testing, and maintenance workflows
 - [Authentication architecture](authentication.md) — Better Auth, JWT, and optional MCP service tokens
 - [Organization tenancy](organizations.md) — Optional Membership-backed tenancy, context, and isolation boundaries
@@ -24,6 +24,7 @@ Understanding-oriented documentation: concepts, architecture, and context.
 - [modelRouter actions](model-router-actions.md) — Named collection and instance operations on modelRouter
 - [Explicit `any` policy](explicit-any-policy.md) — Require rationale markers and ratchet usage per file
 - [No barrel imports](no-barrel-imports.md) — Import concrete modules, not `index` re-export barrels
+- [TypeScript configuration](typescript-configuration.md) — tsconfig profiles for Node, frontend, Expo, and Bun workspaces on TypeScript 6
 - [Production source rules](source-rules.md) — Arrow functions, Luxon, APIError, logging, findOne, `as any`
 - [Positioning](positioning.md) — Canonical copy blocks and the honest Django/Rails comparison
 - [Versioning policy](versioning-policy.md) — Lockstep `@terreno/*` versions, pre-1.0 breaks, deprecation window

package/src/docs/versioned/next/explanation/ai-workflows.md

@@ -27,11 +27,11 @@ Analyzes code diffs after each merge to identify:
 **Trigger:** Push to master  
 **Purpose:** Keeps AI assistant rules synchronized with codebase changes
 
-Maintains the single source of truth in `.rulesync/rules/` and ensures:
-- `.cursor/rules/`, skills, agents, and hooks (Cursor)
-- `CLAUDE.md`, `.claude/rules/`, skills, agents, and hooks (Claude Code)
-- `.github/copilot-instructions.md` (GitHub Copilot)
-- Native hooks for Codex CLI, Copilot CLI, Antigravity CLI, and Devin
+Maintains centralized agent guidance and generates the matching configuration for:
+- Cursor
+- Claude Code
+- GitHub Copilot
+- Codex CLI, Copilot CLI, Antigravity CLI, and Devin
 
 **Workflow:**
 1. Detects package changes, new APIs, or convention updates

package/src/docs/versioned/next/explanation/announcements/rtk-deprecation.md

@@ -6,7 +6,7 @@
 
 ## `@terreno/rtk` data sync is deprecated — migrate to `@terreno/syncdb`
 
-Starting with **56.0.0**, Terreno's default frontend data path is **local-first** via [`@terreno/syncdb`](https://github.com/FlourishHealth/terreno/blob/master/docs/reference/syncdb.md). Collection reads and writes apply to an on-device store first; the server reconciles over the sync protocol. This replaces RTK Query hooks for CRUD lists and mutations.
+Starting with **56.0.0**, Terreno's default frontend data path is **local-first** via [`@terreno/syncdb`](https://github.com/TerrenoLabs/terreno/blob/master/docs/reference/syncdb.md). Collection reads and writes apply to an on-device store first; the server reconciles over the sync protocol. This replaces RTK Query hooks for CRUD lists and mutations.
 
 ### What changed
 
@@ -18,12 +18,12 @@ Starting with **56.0.0**, Terreno's default frontend data path is **local-first*
 
 1. **By next major:** move collection screens from RTK Query to syncdb. `@terreno/rtk` will not publish in the next major line.
 2. **Support window:** `@terreno/rtk` continues to publish with a deprecation notice through the **current major** (56.x beta and stable 0.x).
-3. **Recommended order:** migrate to **Better Auth** first, then syncdb per screen ([migration guide](https://github.com/FlourishHealth/terreno/blob/master/docs/how-to/migrate-rtk-to-syncdb.md)).
+3. **Recommended order:** migrate to **Better Auth** first, then syncdb per screen ([migration guide](https://github.com/TerrenoLabs/terreno/blob/master/docs/how-to/migrate-rtk-to-syncdb.md)).
 
 ### Why local-first
 
-Instant UI, durable offline writes, and simpler screen code — at the cost of explicit conflict and sync-status handling. See [local-first data](https://github.com/FlourishHealth/terreno/blob/master/docs/explanation/local-first-data.md).
+Instant UI, durable offline writes, and simpler screen code — at the cost of explicit conflict and sync-status handling. See [local-first data](https://github.com/TerrenoLabs/terreno/blob/master/docs/explanation/local-first-data.md).
 
 ### Questions
 
-Open a thread in [Docs feedback](https://github.com/FlourishHealth/terreno/discussions/categories/docs-feedback) or reply here.
+Open a thread in [Docs feedback](https://github.com/TerrenoLabs/terreno/discussions/categories/docs-feedback) or reply here.

package/src/docs/versioned/next/explanation/deployment-baseline.md

@@ -46,7 +46,7 @@ Expo Router supports three web output modes. The choice determines hosting optio
 |------|--------|-----------|-----|---------|----------------|
 | `single` | One `index.html` SPA | No | No | Any static host | **Current default** |
 | `static` | Per-route HTML files | No | No | Any static host | Available; better SEO |
-| `server` | `dist/client` + `dist/server` | Yes | Yes (alpha, SDK ≥ 55) | Node/Bun/edge runtime | Not yet — repo catalog is Expo `~54.0.29`; see [Web SSR and admin SPA](https://github.com/FlourishHealth/terreno/blob/master/docs/implementationPlans/web-ssr-and-admin-spa.md) |
+| `server` | `dist/client` + `dist/server` | Yes | Yes (alpha, SDK ≥ 55) | Node/Bun/edge runtime | Not yet — repo catalog is Expo `~54.0.29`; see [Web SSR and admin SPA](https://github.com/TerrenoLabs/terreno/blob/master/docs/implementationPlans/web-ssr-and-admin-spa.md) |
 
 ## Multi-environment checklist
 
@@ -63,7 +63,7 @@ Staging and production differ in these values (each environment needs its **own
 
 ## Containerizing the backend
 
-The canonical Dockerfile is [`example-backend/Dockerfile`](https://github.com/FlourishHealth/terreno/blob/master/example-backend/Dockerfile). It:
+The canonical Dockerfile is [`example-backend/Dockerfile`](https://github.com/TerrenoLabs/terreno/blob/master/example-backend/Dockerfile). It:
 
 1. Installs workspace dependencies and compiles packages in dependency order.
 2. Builds a Bun-compiled binary for production.

package/src/docs/versioned/next/explanation/example-coverage.md

@@ -23,6 +23,7 @@ that file (and its imports) to a working example. Gaps stay explicit.
 | File upload / GCS | yes — `example-backend/src/api/settings.ts`, AI file routes in `example-backend/src/api/ai.ts` | yes — `example-frontend/app/(tabs)/files.tsx`, `example-frontend/app/gcs-settings.tsx` | |
 | Better Auth | yes — `example-backend/src/utils/betterAuthConfig.ts`, `BetterAuthApp` in `example-backend/src/server.ts` | yes — `example-frontend/app/login.tsx`, `example-frontend/lib/betterAuth.ts` | Default `AUTH_PROVIDER` is `better-auth`. |
 | syncdb local-first | yes — `SyncApp` in `example-backend/src/server.ts` | yes — `example-frontend/store/syncdb.ts`, `example-frontend/app/(tabs)/index.tsx` | PR #869 closed without merge; `@terreno/syncdb` shipped on the launch line and is the example todos path. |
+| SyncDB diagnostics | n/a | yes — `debug` registration in `example-frontend/store/syncdb.ts`, debugger UI at `example-frontend/app/syncdb-debug.tsx` | `terreno-mcp-local` can inspect, snapshot/compare/merge, mutate, flush, reconcile/resync, and exercise offline/conflict paths against the running development client. |
 | RBAC | yes — `example-backend/src/rbacRoles.ts`, `access.ts`, `access: {resource: "todo"}` on the todo router | yes — `example-frontend/app/admin/roles.tsx` | Shipped. The IP snapshot that marked RBAC "not shipped" is stale. Plan: [rbac-permissions.md](../implementationPlans/rbac-permissions.md). |
 | Organizations | yes — `createAccess({organizations: true})`, `organizationSettingsSchema`, `orgScopedPlugin` on projects | yes — admin org directory/settings at `example-frontend/app/admin/orgs/` | Settings live on `Organization.settings`; example registers a nested timezone schema. |
 | Background jobs | no | no | No generic job queue example. Admin maintenance scripts (`example-backend/src/adminScripts.ts`, script runner widget) are a related but different surface. Plan: [admin-script-runner.md](../implementationPlans/admin-script-runner.md). |
@@ -31,8 +32,8 @@ that file (and its imports) to a working example. Gaps stay explicit.
 
 | Gap | Why it stays | Follow-up |
 | --- | --- | --- |
-| AI structured output | Chat streaming already demonstrates the AI pillar; structured `generateObject`-style routes are unused by current tutorials | Track with [AI-first tutorials #1010](https://github.com/FlourishHealth/terreno/issues/1010) (`add-ai-features.md` requires one structured-output call). |
-| Generic background jobs | Unshipped as a first-class example; do not invent a queue UI here | Track with [Durable background jobs #1188](https://github.com/FlourishHealth/terreno/issues/1188). Admin script runner is a related surface — [admin-script-runner.md](../implementationPlans/admin-script-runner.md). |
+| AI structured output | Chat streaming already demonstrates the AI pillar; structured `generateObject`-style routes are unused by current tutorials | Track with [AI-first tutorials #1010](https://github.com/TerrenoLabs/terreno/issues/1010) (`add-ai-features.md` requires one structured-output call). |
+| Generic background jobs | Unshipped as a first-class example; do not invent a queue UI here | Track with [Durable background jobs #1188](https://github.com/TerrenoLabs/terreno/issues/1188). Admin script runner is a related surface — [admin-script-runner.md](../implementationPlans/admin-script-runner.md). |
 
 ## Keeping the matrix true
 

package/src/docs/versioned/next/explanation/loop-engineering.md

@@ -161,5 +161,5 @@ contain chain-of-thought or transcripts.
   terminal/non-failing, no conflicts, and no actionable review findings.
 
 The detailed contract, schemas, and three execution scenarios live under
-[`plugins/terreno-planning/references/`](https://github.com/FlourishHealth/terreno/tree/master/plugins/terreno-planning/references).
+[`plugins/terreno-planning/references/`](https://github.com/TerrenoLabs/terreno/tree/master/plugins/terreno-planning/references).
 

package/src/docs/versioned/next/explanation/modular-api-design.md

@@ -228,7 +228,7 @@ Migration will be supported with:
 ## Learn More
 
 - 📖 [Implementation plan](../implementationPlans/ModularAPI.md) — Full technical specification
-- 💬 [GitHub PR #149](https://github.com/FlourishHealth/terreno/pull/149) — Discussion and feedback
+- 💬 [GitHub PR #149](https://github.com/TerrenoLabs/terreno/pull/149) — Discussion and feedback
 
 ## Related
 

package/src/docs/versioned/next/explanation/repository-settings.md

@@ -1,7 +1,7 @@
 # Repository settings (maintainers)
 
 Some GitHub settings cannot be committed to the repo. Enable these manually in
-the [Terreno repository settings](https://github.com/FlourishHealth/terreno/settings).
+the [Terreno repository settings](https://github.com/TerrenoLabs/terreno/settings).
 
 ## Discussions
 
@@ -43,7 +43,7 @@ Package CI, policy, Playwright, Maestro web, architectural review, deploy, and
 release workflows run under `.circleci/` (see
 [how-to/circleci.md](../how-to/circleci.md)). Require the path-filtered CircleCI
 check names. Remove required GitHub Action checks for workflow files whose
-trigger is `on: []`; those checks cannot report anymore. Do not require the
+trigger is `push.branches-ignore: ["**"]`; those checks cannot report anymore. Do not require the
 config-only `circleci-config` workflow. Keep Cursor Approval / Security / Bugbot
 as GitHub App checks; they are not CircleCI jobs.
 

package/src/docs/versioned/next/explanation/roadmap-process.md

@@ -5,11 +5,11 @@ Implementation plans in `docs/implementationPlans/` remain the design source of
 both.
 
 - **GitHub** — discussions, triaged issues, the Terreno Roadmap project board, generated
-  [`ROADMAP.md`](https://github.com/FlourishHealth/terreno/blob/master/ROADMAP.md)
+  [`ROADMAP.md`](https://github.com/TerrenoLabs/terreno/blob/master/ROADMAP.md)
 - **Linear** — estimates, assignees, sprint workflow (internal)
 - **IPs** — approved design docs before substantial cross-package work
 
-See also [CONTRIBUTING.md](https://github.com/FlourishHealth/terreno/blob/master/CONTRIBUTING.md) for the contributor intake flow.
+See also [CONTRIBUTING.md](https://github.com/TerrenoLabs/terreno/blob/master/CONTRIBUTING.md) for the contributor intake flow.
 Issue-sized work that is not a public roadmap item uses
 [GitHub issue lifecycle](../how-to/github-issue-lifecycle.md)
 (`create-github-issue` → `work-github-issues`, or `status:ready-for-dev` →
@@ -88,10 +88,11 @@ half applies:
 | 1 | Announcements | Announcement | Maintainers only | Official release notes, breaking changes, deprecations, and launch updates from the Terreno team. |
 | 2 | Q&A | Question / Answer | Anyone | Ask how to use Terreno. Search existing threads first; accepted answers may become how-to guides in `docs/how-to/`. |
 | 3 | Ideas | Open-ended | Anyone | Feature ideas and improvements before they are shaped. This is the intake funnel — do not open a tracking issue until a maintainer promotes your idea. |
-| 4 | Agents & AI | Open-ended | Anyone | MCP setup, Cursor/Claude skills, agent workflows, and prompt patterns for building with Terreno. |
-| 5 | RFCs | Open-ended | Anyone | Substantial proposals that change public API or add packages. Use the RFC discussion template; accepted RFCs become IPs. |
-| 6 | Show and tell | Open-ended | Anyone | Apps and experiments built with Terreno. Share what you shipped and what friction you hit. |
-| 7 | Docs feedback | Open-ended | Anyone | Report missing or confusing documentation. Link the page URL; recurring feedback becomes docs PRs. |
+| 4 | Hacktoberfest | Open-ended | Anyone | Pitch something to build during Hacktoberfest and upvote the ideas you want. Popular, well-scoped ideas become `hacktoberfest` issues anyone can pick up. |
+| 5 | Agents & AI | Open-ended | Anyone | MCP setup, Cursor/Claude skills, agent workflows, and prompt patterns for building with Terreno. |
+| 6 | RFCs | Open-ended | Anyone | Substantial proposals that change public API or add packages. Use the RFC discussion template; accepted RFCs become IPs. |
+| 7 | Show and tell | Open-ended | Anyone | Apps and experiments built with Terreno. Share what you shipped and what friction you hit. |
+| 8 | Docs feedback | Open-ended | Anyone | Report missing or confusing documentation. Link the page URL; recurring feedback becomes docs PRs. |
 
 ### Pinned posts
 
@@ -102,8 +103,8 @@ Pin one intro post per category after creation. Bodies below are ready to paste.
 ```markdown
 Release announcements, breaking changes, and deprecation notices land here.
 
-- Do **not** file support bugs as announcements — use [Issues](https://github.com/FlourishHealth/terreno/issues/new/choose) or Q&A.
-- Security issues: see [SECURITY.md](https://github.com/FlourishHealth/terreno/blob/master/SECURITY.md) (private report only).
+- Do **not** file support bugs as announcements — use [Issues](https://github.com/TerrenoLabs/terreno/issues/new/choose) or Q&A.
+- Security issues: see [SECURITY.md](https://github.com/TerrenoLabs/terreno/blob/master/SECURITY.md) (private report only).
 ```
 
 #### Q&A
@@ -111,9 +112,9 @@ Release announcements, breaking changes, and deprecation notices land here.
 ```markdown
 Ask **how** to use Terreno — setup, APIs, deployment, agents.
 
-1. Search [existing Q&A](https://github.com/FlourishHealth/terreno/discussions/categories/q-a) and the [docs site](https://terreno-docs.netlify.app/).
-2. For step-by-step guides, start with [`docs/how-to/`](https://github.com/FlourishHealth/terreno/tree/master/docs/how-to).
-3. Bug reports belong in [Bug report issues](https://github.com/FlourishHealth/terreno/issues/new?template=bug_report.yml), not here.
+1. Search [existing Q&A](https://github.com/TerrenoLabs/terreno/discussions/categories/q-a) and the [docs site](https://terreno-docs.netlify.app/).
+2. For step-by-step guides, start with [`docs/how-to/`](https://github.com/TerrenoLabs/terreno/tree/master/docs/how-to).
+3. Bug reports belong in [Bug report issues](https://github.com/TerrenoLabs/terreno/issues/new?template=bug_report.yml), not here.
 
 When an answer repeats, maintainers turn it into a how-to doc via PR.
 ```
@@ -123,19 +124,36 @@ When an answer repeats, maintainers turn it into a how-to doc via PR.
 ```markdown
 **Ideas are the intake funnel.** Share problems and rough solutions before they become roadmap items.
 
-- Do **not** open a feature issue directly — maintainers promote accepted ideas to tracked issues on the [Terreno Roadmap](https://github.com/FlourishHealth/terreno/projects) board.
+- Do **not** open a feature issue directly — maintainers promote accepted ideas to tracked issues on the [Terreno Roadmap](https://github.com/TerrenoLabs/terreno/projects) board.
 - For API/package-level design, use the **RFCs** category instead.
-- Bugs → [Bug report](https://github.com/FlourishHealth/terreno/issues/new?template=bug_report.yml).
+- Bugs → [Bug report](https://github.com/TerrenoLabs/terreno/issues/new?template=bug_report.yml).
 ```
 
+#### Hacktoberfest
+
+```markdown
+**Pitch Hacktoberfest ideas here, and 👍 the ones you want built.**
+
+1. [Start a Hacktoberfest discussion](https://github.com/TerrenoLabs/terreno/discussions/new?category=hacktoberfest) — the form asks for the idea, area, rough size, and what "done" looks like.
+2. Upvote and comment on other pitches. Upvotes are how maintainers rank them.
+3. Maintainers turn popular, well-scoped ideas into issues labeled [`hacktoberfest`](https://github.com/TerrenoLabs/terreno/issues?q=is%3Aissue+is%3Aopen+label%3Ahacktoberfest) and link them back here. Pick one up by commenting on the issue.
+
+Longer-term feature ideas → **Ideas**. Bugs → [Bug report](https://github.com/TerrenoLabs/terreno/issues/new?template=bug_report.yml).
+```
+
+Promotion follows the Ideas path, with one change: a Hacktoberfest idea small enough to finish
+in a weekend becomes a `hacktoberfest` + `good first issue` work item directly (see
+[GitHub issue lifecycle](../how-to/github-issue-lifecycle.md)) instead of a `Shaping` roadmap
+item. Larger ones go through `roadmap-promote` like any other idea.
+
 #### Agents & AI
 
 ```markdown
 MCP server setup, Cursor/Claude skills, and agent-driven workflows.
 
-- MCP package: [`mcp-server/`](https://github.com/FlourishHealth/terreno/tree/master/mcp-server) and hosted `terreno-mcp`.
-- Agent skills: [`.rulesync/skills/`](https://github.com/FlourishHealth/terreno/tree/master/.rulesync/skills) (mirrored into editor-specific copies).
-- Terreno planning plugin: [`plugins/terreno-planning/`](https://github.com/FlourishHealth/terreno/tree/master/plugins/terreno-planning).
+- MCP package: [`mcp-server/`](https://github.com/TerrenoLabs/terreno/tree/master/mcp-server) and hosted `terreno-mcp`.
+- Agent skills: [`.rulesync/skills/`](https://github.com/TerrenoLabs/terreno/tree/master/.rulesync/skills) (mirrored into editor-specific copies).
+- Terreno planning plugin: [`plugins/terreno-planning/`](https://github.com/TerrenoLabs/terreno/tree/master/plugins/terreno-planning).
 
 General feature ideas → **Ideas**. Doc typos → **Docs feedback** or a docs PR.
 ```
@@ -145,7 +163,7 @@ General feature ideas → **Ideas**. Doc typos → **Docs feedback** or a docs P
 ```markdown
 Propose changes to **public API**, **new published packages**, or **cross-package architecture**.
 
-Use the [RFC template](https://github.com/FlourishHealth/terreno/discussions/new?category=rfcs) (Summary, Motivation, Design, Alternatives).
+Use the [RFC template](https://github.com/TerrenoLabs/terreno/discussions/new?category=rfcs) (Summary, Motivation, Design, Alternatives).
 
 Accepted RFCs become implementation plans in `docs/implementationPlans/` before large code changes. Small bugs and docs fixes do not need an RFC.
 ```
@@ -170,7 +188,7 @@ Every docs page also has a **Discuss this page** link in the footer.
 
 ### Project board
 
-The board must be an **organization** project under `FlourishHealth`. The generator queries
+The board must be an **organization** project under `TerrenoLabs`. The generator queries
 `organization(login:).projectV2`, so a repo-level project returns no data.
 
 `bun run roadmap:sync` creates the project, its fields, and its items from repo data — no
@@ -187,8 +205,8 @@ What it reads, and therefore what you edit to change the board:
 
 | Source | Drives |
 | ------ | ------ |
-| [`.github/roadmap-fields.yml`](https://github.com/FlourishHealth/terreno/blob/master/.github/roadmap-fields.yml) | `Status`, `Target`, `Impact` options |
-| `area:*` labels in [`.github/labels.yml`](https://github.com/FlourishHealth/terreno/blob/master/.github/labels.yml) | `Area` options |
+| [`.github/roadmap-fields.yml`](https://github.com/TerrenoLabs/terreno/blob/master/.github/roadmap-fields.yml) | `Status`, `Target`, `Impact` options |
+| `area:*` labels in [`.github/labels.yml`](https://github.com/TerrenoLabs/terreno/blob/master/.github/labels.yml) | `Area` options |
 | [`roadmap-seed-issues.md`](roadmap-seed-issues.md) | one item per roadmap entry, plus its field values and issue labels |
 
 **Fields** (single-select unless noted):
@@ -205,7 +223,7 @@ What it reads, and therefore what you edit to change the board:
 `Target` answers *which release*, never *what state* — `Status` carries state. Already-shipped
 work uses `Target = Released` so it groups at the bottom of `ROADMAP.md` instead of inflating
 an upcoming version. `TARGET_ORDER` in
-[`scripts/generate-roadmap/lib.ts`](https://github.com/FlourishHealth/terreno/blob/master/scripts/generate-roadmap/lib.ts)
+[`scripts/generate-roadmap/lib.ts`](https://github.com/TerrenoLabs/terreno/blob/master/scripts/generate-roadmap/lib.ts)
 must stay deep-equal to the yaml list; a test enforces it.
 
 **Views** — still UI-only; there is no GitHub API for creating project views.
@@ -227,29 +245,29 @@ before applying a rewrite.
 
 ### Labels
 
-[`.github/labels.yml`](https://github.com/FlourishHealth/terreno/blob/master/.github/labels.yml) is the source of truth.
+[`.github/labels.yml`](https://github.com/TerrenoLabs/terreno/blob/master/.github/labels.yml) is the source of truth.
 
 Every issue on the board carries the **`roadmap`** label. That label — not a title prefix — is
 how roadmap work is filtered:
 
 ```bash
-gh issue list --repo FlourishHealth/terreno --label roadmap --state all
+gh issue list --repo TerrenoLabs/terreno --label roadmap --state all
 ```
 
 `roadmap:sync` adds it to every issue it declares, so seed entries do not repeat it on their
 `**Labels:**` line. Tracking issues used to be titled `[Roadmap] <outcome>`; titles are now
 just the outcome, and `displayTitle` in
-[`scripts/generate-roadmap/lib.ts`](https://github.com/FlourishHealth/terreno/blob/master/scripts/generate-roadmap/lib.ts)
+[`scripts/generate-roadmap/lib.ts`](https://github.com/TerrenoLabs/terreno/blob/master/scripts/generate-roadmap/lib.ts)
 strips the legacy prefix wherever it survives.
 
 Apply or update labels with `gh` authenticated as a maintainer:
 
 ```bash
-bun run labels:sync --repo FlourishHealth/terreno --dry-run   # preview
-bun run labels:sync --repo FlourishHealth/terreno             # apply
+bun run labels:sync --repo TerrenoLabs/terreno --dry-run   # preview
+bun run labels:sync --repo TerrenoLabs/terreno             # apply
 ```
 
-[`scripts/sync-labels.ts`](https://github.com/FlourishHealth/terreno/blob/master/scripts/sync-labels.ts)
+[`scripts/sync-labels.ts`](https://github.com/TerrenoLabs/terreno/blob/master/scripts/sync-labels.ts)
 parses the YAML and passes each description to `gh` as a single argument, so descriptions
 containing commas or quotes survive intact. It refuses to run on a malformed color,
 a missing description, or a duplicate name.
@@ -266,8 +284,11 @@ Delete unused GitHub defaults after the new taxonomy is applied (`gh label list`
 The workflow's built-in `GITHUB_TOKEN` **cannot** be used here: it is repository-scoped and
 returns no `projectV2` data for an organization project. GitHub also reserves the name
 `GITHUB_TOKEN`, so a PAT cannot be supplied under that name — hence the separate
-`ROADMAP_PROJECT_TOKEN` secret. Pushing the regenerated `ROADMAP.md` still uses the default
-token via `permissions: contents: write`.
+`ROADMAP_PROJECT_TOKEN` secret. The same PAT also pushes the regenerated `ROADMAP.md`: the
+`master` ruleset requires a pull request and the default `GITHUB_TOKEN` is not a bypass actor
+on it, so the PAT needs `repo` scope and its owner must be listed as a ruleset bypass actor.
+[`.github/scripts/git-auth-roadmap-pat.sh`](https://github.com/TerrenoLabs/terreno/blob/master/.github/scripts/git-auth-roadmap-pat.sh)
+applies that credential only for the fetch/push steps, so `bun install` never sees it.
 
 Locally, export the PAT as `GITHUB_TOKEN` (for example `GITHUB_TOKEN=$(gh auth token)`), which
 is the variable the generator reads.
@@ -325,9 +346,9 @@ bun run roadmap:check --on-board --labels "roadmap,area:api,type:feature" --stat
 Run it with no arguments to print every valid label and field option. It enforces exactly one
 `area:*` and one `type:*` label, requires the `roadmap` label under `--on-board` (omit the
 flag when triaging an issue that is not headed for the board), rejects labels absent from
-[`.github/labels.yml`](https://github.com/FlourishHealth/terreno/blob/master/.github/labels.yml),
+[`.github/labels.yml`](https://github.com/TerrenoLabs/terreno/blob/master/.github/labels.yml),
 rejects Project values absent from
-[`.github/roadmap-fields.yml`](https://github.com/FlourishHealth/terreno/blob/master/.github/roadmap-fields.yml),
+[`.github/roadmap-fields.yml`](https://github.com/TerrenoLabs/terreno/blob/master/.github/roadmap-fields.yml),
 and catches an `Area` field that disagrees with the issue's `area:` label.
 
 Those two files are the single source for the taxonomy: labels in `labels.yml`, Status/Target/
@@ -376,11 +397,10 @@ do not claim completion until done.
 
 | Workflow | Trigger | Purpose |
 | -------- | ------- | ------- |
-| [`.github/workflows/triage.yml`](https://github.com/FlourishHealth/terreno/blob/master/.github/workflows/triage.yml) | Issue opened | `status:needs-triage` + `area:*` from package dropdown + `type:*` from Kind when present |
-| [`.github/workflows/roadmap-generate.yml`](https://github.com/FlourishHealth/terreno/blob/master/.github/workflows/roadmap-generate.yml) | Daily + manual | `roadmap:sync --check` for board drift, then regenerate `ROADMAP.md` from the board |
-| [`.github/workflows/roadmap-sync.yml`](https://github.com/FlourishHealth/terreno/blob/master/.github/workflows/roadmap-sync.yml) | Taxonomy files change on `master` + manual | Apply labels and reconcile the board's fields and items |
-| [`.github/workflows/roadmap-reconcile.yml`](https://github.com/FlourishHealth/terreno/blob/master/.github/workflows/roadmap-reconcile.yml) | IP or task files change on `master` + manual | Advance status from IP headers, push to the board, regenerate `ROADMAP.md` |
-
+| [`.github/workflows/triage.yml`](https://github.com/TerrenoLabs/terreno/blob/master/.github/workflows/triage.yml) | Issue opened | `status:needs-triage` + `area:*` from package dropdown + `type:*` from Kind when present |
+| [`.github/workflows/roadmap-generate.yml`](https://github.com/TerrenoLabs/terreno/blob/master/.github/workflows/roadmap-generate.yml) | Daily + manual | `roadmap:sync --check` for board drift, then regenerate `ROADMAP.md` from the board and open a pull request when it changes |
+| [`.github/workflows/roadmap-sync.yml`](https://github.com/TerrenoLabs/terreno/blob/master/.github/workflows/roadmap-sync.yml) | Taxonomy files change on `master` + manual | Apply labels and reconcile the board's fields and items |
+| [`.github/workflows/roadmap-reconcile.yml`](https://github.com/TerrenoLabs/terreno/blob/master/.github/workflows/roadmap-reconcile.yml) | IP or task files change on `master` + manual | Advance status from IP headers, push to the board, regenerate `ROADMAP.md` |
 All three share the `roadmap` concurrency group. They write the same board, and interleaving
 them produces confusing partial states. After the group lock is acquired, each job refreshes
 to the latest branch HEAD so a queued `roadmap-sync` cannot overwrite statuses that
@@ -443,7 +463,7 @@ Two headers keep a plan out of that accounting:
 | Task file `**Status:** Closed` | The checklist is history — the IP finished by another route, so its unchecked boxes are not outstanding work and never contradict a `Shipped` status |
 
 Triage resolves the `area:*` label with
-[`scripts/issueAreaLabels.ts`](https://github.com/FlourishHealth/terreno/blob/master/scripts/issueAreaLabels.ts),
+[`scripts/issueAreaLabels.ts`](https://github.com/TerrenoLabs/terreno/blob/master/scripts/issueAreaLabels.ts),
 which owns the package-to-area table. Add new packages there, not in the workflow.
 
 Run the generator locally against the real board: