@bettercms-ai/mcp 0.78.1 → 0.79.1

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

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:

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".
@@ -85,8 +82,8 @@ convert the source, `submit_conversion_receipt` also returned complete.
    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 }`
+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

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.1",
+  "version": "0.79.1",
   "type": "module",
   "description": "BetterCMS MCP server — schema, content, forms + components authoring tools over the Management API, authed via OAuth device-code.",
   "bin": {