@bettercms-ai/mcp 0.78.0 → 0.78.1

package/dist/skills/bettercms/SKILL.md

@@ -186,8 +186,8 @@ Stop at the first step that is not clean, fix, then restart. A report that does
 
 1. **Fetch the live URL**, cache-busted: a 200 whose body contains copy you just published. The
    steps below read the control plane, and all of them can be green on a site that answers 404.
-2. `get_binding_report` for every route you touched: `coverage.pending` empty, and
-   `mode: "declared"` on a declared site. `refreshReason: "never-generated"` means no BetterCMS
+2. `get_binding_report` for every route you touched: `unaddressable` under 2%, and, where the
+   source declares its bindings, `coverage.pending` empty and `mode: "declared"`. `refreshReason: "never-generated"` means no BetterCMS
    release wrote one (on headless none ever will, so step 1 is the proof); `"outdated"` means
    the next release rewrites it.
 3. `get_site_composition`: every page you touched is made of sections, with the intended

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

@@ -265,7 +265,7 @@ Check: change the bound string, publish, reload: the drawn text reads the new va
 ## 12. In the editor's canvas
 
 The Visual Editor shows the real page with its scripts running, and owns three things there: the
-scroll (its canvas scrolls and the page's window follows), the pointer (a click selects a field)
+scroll (the page scrolls its own window, as it does live), the pointer (a click selects a field)
 and the place on the page (picking a field in the panel scrolls to it). Motion that reads the
 window's scroll or the clock runs there as it does live. Only what takes one of those three away
 has to stand down, and the site decides that with one question:
@@ -284,7 +284,7 @@ canvas, and false on the published page. What each kind of page does there:
 | Native scroll, CSS scroll-driven animations (`animation-timeline`), Motion `useScroll` / `whileInView`, ScrollTrigger pin and scrub | runs as live | nothing |
 | Lenis, Locomotive Scroll 5 | runs; the wheel has no easing (section 6) | nothing |
 | GSAP ScrollSmoother | runs; the window still scrolls, the content eases behind it | nothing |
-| Locomotive Scroll 4, any script that locks the window and moves the content by a transform | the page works under its own wheel, but the canvas cannot scroll it and a field picked in the panel is not brought into view | `smooth: !inEditor()`, so the window scrolls |
+| Locomotive Scroll 4, any script that locks the window and moves the content by a transform | the page works under its own wheel, but the editor cannot scroll it and a field picked in the panel is not brought into view | `smooth: !inEditor()`, so the window scrolls |
 | A wheel-driven slide deck (GSAP `Observer`, fullPage) | the same | do not create the observer when `inEditor()`; let the sections stack and scroll |
 | A scene with its own scroll layer (react-three-fiber `ScrollControls`, a fixed `overflow: auto` layer) | runs; picking a field scrolls that layer | nothing |
 | An intro or preloader that holds the page (`overflow: hidden` until it ends, a full-screen cover) | plays on every reload of the canvas, and covers the page while it does | skip it when `inEditor()` |
@@ -292,5 +292,5 @@ canvas, and false on the published page. What each kind of page does there:
 Never use `inEditor()` to change what a field renders, to hide a section or to stop a timeline:
 the canvas must show what a visitor gets. It is for scroll takeover, intros and nothing else.
 
-Check: open the page in the Visual Editor, scroll with the wheel, drag the canvas scrollbar to the
+Check: open the page in the Visual Editor, scroll with the wheel, drag the page's scrollbar to the
 footer, then pick a field of the first section in the panel: the canvas returns to it.

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

@@ -189,7 +189,8 @@ Where the markup says no more it numbers them (`Pricing text 4`, `Hero image 2`)
 whose classes name nothing is called by its heading's words. No build can say that a picture is
 the dashboard screenshot; the site's code can. So these never hold the gate open: they are
 `receipt.gate.naming`, and `get_next_steps` lists the step `names-from-code` until each is
-renamed. Do it in the same job, after the gate's own rows: an editor reads these names all day.
+renamed. Do it in the same job, after the gate's own rows and before the final report: an
+editor reads these names all day, and a setup that leaves them is not finished.
 
 Name from the site's code, the way a developer writes a schema. Open the section's source file
 and use what it calls things (`plan.cents`, `billingFrequency`, `StatsBand.astro`):
@@ -202,12 +203,13 @@ and use what it calls things (`plan.cents`, `billingFrequency`, `StatsBand.astro
 | A field or prop | what it HOLDS there, one to three words | `Dismiss key`, `Starter plan price`, `Dashboard screenshot`, `Billing frequency` | its own copy, a role with a number (`Text 4`), the section's name alone |
 | Help text | most fields get none. One plain sentence under 90 characters, only for a format or unit, a place the canvas cannot show, a real constraint or a fallback. No semicolons, no dashes, no values from the page | `Leave empty to use the page title.` | the label or the value said again, writing advice, a figure copied from another page |
 
-**Advice is not work left.** `receipt.gate.advice`, `gate.families`, `gate.kit` and `gate.naming`
+**Advice is not work left**, except the names. `gate.naming` is part of the job: rename every
+row before you report, as above. `receipt.gate.advice`, `gate.families` and `gate.kit`
 are things a person may want to change about the site's own content or build: a title longer than
 a search result shows, no default share image, an element outside any section, a route family that
 could be a collection, a kit entry to confirm, a name to sharpen. The site is fully editable with
-every one of them standing. When `gate.complete` is true the setup is DONE: say so, list the
-advice in a few lines as optional improvements, and never call any of it pending, blocked,
+every one of them standing. When `gate.complete` is true and `gate.naming` is absent or empty the setup is
+DONE: say so, list the advice in a few lines as optional improvements, and never call any of it pending, blocked,
 remaining or left over, and never end on a question about it.
 
 A section says two things: what it IS (its kind) and what it SAYS (its title). Only the kind is

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

@@ -62,8 +62,9 @@ Everything else has a default. Do not ask about it; decide, then report what you
 
 ### Phase 3 — Convert and componentize
 
-Check: `editor_setup { check: true }` reads `ready`, `submit_conversion_receipt` returned complete
-and `get_componentize_plan` proposes nothing more.
+Check: `editor_setup { check: true }` reads `ready`, `get_next_steps` returns
+`receipt.complete: true` and `get_componentize_plan` proposes nothing more. Where the job was to
+convert the source, `submit_conversion_receipt` also returned complete.
 
 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
@@ -79,8 +80,11 @@ and `get_componentize_plan` proposes nothing more.
    through you. If they are not found there and the site loads its content from another CMS,
    move that content into BetterCMS ([external-content.md](external-content.md)). Never ask the
    user for a key or read one: a site left depending on missing keys renders empty or crashes.
-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.
+3. Work from `get_next_steps`: run `receipt.gate.nextAction`, read it again after each batch, and
+   repeat until `receipt.complete` is true. On a site set up from its build that gate is the only
+   finish line. Run the `convert_site` prompt only when the job is to convert the source (the gate
+   asks for it, the owner wants the code to declare its bindings, or the project is headless), and
+   then to its own complete receipt, never 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 (`componentize_sections { codemod: true }`
    when there is no checkout) and `submit_componentize_receipt` ([componentize.md](componentize.md)).
@@ -96,8 +100,9 @@ Check: the deployed site passes the numbers below on every route.
 
 1. Deploy the way this project deploys: `deploy_project` on BetterCMS hosting; on a headless
    project, push to the repo its host builds (never `deploy_project` there).
-2. `get_binding_report` is the finish line: zero unmatched, an empty `coverage.pending`, and
-   `unaddressable` below 2% on each route. `refreshReason: "never-generated"` on headless means
+2. `get_next_steps` reading `receipt.complete: true` is the finish line. `get_binding_report`
+   says why a route is short of it: `unaddressable` below 2% on each route, and, on a source you
+   converted, zero unmatched and an empty `coverage.pending`. `refreshReason: "never-generated"` on headless means
    fetch the live site instead.
 3. Run the verify loop in SKILL.md against the live URL, then the two-path smoke test (click
    through to a detail page, clean console, direct reload) in [frameworks.md](frameworks.md)

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

@@ -266,7 +266,7 @@ for a content value the sync got wrong is §4.
 | Need | Surface | Owner |
 |---|---|---|
 | Rebuild or revalidate a site on publish | The publish webhook, signed `X-BetterCMS-Signature` (HMAC-SHA256 of the raw body) with the project's webhook secret ([frameworks.md](frameworks.md) Revalidation) | Secret set in the dashboard; your route verifies it |
-| Notify another system of an event | Event webhooks, `list_webhooks` / `create_webhook`: `content.publish`, `content.unpublish`, `content.stage_changed` (workflow stage), `content.created`, `content.updated`, `content.deleted` and `deployment.triggered`; HMAC-SHA256 signed in `X-BetterCMS-Signature`; payloads carry ids, never content. The signing `secret` is returned ONCE, on create. A receiver that writes back on `content.updated` loops unless it skips its own writes. Per-subscription payload filters: dashboard | You |
+| Notify another system of an event | Event webhooks, `list_webhooks` / `create_webhook`: `content.publish`, `content.unpublish`, `content.stage_changed` (workflow stage), `content.created`, `content.updated`, `content.deleted` and `deployment.triggered`; HMAC-SHA256 signed in `X-BetterCMS-Signature`; payloads carry ids, never content: an entry's `content.publish`/`content.unpublish` carries `data.entryId`, a page's carries `data.pageId` and `kind: "page"` (so `entryId` is not always present). The signing `secret` is returned ONCE, on create. A receiver that writes back on `content.updated` loops unless it skips its own writes. Per-subscription payload filters: dashboard | You |
 | Send form submissions somewhere | Per-form integrations: Google Sheets, Slack, a webhook, email | Dashboard only |
 | Go live or retire at a time | `scheduledAt` (publish a draft at a time; needs publish permission) and `unpublishAt` (return a published row to draft) on `update_content_entry` and `update_page`; `null` cancels either. Campaigns: `publish_campaign` takes both | You. An edit that omits `scheduledAt` CANCELS the pending publish, so resend it with every edit before it fires; omitting `unpublishAt` never cancels it |
 | Show one section only for a period | `window` `{ from?, until? }` on a page block (`update_page` `blockJson`) or on a Layout Section (`update_layout` `add-section`, `update-section`). Shown from `from` until `until`; each is an ISO 8601 datetime with an offset (`2026-11-27T00:00:00+01:00`), stored as UTC, and either may be left out. `null` clears it. Refusals: `invalid_window` (no offset, or not a date), `window_inverted` (`from` not before `until`), `window_in_component` (inside a component's `blockJson`: put it on the placement), `window_in_entry` (on a block inside an entry's sections value: put it on the page block or Layout Section that shows the entry). A Section a page adds or customizes takes a window like a Global one | You. Outside its window the block is in no published output: the page, its Markdown, the delivery API and search. A draft preview draws it, marked. A page BetterCMS renders per request changes at the boundary; a static site catches up within about a minute, in place when a section goes and with a build when one appears. Site code that renders its own header ignores a Section's window |

package/package.json

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