@bettercms-ai/mcp 0.67.0 → 0.67.3

package/dist/index.js

@@ -2713,7 +2713,7 @@ var PARAM_TEXT = {
   sourceUrl: "instead of data: a public http(s) URL the server fetches and stores (private or internal addresses are refused)",
   focalX: "focal point, 0-1 across from the left edge; null resets to the centre",
   focalY: "focal point, 0-1 down from the top edge; null resets to the centre",
-  mergeHref: "pageId only: the link field paired with `path` (the label). Both become ONE `button` field keyed `key` (default: their stem, primaryCtaHref \u2192 primaryCta). Each entry's DRAFT gets {label, href} and keeps the old values; the live copy changes on publish. ifMatch is the page's version",
+  mergeHref: "pageId only: the link field paired with `path` (the label). Both become ONE `button` field keyed `key` (default: their stem, primaryCtaHref \u2192 primaryCta). Each entry's DRAFT gets {label, href} and keeps the old values; the live copy changes on publish. ifMatch is the page's version. 409 CODE_RENDERED_ROUTE: do its `next` recipe in code",
   confirmedInput: "true only after the user explicitly approved adding this custom input (`ui.input`); else setting or changing one is refused input_needs_confirmation. Removing one needs no approval"
 };
 var INPUT_CONFIRMED_HEADER = "x-bcms-confirmed-input";
@@ -5081,7 +5081,7 @@ ${res.warnings.join("\n")}` : summary, res.data);
       name: "get_page",
       config: {
         title: "Get a page (with its field schema)",
-        description: "Get one page INCLUDING its full field schema (keys, types, nested group/repeater children), pageType, `path` and `language`. Read this before set_page_content so you write correctly-keyed values, or before add_field so you know the existing keys.",
+        description: "Get one page INCLUDING its full field schema (keys, types, nested group/repeater children), pageType, `path` and `language`. A field with `stale: true` is one the build no longer renders: kept, hidden in the editor. Read this before set_page_content so you write correctly-keyed values, or before add_field so you know the existing keys.",
         inputSchema: getPageInput.shape
       },
       handler: guard(
@@ -5566,7 +5566,7 @@ ${notes.join("\n")}` : summary, created);
       name: "get_component",
       config: {
         title: "Get a component (with its blockJson)",
-        description: "Get one component by id INCLUDING its blockJson tree and props (with any stored `ui` authoring chrome on them). Read this before update_component so you keep the existing blocks, and after declaring field UI as the receipt that it landed \u2014 a prop absent here was not stored. " + VARIANT_GROUP_NOTE,
+        description: "Get one component by id INCLUDING its blockJson tree and props (with any stored `ui` authoring chrome on them; `stale: true` = no placement renders it). Read this before update_component so you keep the existing blocks, and after declaring field UI as the receipt that it landed \u2014 a prop absent here was not stored. " + VARIANT_GROUP_NOTE,
         inputSchema: getComponentInput.shape
       },
       handler: guard(
@@ -7031,7 +7031,13 @@ Do not stop at the plan or at a partial receipt \u2014 finish the whole site, ne
 8. \`get_binding_report\`: \`unmatched\` 0, \`unaddressable\` under 2% per route; fix the SOURCE, deploy, re-read (playbook \xA711).
 9. \`set_binding_mode { declaredBindings: true }\`, deploy AGAIN and poll, then confirm \`get_binding_report\`
    reads mode "declared", unmatched 0, bound above 0, \`coverage.pending\` empty. Send me that report.
-10. Ask me whether to commit and push to my repository, commit only, or leave it uncommitted (unpushed, the
+10. \`get_next_steps\`: if it lists \`upgrade-section-roots\` (section spacing and style handles), in the repo run
+   \`npx @bettercms-ai/convert@latest --upgrade-sections --root . --dry-run\`, read the plan, then run it for real. For every
+   root its receipt lists as \`skipped\`, pass the block down by hand: \`{...sectionRootAttrs(block)}\` on the section root, or
+   \`data-bcms-style=""\` plus \`style={...}\` from \`block.style\`. Run \`--verify-styles\` again and restore what it lists (the
+   marker and the inline style from \`block.style\` are allowed; changing a class or an existing style is not). Deploy,
+   poll, call \`get_next_steps\` again and tell me what it still lists. Not listed: say so and move on; invent no work.
+11. Ask me whether to commit and push to my repository, commit only, or leave it uncommitted (unpushed, the
    next rebuild from my repo drops it). Touch git only as I answer.`;
 var FIELD_UI_PROMPT = {
   title: "Declare how fields LOOK in the editor (guided)",