@bettercms-ai/mcp 0.65.1 → 0.66.0

package/dist/skills/bettercms/SKILL.md

@@ -81,6 +81,10 @@ These hold on every task. The reference in brackets has the detail and the codes
     CMS on a bound leaf and an edit shows in preview and after publish.
 12. **Bulk work runs as code, not as a chain of tool calls.** Propose the mapping and dry-run it
     before a high-volume write; use the MCP for state, targeted fixes and reports.
+13. **A build makes a site live, not editable.** It brings in SEO and meta, media, the brand and
+    the models `bcms-content.json` declares. Pages, collections, forms, bindings and components
+    are `editor_setup`'s: run it after an import or a rebuild (`get_deploy_status` `editorSetup`
+    `never` or `stale`). [getting-started.md]
 
 ## What you do, and what only the owner does
 

package/dist/skills/bettercms/references/componentize.md

@@ -30,7 +30,7 @@ Inside a section, pick the smallest shape that holds the children:
 
 Never let a component contain itself, directly or through a child.
 
-## 2. The componentize lane (a site whose pages were derived at import)
+## 2. The componentize lane (a site whose pages `editor_setup` derived)
 
 1. `get_componentize_plan { summary: true }` first (no values; the full plan is hundreds of KB,
    and `paged: true` reads it 10 pages at a time). It creates nothing and is computed live from
@@ -60,8 +60,10 @@ Never let a component contain itself, directly or through a child.
    `ALREADY_COMPONENTIZED`.
 5. `publish_component` for each, then publish the pages. An unpublished component renders
    nothing on the live site.
-6. In the repo, run the codemod with `--componentize` and a `--receipt` file, commit and push the
-   files it wrote, and hand that receipt verbatim to `submit_componentize_receipt`. It records
+6. The repository half. With no checkout, `componentize_sections { digest, codemod: true }` runs
+   the section-order codemod on the repo's own Actions (`skipped` means there is no repo it may
+   commit to). In a checkout, run the codemod with `--componentize` and a `--receipt` file, commit
+   and push the files it wrote, and hand that receipt verbatim to `submit_componentize_receipt`. It records
    each extracted section as the source of the component with the same slug, so no
    `set_component_source` per component is needed. Deploy.
 7. Output validation, from step 3 of §6.

package/dist/skills/bettercms/references/components.md

@@ -149,8 +149,15 @@ A code-built site ships only what its templates draw, whatever the page's `block
   editor reaches the live site only when the template loops over the page's blocks in order and
   each section root carries its block id as `data-bcms-block`. The codemod's `--componentize` pass
   generates `src/lib/bcms-sections.ts` for the loop and adds those attributes. Until it ships, the
-  editor locks Add section and reordering on that route, and `submit_conversion_receipt` keeps
+  editor still adds, moves, swaps and removes sections (saved, and drawn on the canvas at once),
+  tells the author that publishing leaves the live order to the site's code, and its "Let BetterCMS
+  control section order" button commits that same codemod to the connected repository. `submit_conversion_receipt` keeps
   `complete: false` with one `SECTIONS_UNSTAMPED` row per route.
