@bettercms-ai/mcp 0.75.0 → 0.76.0

package/dist/index.js

@@ -3005,6 +3005,7 @@ var PARAM_TEXT = {
   componentPreview: "a slot row's look: {title?, subtitle?, media?} TOP-LEVEL prop keys, fallback?, icon?; null clears. \xA73 of bettercms://playbook/schema",
   componentIcon: "the block icon, a dock icon name; null clears. \xA73 of bettercms://playbook/schema",
   componentTabs: "/kit tabs no top-level prop sits in: [{id,label,icon?,order?}]. \xA73 of bettercms://playbook/schema",
+  componentKitEntry: "the bettercms://kit entry id its V2 dock UI follows (422 kit_entry_unknown otherwise); null clears. The setup gate's dock row needs one",
   describes: "for editors: what it is and holds; omitted: written for you",
   runtimeBundle: "instead of pageId: the server-app bundle cleanup",
   pageRef: "page id or path ('/de/about'); a bare slug only when one page has it",
@@ -4114,6 +4115,7 @@ function buildToolDefs(deps) {
     preview: componentPreviewArg.optional(),
     icon: dockIconArg.nullable().optional().describe(PARAM_TEXT.componentIcon),
     tabs: z.array(z.object({ id: z.string(), label: z.string(), icon: z.string().optional(), order: z.number().int().optional() })).nullable().optional().describe(PARAM_TEXT.componentTabs),
+    kitEntry: z.string().min(1).max(100).nullable().optional().describe(PARAM_TEXT.componentKitEntry),
     blockJson: z.array(blockObject).default([]).describe("the component's block tree"),
     props: z.array(componentPropObject).default([]).describe(
       "overridable fields. DECLARE A PROP \u2014 WITH A `target` \u2014 for every string, link and image a marketer will ever touch: only the leaves a prop targets are click-to-edit. Each one may carry `ui` to say how its control presents in the inspector \u2014 a collapsed group, what titles and thumbnails a table's rows, whether that table's rows can be dragged at all. 'button' is ONE unit {label, href, variant?, size?, arrow?, icon?, newTab?} on a button block's 'props', never a text prop plus a url prop. 'link' an href, 'date' YYYY-MM-DD, 'color' a hex, 'file' {url, name?}, 'icon' an icon name or an image, 'multiselect' a string[] from config.options (required). " + SLOT_MULTIPLE_NOTE + " " + PROP_V2_NOTE
@@ -4132,6 +4134,7 @@ function buildToolDefs(deps) {
     description: z.string().optional(),
     preview: componentPreviewArg.optional(),
     icon: dockIconArg.nullable().optional().describe(PARAM_TEXT.componentIcon),
+    kitEntry: z.string().min(1).max(100).nullable().optional().describe(PARAM_TEXT.componentKitEntry),
     blockJson: z.array(blockObject).optional().describe("REPLACES the block tree"),
     props: z.array(componentPropObject).optional().describe(
       "REPLACES the prop array \u2014 include every prop you want to keep, WITH its stored `ui`, or that prop's authoring chrome is dropped along with the prop. Read get_component first."
@@ -6252,10 +6255,12 @@ ${lines.join("\n")}`, found);
       },
       handler: guard(
         async (args) => withClient(async (client) => {
-          const { component, replaced } = await client.extractComponent(args);
+          const res = await client.extractComponent(args);
+          const { component, replaced } = res;
+          const kit = res.kit;
           return ok(
             `Created component '${component.name}' (id ${component.id}) and repointed ${replaced} sections to it. Page drafts changed; publish those pages to make it live.`,
-            { ...component, nextAction: DOCK_UI_NEXT }
+            { ...component, ...kit ? { kit } : {}, nextAction: DOCK_UI_NEXT }
           );
         })
       )
@@ -6516,6 +6521,10 @@ DERIVED by \`editor_setup\`, where the componentize lane in \xA710 reuses every
                                               mcp notes and avoid its pitfalls (tag rules below).
                                               Its props carry NO target: give each one a target
                                               into YOUR blockJson (\xA73) before create_component
+                                              Every component names its kitEntry
+                                              (bettercms://kit/entry/{id}); its ui follows that
+                                              entry; override the match when it's wrong; exempt
+                                              with no-kit-match only with a note
     Repeated visual region on a page?      -> a COMPONENT with sectionType (a Section)
       ...and it comes in more than one look? -> siblings sharing that sectionType = VARIANTS
     A stack of mixed, reorderable content? -> kind:'block' models + a \`modular\` field