@bettercms-ai/mcp 0.59.2 → 0.61.0

package/dist/index.js

@@ -2268,15 +2268,19 @@ var uiObject = z.object({
   collapsed: z.boolean().optional().describe("start this panel collapsed. Use it for long optional sections."),
   preview: z.object({
     title: z.string().min(1).optional().describe("CHILD KEY whose value titles a collapsed row"),
+    subtitle: z.string().min(1).optional().describe("CHILD KEY whose value is the row's second line (e.g. 'level' \u2192 'Heading \xB7 h2')"),
     media: z.string().min(1).optional().describe("CHILD KEY whose value is the row's thumbnail (image/file/url all work)")
   }).optional().describe(
-    "how ONE ITEM summarises itself when collapsed. Both slots name a CHILD KEY of THIS field/prop \u2014 not a value, not a dotted path. Without it a repeater of testimonials reads 'Item 1, Item 2, Item 3'; with {title:'author', media:'avatar'} it reads the names with their faces."
+    "how ONE ITEM summarises itself when collapsed. Every slot names a CHILD KEY of THIS field/prop \u2014 not a value, not a dotted path. Without it a repeater of testimonials reads 'Item 1, Item 2, Item 3'; with {title:'author', media:'avatar'} it reads the names with their faces."
   ),
   layout: z.enum(["list", "grid"]).optional().describe(
     "how the ITEMS are arranged. Omit (\u2261 'list') for rows of text; 'grid' for items whose thumbnail is the thing you scan \u2014 a gallery, a logo wall, a team. Same placement rule as `preview`."
   ),
   reorderable: z.boolean().optional().describe(
     "omit (\u2261 true) unless the order is PART OF THE MEANING. `false` LOCKS the list \u2014 a 'three steps' band that must stay three steps in that order, a nav whose order is semantic, a timeline. Valid only where there is a list to lock."
+  ),
+  control: z.enum(["segmented", "slider"]).optional().describe(
+    "editor control for a LEAF. Omit for the default. 'segmented' on a select with a few short options (alignment, theme, size); 'slider' on a number that has config.min < config.max (opacity, columns). Anything else is refused with the rule named."
   )
 });
 var fieldShape = {
@@ -2976,6 +2980,7 @@ function buildToolDefs(deps) {
     category: componentCategory.optional().describe("defaults to 'custom'"),
     group: z.string().min(1).max(100).optional().describe("the folder editors see in the dashboard's Components tab, addressed by NAME (e.g. 'Sections', 'Navigation', 'Forms'). Resolved against this project's Groups and CREATED when missing, so a whole-site run can file everything without looking any id up first. Separate from `category`, which is the picker tab."),
     sectionType: sectionType.optional(),
+    variantOf: z.string().min(1).max(255).optional().describe("id/slug of the component this is a VARIANT of: joins or starts its family (422 if its shared inputs are missing)"),
     projectId: z.string().nullable().optional().describe("owning project id; null creates a workspace-wide global component"),
     allowedOn: allowedOn.optional(),
     description: z.string().optional(),
@@ -2992,6 +2997,7 @@ function buildToolDefs(deps) {
     sectionType: sectionType.nullable().optional().describe(
       "null demotes it to an ordinary component \u2014 it disappears from the 'Add a section' picker, and instances already placed keep rendering but lose their section chrome and variant switcher"
     ),
+    variantOf: z.string().min(1).max(255).optional().describe("see create_component"),
     allowedOn: allowedOn.optional().describe("REPLACES the placement allowlist"),
     description: z.string().optional(),
     blockJson: z.array(blockObject).optional().describe("REPLACES the block tree"),
@@ -4718,7 +4724,7 @@ ${notes.join("\n")}` : summary, created);
       name: "create_component",
       config: {
         title: "Create a reusable component",
-        description: "Create a reusable component from a blockJson tree. THIS IS ALSO HOW A PAGE GETS ITS SECTIONS: set `sectionType` (e.g. 'Hero') and the component becomes a placeable section, selectable in the editor's 'Add a section' picker. Components sharing a `sectionType` are its layout VARIANTS \u2014 one Hero with a 'Centered' and a 'Two-column' variant, same prop keys, so a swap keeps the content. CONFIRM the structure with the user first. blockJson is an array of blocks \u2014 the same set create_page accepts (heading, text/richtext, image, button, spacer, video, columns, section, slider, tabs, navbar, footer, form, component, collection), NOT a narrower one; `section` nests child blocks in props.children and `columns` in props.columns. `props` declares overridable fields. Returns the new id \u2014 render with `<BcmsBlocks>`. Always lands as a DRAFT \u2014 call publish_component to put it on the live site; until then it renders as NOTHING there, with no error. " + SECTION_DOCTRINE,
+        description: "Create a reusable component from a blockJson tree. THIS IS ALSO HOW A PAGE GETS ITS SECTIONS: set `sectionType` (e.g. 'Hero') and the component becomes a placeable section, selectable in the editor's 'Add a section' picker. Components sharing a `sectionType` are its layout VARIANTS \u2014 one Hero with a 'Centered' and a 'Two-column' variant, same prop keys, so a swap keeps the content. CONFIRM the structure with the user first. blockJson is an array of blocks \u2014 the same set create_page accepts (heading, text/richtext, image, button, spacer, video, columns, section, slider, tabs, navbar, footer, form, component, collection), NOT a narrower one; `section` nests child blocks in props.children and `columns` in props.columns. `props` declares overridable fields. Returns the new id \u2014 render with `<BcmsBlocks>`. Always lands as a DRAFT \u2014 call publish_component to put it on the live site; until then it renders as NOTHING there, with no error.  Buttons auto-join the project's Button family; section buttons link to its looks." + SECTION_DOCTRINE,
         inputSchema: createComponentInput.shape
       },
       handler: guard(
@@ -5033,7 +5039,7 @@ ${lines.join("\n")}`, found);
       name: "duplicate_component",
       config: {
         title: "Add a look to a component family",
-        description: "Add a new LOOK to a component's variant family (\"+ New variant\"), e.g. a Ghost button the site does not have: copy the component into the same family and folder under `name`, with a new unique slug. `preset` restyles its button block: primary / secondary fill it with the brand kit's primary / accent colour; ghost drops the fill and border, keeps the padding and colours the text with the old fill; link is a ghost with no padding. Omit `preset` for a plain copy. outline drops the fill, keeps the padding and draws a border all round in the old fill's colour, which becomes the text colour. A look the style vocabulary cannot express is refused with 422 and the reason \u2014 relay it, never approximate it with update_component. 409 means that name is already a look in the family. When the family's contract is published and this connection may publish, the new look is published at once and is choosable in every section's style select; otherwise it is a draft: call publish_component.",
+        description: "Add a new LOOK to a component's variant family (\"+ New variant\"), e.g. a Ghost button the site does not have: copy the component into the same family and folder under `name`, with a new unique slug. `preset` restyles its button block: primary / secondary fill it with the brand kit's primary / accent colour; ghost drops the fill and border, keeps the padding and colours the text with the old fill; link is a ghost with no padding. Omit `preset` for a plain copy. Starts a family if none. outline drops the fill, keeps the padding and draws a border all round in the old fill's colour, which becomes the text colour. A look the style vocabulary cannot express is refused with 422 and the reason \u2014 relay it, never approximate it with update_component. 409 means that name is already a look in the family. When the family's contract is published and this connection may publish, the new look is published at once and is choosable in every section's style select; otherwise it is a draft: call publish_component.",
         inputSchema: duplicateComponentInput.shape
       },
       handler: guard(
@@ -5896,8 +5902,8 @@ delivered value \u2014 they change editor chrome only.
   BARE KEY, and the key namespace is FLAT across the model (\xA7 the duplicate-key rule), so the
   key you reference must exist.
 - **\`ui.collapsed\`** \u2014 start a nesting field's panel closed. For long optional sections.
-- **\`ui.preview\`** \u2014 how ONE ITEM of a nesting field summarises itself when collapsed. Both
-  slots name a **CHILD FIELD KEY of that field** \u2014 not a value, not a dotted path.
+- **\`ui.preview\`** \u2014 how ONE ITEM of a nesting field summarises itself when collapsed. Each
+  slot (\`title\`, \`subtitle\`, \`media\`) names a **CHILD FIELD KEY of that field** \u2014 not a value, not a dotted path.
   Without it a repeater of ten testimonials reads "Item 1 \u2026 Item 10" and the author has to open
   each one to find the one they meant. \`media\` may point at an \`image\`, \`file\` or url-ish
   \`text\` child; the type is not constrained.
@@ -5909,19 +5915,25 @@ delivered value \u2014 they change editor chrome only.
   in that order, a nav whose order is semantic, a timeline. Locking a list nobody should reorder
   is the declaration there was previously no way to make; locking one out of tidiness takes a
   capability away from the author, so do not set it "just in case".
+- **\`ui.control\`** \u2014 which control a LEAF edits with; omit it for the default. \`'segmented'\` on a
+  \`select\` with a few short options (alignment, theme, size: one click instead of a dropdown);
+  \`'slider'\` on a \`number\` with \`config.min\` < \`config.max\` (opacity, columns). Anywhere else it
+  is refused with the rule named.
 
-**Five refusals, all deliberate, all 400 with the fix in the message.**
+**Six refusals, all deliberate, all 400 with the fix in the message.**
 1. An unknown key inside \`ui\` is REJECTED, not stripped. \`ui\` is a strict object precisely so
    that a typo is a refusal you can read instead of a 200 with your declaration gone.
 2. \`ui.preview\` on a LEAF field is refused \u2014 it summarises an item, and a leaf has no items.
    Valid on \`group\`, \`repeater\`, an \`array\` with \`config.zones\`, or \`modular\`.
-3. \`preview.title\` / \`preview.media\` naming a key that is not a child of that field is refused,
+3. \`preview.title\` / \`preview.subtitle\` / \`preview.media\` naming a key that is not a child of that field is refused,
    and the error lists the valid child keys.
 4. \`ui.layout\` follows the same rule as \`preview\`: nesting fields only. A leaf has no items
    to arrange.
 5. \`ui.reorderable\` is STRICTER \u2014 it needs a LIST, not merely children. Valid on \`repeater\`,
    an \`array\` with \`config.zones.repeatable\`, or \`modular\`. A \`group\` (and a non-repeatable
    zone) holds exactly ONE item, so there is nothing there to drag and the write is refused.
+6. \`ui.control\` outside its fit is refused: \`segmented\` needs a \`select\`, \`slider\` a \`number\`
+   whose \`config.min\` and \`config.max\` are both set with min < max.
 
 **The same \`ui\` rides on COMPONENT PROPS.** \`create_component\` / \`update_component\` take it on
 each entry of \`props\`, with the placement rules the prop vocabulary implies: \`preview\` and
@@ -6583,9 +6595,10 @@ Read bettercms://playbook/schema section 14 first \u2014 it has the exact prop s
 **What you are setting** (all of these ride on any field, on create_content_model / create_page /
 add_field / add_page_field; none of them affect delivery):
   ui.collapsed              start a nesting field's panel closed
-  ui.preview {title,media}  which CHILD FIELD KEY titles a collapsed row, and which is its thumb
+  ui.preview {title,subtitle,media}  which CHILD FIELD KEY titles a collapsed row, its second line, its thumb
   ui.layout 'list'|'grid'|'table'   how its items are arranged; table is for repeatable row schemas; omit for list
   ui.reorderable            omit (= true) unless the ORDER IS THE MEANING; false LOCKS the list
+  ui.control 'segmented'|'slider'   a LEAF's control: segmented on a select, slider on a number with config.min < max
   helpText                  one line under the field: what to WRITE here
   showIf                    hide a field until another field has a value