@bettercms-ai/mcp 0.83.2 → 0.83.4

package/dist/skills/bettercms/SKILL.md

@@ -199,7 +199,8 @@ Stop at the first step that is not clean, fix, then restart. A report that does
    `receipt.gate.nextAction` and read again after each batch; nothing else ends an imported
    site's setup, and an exception is recorded only for a reason that is true. The gate, its bars and the exceptions it accepts are in
    [finish-site.md](references/finish-site.md). Suggestions still in `missing` after that, and
-   owner actions, go in your final message by name.
+   owner actions, go in your final message by name. Before it, settle each `receipt.questions`
+   row: answer it if you are sure, else ask the owner in chat (finish-site.md).
 
 "Done" means the loop is clean and the gate reads complete, not that a tool call returned 200.
 `bettercms init` reads the gate again when you exit and prints its numbers per page, so the

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

@@ -259,6 +259,17 @@ Refused whatever the note says: `out-of-time`, `out-of-context`, `too-many-route
 `tool-failed`, `not-asked`, `good-enough`. A sentence to the user about a gap is not an
 exception either: the gate stays incomplete, and the CLI exits non-zero with that gap listed.
 
+### Setup questions: answer what you are sure of, ask the rest
+
+`get_next_steps` lists `receipt.questions`, and `get_editable_plan` the same `rows`: the choices
+the platform cannot make alone (which element is the logo, whether the header is one across
+pages, seeds, kit sections, the brand colours, what a body may hold). The dashboard does not ask
+them, and neither does `bettercms init`: you do. For each, explore the site. If you are confident,
+answer it yourself with `confirm_editable_plan` (the option's `decision`, unchanged) and tell the
+owner what you chose. If you are not sure, ask the owner in chat, its `options` as a choice with
+`recommended` first, and record their answer the same way. Never finish with an unsure one
+unasked.
+
 ### What setup derives on a collection's item pages
 
 Setup reads a few entry pages of each collection and makes one field of everything they render

package/package.json

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