@bettercms-ai/mcp 0.78.0 → 0.79.0

package/dist/kit-catalog.json

@@ -1,5 +1,152 @@
 {
  "$comment": "GENERATED from the dashboard's Kit Library (KIT_LIBRARY + EXAMPLES) by scripts/kit-export.ts. Do not edit. Regenerate (dashboard: bun run kit:export -- --backend <backend checkout>).",
+ "fieldConfig": {
+  "read": {
+   "*": [
+    "placeholder",
+    "zones",
+    "options",
+    "fields"
+   ],
+   "text": [
+    "minLength",
+    "maxLength",
+    "pattern",
+    "patternMessage",
+    "inputType"
+   ],
+   "longtext": [
+    "minLength",
+    "maxLength",
+    "pattern",
+    "patternMessage",
+    "inputType"
+   ],
+   "url": [
+    "minLength",
+    "maxLength",
+    "pattern",
+    "patternMessage",
+    "inputType"
+   ],
+   "richtext": [
+    "minLength",
+    "maxLength",
+    "pattern",
+    "patternMessage",
+    "inputType"
+   ],
+   "document": [
+    "minLength",
+    "maxLength",
+    "pattern",
+    "patternMessage",
+    "inputType"
+   ],
+   "number": [
+    "min",
+    "max",
+    "step",
+    "scale",
+    "unit",
+    "validation"
+   ],
+   "rating": [
+    "min",
+    "max",
+    "step",
+    "scale",
+    "unit",
+    "validation"
+   ],
+   "select": [
+    "multiSelect"
+   ],
+   "multiselect": [
+    "min",
+    "max",
+    "allowCustom"
+   ],
+   "tags": [
+    "min",
+    "max",
+    "allowCustom"
+   ],
+   "code": [
+    "language",
+    "languages"
+   ],
+   "date": [
+    "timezone",
+    "includeTime"
+   ],
+   "datetime": [
+    "timezone",
+    "includeTime"
+   ],
+   "reference": [
+    "contentModelId",
+    "polymorphic",
+    "allowedModelSlugs",
+    "targets",
+    "filter"
+   ],
+   "multi-reference": [
+    "contentModelId",
+    "polymorphic",
+    "allowedModelSlugs",
+    "targets",
+    "filter",
+    "min",
+    "max"
+   ],
+   "array": [
+    "itemType",
+    "minItems",
+    "maxItems",
+    "item"
+   ],
+   "image": [
+    "media"
+   ],
+   "modular": [
+    "blockSlugs",
+    "minItems",
+    "maxItems"
+   ]
+  },
+  "host": {
+   "any": [
+    "sectionLabel",
+    "sectionShape",
+    "sectionTitle",
+    "format"
+   ],
+   "richtext": [
+    "accept",
+    "allowMultipleParagraphs",
+    "inline",
+    "allowTargetBlank",
+    "components",
+    "hostTag",
+    "features"
+   ]
+  },
+  "server": [
+   "seeded",
+   "shared",
+   "sharedValue",
+   "attr",
+   "numeric",
+   "iconFont",
+   "htmlClasses",
+   "units",
+   "lead",
+   "band",
+   "family",
+   "shape"
+  ]
+ },
  "categories": [
   {
    "name": "Navigation & chrome",

package/dist/skills/bettercms/SKILL.md

@@ -57,8 +57,8 @@ Listing tools needs no sign-in; the first tool **call** does.
 These hold on every task. The reference in brackets has the detail and the codes.
 
 1. **Confirm the bound project before any write**: §9 of the schema playbook, then `get_project`.
-   Its `authoringPreference` (components, fields, or null while owed) is asked once, can be
-   re-answered, and is the user's answer, never yours.
+   Its `authoringPreference` defaults to components (recorded by a deploy, a promote or setup)
+   and is never asked; the owner can switch it to fields.
 2. **Never create SEO fields** (§5b). Page and entry meta are native columns. [seo.md]
 3. **A page is a list of sections**, never loose top-level blocks, and never a nav, footer or
    modal: chrome is the Layout. A call to action is one `button` field, never a text field
@@ -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/content-modeling.md

@@ -235,6 +235,11 @@ coverage as `help`. The platform writes a line only for the four reasons above a
 elements with none; clear the finding by running `editor_setup`, or by writing one of the four
 kinds yourself, never with filler.
 
+**Config keys.** Write only the `config` keys a field type documents (`maxLength`, `min`/`max`,
+`options`, `itemType`, `zones`, a rich text's `accept`/`inline`): any other key sends that field to
+the old classic editor. The import's own keys (`attr`, `numeric`, `units`, `band`, `seeded`, …) are the
+server's: both MCP surfaces drop them from what you write.
+
 ## 6. Changing a schema safely
 
 A schema write alone is not a release. Before one, read the model with `get_content_model`, a few
@@ -323,7 +328,7 @@ production cannot store it. Translate before the first write.
 | `boolean` | `boolean` | `boolean` |
 | `slug` | `slug` (an entry's own slug stays on the entry) | `text` |
 | `url`, `link` | `link` | `link`; `url` for a media or embed address |
-| `email`, `phone` | `email`, `phone` | `text` |
+| `email`, `phone` | `email`; a phone number is `text` with `richText: false` (`phone` opens only in the classic editor) | `text` |
 | `date`, `datetime` | `date`, `datetime` | `date` (`YYYY-MM-DD`); a datetime stays `text` |
 | `color` | `color` | `color` |
 | `select` | `select` | `select` with `config.options` |
@@ -341,14 +346,14 @@ production cannot store it. Translate before the first write.
 | `object` | `group` | `group` |
 | `array` of objects | `repeater`; item limits in `config.minItems` / `config.maxItems` (the editor shows "max N") | `table` |
 | `array` of strings | `array` (`itemType: "text"`) | `table` |
-| `array` of several item shapes | `modular` with `config.blockSlugs` (create the block models first) | separate components |
-| `slot` | `sections` or `component-ref` | `slot` (one instance; a list with `config.multiple`) |
+| `array` of several item shapes | one component per shape, placed as sections; on a model, a `repeater` whose rows carry each shape's fields (`modular` opens only in the classic editor) | separate components |
+| `slot` | components placed on the page (componentize); never a `sections` or `component-ref` field, which the page form cannot edit | `slot` (one instance; a list with `config.multiple`) |
 | a form `reference` | a `form` block inside the section | `form` |
 
 V2 features with no production shape are dropped and reported, never faked: a per-cell table
 type, per-breakpoint values (only `style.hideOn` differs by breakpoint) and per-field
 localization. Two have a shape now: typed table columns are a `repeater` with one field per column
-and `ui.layout: "table"`, and a slot with several children is a `slot` prop with `config.multiple`
+(never `ui.layout: "table"`, which the editor cannot draw), and a slot with several children is a `slot` prop with `config.multiple`
 ([components.md](components.md) §1).
 
 | The plan says | Production word |
@@ -362,7 +367,7 @@ and `ui.layout: "table"`, and a slot with several children is a `slot` prop with
 | Variant, layout | Components sharing one `sectionType` ([components.md](components.md)) |
 | Listing | `collection` block (§4) |
 | Picks | `multi-reference` |
-| Polymorphic array, modules | `modular` field |
+| Polymorphic array, modules | one component per shape |
 
 Tools and reports use the production word. Labels and help an editor reads never say
 "document": the `document` field is labelled Body.

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

@@ -87,9 +87,11 @@ its number, a `fixCode` and a `fix`, the call that closes it.
 (`fixCode`, `count`, the `fix` of its first row, the first `routes`), two with the same count in a
 fixed order. Run it on every row that carries that `fixCode`, call `get_next_steps`, and repeat
 until `complete`: following it reaches `complete` with no step that changes nothing. A fix no
-tool can make is named only when nothing else is left. A `fix` of `null` means no tool closes that row (a collection's listing
-route, a URL that cannot be placed, two pages nobody but the owner can choose between): put it to
-the user and stop retrying. Treat a row that its fix did not move the same way.
+tool can make is named only when nothing else is left. A `fix` of `null` means no tool closes that row by itself: its
+`detail` names what to change in the site's code, so change it, commit, push and `rebuild_project`.
+Only a collection's listing route, a URL that cannot be placed and two pages nobody but the owner
+can choose between are left; record each as an exception with a true reason, never stop to ask. A
+row its fix did not move twice is recorded the same way.
 
 A `sections` or `style` row is a page nobody can add a section to, reorder or space, however
 complete its copy is. Its `fixCode` names the one fix, and `fix` the call when a tool can make it:
@@ -97,8 +99,8 @@ complete its copy is. Its `fixCode` names the one fix, and `fix` the call when a
 | `fixCode` | The fix |
 |---|---|
 | `run-sections-conversion` | Only the site's code can draw this page's sections: its app renders the route, a framework hydrates the page whole (`PAGE_HYDRATED`), or the release could not map its bands. In a checkout run `npx @bettercms-ai/convert@latest --sections --root .` ([componentize.md](componentize.md) §5), or call `componentize_sections` with `codemod: true` and the plan's `digest`; `--upgrade-sections` for a `style` row. Then push and release |
-| `rebuild` | The build that serves is older than what makes the row pass: a published section, the wrap's commit (`wrap: "wrapped"` on a row that still fails), or the in-place switch. No tool starts one: ask the user to push and Rebuild |
-| `enable-in-place-structure` | A static page the release can write by itself, and the project's in-place structure switch is off. Setup switches it on for a project it creates; on an existing one it is the operator's call. No repository change |
+| `rebuild` | The build that serves is older than what makes the row pass: a published section, the wrap's commit (`wrap: "wrapped"` on a row that still fails), or the in-place switch. Push what changed, then `rebuild_project` and `get_deploy_status { waitSeconds: 50 }` until it is live |
+| `enable-in-place-structure` | A static page the release can write by itself, and the project's in-place structure switch is off. Setup switches it on for a project it creates; on an existing one, `update_project { structureInPlace: true }`. No repository change |
 | `run-setup` | Nothing measured what the row reads, or a page is still to register: `editor_setup { force: true }`, then read again |
 
 The other rows name their fix the same way:
@@ -189,7 +191,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 +205,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

@@ -11,11 +11,9 @@ for what it leaves out.
 
 ## Communication style
 
-Be succinct. Say what you did ("Converted 12 routes; 3 values still unmatched on /pricing"), ask
-direct questions, and skip narrating what you are about to do. Give numbers, not adjectives.
-
-Before starting, tell the user they can pause and resume anytime by saying
-**"Continue BetterCMS setup"**.
+Be succinct. Say what you did ("Converted 12 routes; 3 values still unmatched on /pricing") and
+skip narrating what you are about to do. Give numbers, not adjectives. Finish the setup in this
+run: do not stop to ask anything the sections below give an answer for.
 
 **RESUME TRIGGER.** On "Continue BetterCMS setup", read `get_project`, `get_next_steps` and
 `get_binding_report` for the project and the gap ledger at `.bettercms/ledger.json` if it exists,
@@ -42,17 +40,16 @@ Check: the MCP answers for this project id, and this folder is its repo.
      added while you run loads only when the agent starts, and every step below works on that
      folder's source.
 
-### Phase 2 — The questions the MCP requires, and no others
-
-Check: `get_project` shows `authoringPreference` set and the user has answered media delivery.
+### Phase 2 — No questions: the defaults are recorded
 
-Ask exactly these two, each through its tool, and never answer them yourself:
+Nothing here is asked. Record and report:
 
-1. **Authoring**: `set_authoring_preference` (components or fields). Recommend components for a
-   marketing site. It is asked once per project and can be re-answered.
-2. **Media delivery**: `set_media_delivery` (the BetterCMS CDN, recommended, or the API origin).
+1. **Authoring**: components. A deploy, a promote and every `editor_setup` record it when nothing
+   is set; call `set_authoring_preference` only if the prompt you were started with names `fields`.
+2. **Media delivery**: the BetterCMS CDN, the project's default. Leave it.
+3. **Git**: the prompt you were started with says whether you may push. Follow it; never ask.
 
-Everything else has a default. Do not ask about it; decide, then report what you decided:
+Everything else has a default too. Do not ask about it; decide, then report what you decided:
 
 - **Scope is the whole site**: every page, section, heading, paragraph, list item, link and image
   the site renders. Not the home page first, not "the main copy".
@@ -62,8 +59,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,10 +77,13 @@ 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.
-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 }`
+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. With components recorded: `get_componentize_plan`, then apply it with
+   `componentize_sections` (the owner can undo it), 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).
    The gate's `sections` and `style` rows are part of it: a setup whose pages cannot take a new
@@ -96,8 +97,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/dist/skills/bettercms/references/site-blueprints.md

@@ -122,11 +122,11 @@ every entry and are not repeated in the tables. SEO fields are never listed.
 | Map pin | `location` (lat, lng, optional label). Never two text fields |
 | Tags, amenities, bullet lists | `array` with `itemType: "text"`. One choice from a fixed list is `select` |
 | Rows of the same shape (hours, facts, metrics, tickets) | `repeater` of `text`, `number`, `select`, `boolean` children |
-| Mixed ordered blocks in a case study | `modular` |
+| Mixed ordered blocks in a case study | one component per block shape, placed as sections |
 | One or many other entries | `reference`, `multi-reference`. A missing target is refused on write |
-| Call to action | `button` (label and link in one value). A bare link is `link`; also `email`, `phone` |
+| Call to action | `button` (label and link in one value). A bare link is `link`; also `email`; a phone number is `text` |
 | Date, date and time | `date`, `datetime`. Keep the zone as a `text` IANA name beside it when the site shows times |
-| A spec or comparison table | `repeater` with one field per column (any field type) and `ui.layout: "table"`. There is no separate table field type |
+| A spec or comparison table | `repeater` with one field per column (any field type). There is no separate table field type |
 
 An external system's id (`"store_product_id"`, `"ats_job_id"`, `"feed_id"`, `"lms_course_id"`)
 is a `text` field kept as migration metadata and locked: `readOnly: "developer"` with a
@@ -261,7 +261,7 @@ Projects collection, `urlPattern` `/work/:slug` (or the established prefix):
 | `"year"` | `number` | |
 | `"services"` | `multi-reference` to Services, or `array` of text | References when service pages exist |
 | `"cover_image"`, `"excerpt"` | `image`, `longtext` | Words baked into a hero image move into fields |
-| `"modules"` or `"body"` | `modular`, or `document` | `modular` (text, image, gallery, quote, video, stats blocks) for image-led studies; `document` when mostly prose |
+| `"modules"` or `"body"` | components, or `document` | one component per block (text, image, gallery, quote, video, stats) for image-led studies; `document` when mostly prose |
 | `"results"` | `repeater`: `"value"`, `"label"` | Only verified outcomes |
 | `"credits"` | `repeater`: `"role"`, `"name"` | |
 | `"testimonial"` | `reference` to Testimonials | |

package/dist/skills/bettercms/references/write-limits.md

@@ -207,7 +207,6 @@ write new rich text in that shape.
 | 409 `unique_conflict` | Another entry already holds this value in a unique field. `conflicts` names it | Match to that entry and update it; do not create a twin |
 | 409 `locale_conflict` | The translation group already has an entry in that locale. `errors` names `locale` or `translationOf` | Edit the existing translation |
 | 409 `Version conflict` (entries), `VERSION_CONFLICT` (sidebar, section zones) | Someone wrote since your read. The entry body carries `currentVersion` | Read again, re-apply your change to the fresh value, write with the new version |
-| 409 `AUTHORING_DECISION_REQUIRED` | Deploy or promote was called before a human chose components or fields. `message` is the question | Ask the user, then `set_authoring_preference`. Do not retry or route around it |
 | 409 `stale-plan` | The site changed after the componentize plan was read; `digest` is the current one | `get_componentize_plan` again, re-confirm, resubmit with the new digest |
 | 409 `style-edits` | The conversion receipt lists changed classes or styles. `styleEdits` holds up to 40 tokens | Restore every token, rerun `npx @bettercms-ai/convert --verify-styles`, resubmit the receipt |
 | 400 `digest-mismatch` | The receipt was built for a different brief | Read the brief again and rebuild the receipt against it |

package/package.json

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