+- **The order is measured, not assumed.** A release reads the stamped section roots in document order:
+  a build that draws them in the CMS order (`ordered: true` on the binding report's structure row)
+  owns nothing, whatever sections it has no code for; one that draws them in its own order
+  (`ordered: false`) — a template that hardcodes its bands and stamps each with a snapshot id — is
+  code-ordered as soon as the CMS order moves. Stamp ids only from the loop, never as literals.
 - **No chrome placements on a page.** A nav, footer or modal placement the site's layout draws
   renders nowhere, and the editor locks its outline row and skips it when it moves the sections
   around it. Remove it.
@@ -232,7 +239,7 @@ Components are organised into `component_groups` (the folders of the Components
   `Sections/<Page title>` (`Sections/<Page title>/<pattern>` for a template), and a dashboard or
   studio run leaves it unfiled. The receipt's `components.groups` lists the Groups it filed into.
   A reused component keeps its Group.
-- Sections a release imports are filed the same way, after the release.
+- Sections `editor_setup` componentizes are filed the same way.
 - `componentize_sections` reuses a component by identity and slug, never by family, so a
   hand-built `Hero / Split` is not picked for a derived hero band. Run `dryRun: true` and read
   `components.wouldDuplicate`: each id is an existing same-family component the run would sit a

package/dist/skills/bettercms/references/content-modeling.md

@@ -29,7 +29,9 @@ A page is `singleton` (one page and its own content: home, about, a legal page)
 Choose by repetition: a shape that repeats per item is a collection; a one-off is a singleton,
 even when it lists items, because the list page reads the collection. A dynamic page is its
 collection: the model and its entries both point at the page (`content_models.page_id`,
-`content_entries.page_id`), so never create a separate page per entry.
+`content_entries.page_id`), so never create a separate page per entry. A dynamic page made with
+`create_page` takes its route pattern and its collection through `update_page { dynamic:
+{ previewPath, modelId } }`: `/blog/{slug}`, and an existing collection with no page yet.
 
 | Source pattern | BetterCMS destination |
 |---|---|

package/dist/skills/bettercms/references/finish-site.md

@@ -69,6 +69,7 @@ and add the new result. Update the file as each row moves, so a reset loses at m
 
 | # | Step | Reference |
 |---|---|---|
+| 0 | Editor setup: `editor_setup { check: true }` reads `ready` for the live build (run `editor_setup` when it does not) | [getting-started.md](getting-started.md) |
 | 1 | Routing and data shape: page / collection / entry classification and folders; keep public URLs | [content-modeling.md](content-modeling.md) |
 | 2 | Sections and reuse: every band a section; dedupe compatible patterns into variants and overrides; nav and footer as globals (`get_componentize_plan`, `componentize_sections` on a components project) | [components.md](components.md), [componentize.md](componentize.md) |
 | 3 | Editor contract: field types, labels, validation, Portable Text accept lists, nested groups | [portable-text.md](portable-text.md) |

package/dist/skills/bettercms/references/forms-and-interactions.md

@@ -166,6 +166,7 @@ Rules:
 | List, read, create, update, delete forms | MCP: `list_forms`, `get_form`, `create_form`, `update_form`, `delete_form` |
 | Read and delete submissions | MCP: `list_form_submissions`, `delete_form_submission` |
 | Publish | MCP: `publish_form`. Unpublish: dashboard Forms tab |
+| Mark a derived form as not a form (a search box, a widget), or restore it | MCP: `update_form { ignored: true }` / `{ ignored: false }` |
 | Integrations (Google Sheets, Slack, webhook, email, HubSpot, Salesforce) | Dashboard |
 | Turnstile on/off, honeypot field name, notification emails | MCP: `create_form` / `update_form` (`turnstileEnabled`, `honeypotField`, `notifyEmails`). The Turnstile secret key: dashboard only; sending `turnstileSecretKey` through the API is refused with 403 `FORM_SECRET_DASHBOARD_ONLY` |
 

package/dist/skills/bettercms/references/getting-started.md

@@ -62,9 +62,13 @@ Everything else has a default. Do not ask about it; decide, then report what you
 
 ### Phase 3 — Convert and componentize
 
-Check: `submit_conversion_receipt` returned complete and `get_componentize_plan` proposes
-nothing more.
+Check: `editor_setup { check: true }` reads `ready`, `submit_conversion_receipt` returned complete
+and `get_componentize_plan` proposes nothing more.
 
+0. A build brings in only SEO and meta, media, the brand and the models `bcms-content.json`
+   declares. Pages, collections, forms, bindings and components come from `editor_setup`: run it
+   and poll `editor_setup { check: true }` until `ready` before anything below. Run it again
+   whenever `get_deploy_status` reports `editorSetup` `stale`.
 1. Explore the repo (the "Read when" column of SKILL.md's reference table names the signals) and
    read `get_site_composition`.
 2. If `list_env_vars` reports `missing` variables, run `npx @bettercms-ai/cli@latest env push`
@@ -75,8 +79,8 @@ nothing more.
 3. Run the `convert_site` prompt end to end. Its finish line is the only one; repeat until the
    receipt is complete, never stop at a partial one.
 4. When the answer was components: `get_componentize_plan`, confirm it with the user, apply it
-   with `componentize_sections`, then the repository half and `submit_componentize_receipt`
-   ([componentize.md](componentize.md)).
+   with `componentize_sections`, then the repository half (`componentize_sections { codemod: true }`
+   when there is no checkout) and `submit_componentize_receipt` ([componentize.md](componentize.md)).
 5. Work the rest through [finish-site.md](finish-site.md) (gap ledger, repair order, proof loop).
 
 ### Phase 4 — Publish and verify

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bettercms-ai/mcp",
-  "version": "0.65.1",
+  "version": "0.66.0",
   "type": "module",
   "description": "BetterCMS MCP server — schema, content, forms + components authoring tools over the Management API, authed via OAuth device-code.",
   "bin": {