@bettercms-ai/mcp 0.38.0 → 0.38.1

package/dist/index.js

@@ -4254,7 +4254,12 @@ component placement, and the page keeps its fields, its values and its bindings.
     1. set_authoring_preference { preference: "components" }
     2. get_componentize_plan    one component per section, computed live; creates nothing. It
                                 reads this project's PUBLISHED pages, so no deploy is needed
-                                to reach it \u2014 the deploy is the last step, not the first
+                                to reach it \u2014 the deploy is the last step, not the first.
+                                On a site DERIVED at import the release hook has already run
+                                this plan in bind mode and PUBLISHED what it created, so
+                                expect ALREADY_COMPONENTIZED and skip to step 6 (publish the
+                                pages) \u2014 the lane publishes the COMPONENTS, not the placements,
+                                which are still draft blocks on the pages
     3. show the user the plan and CONFIRM \u2014 it says how many components and which pages
     4. componentize_sections    \`dryRun: true\` first, then for real; components land as DRAFTS
                                 and each placement carries \`props.bind\` to the page's field
@@ -4437,7 +4442,10 @@ still gets its own component: its own family, plus \`allowedOn: ["slug:<page>"]\
 with NO \`sectionType\` never appears in the editor's "Add a section" picker. Start from the
 builtin blueprints \`list_components\` returns (\`builtin:*\`) instead of hand-writing block JSON.
 On a DERIVED site run \`get_componentize_plan\` \u2192 \`componentize_sections\` FIRST \u2014 it does most
-of this in one call.
+of this in one call, and on a site derived at IMPORT the release hook has already run it in bind
+mode and published the components, so expect ALREADY_COMPONENTIZED \u2014 the placements it wrote are
+still DRAFT blocks on the pages, so publish the pages, then \`npx @bettercms-ai/convert
+--componentize\`.
 
 **3. The hierarchy editors see is the GROUP.** \`create_component\` and \`update_component\` take
 \`group\`: a NAME, resolved against the project's component groups and created when missing. That