@bettercms-ai/mcp 0.65.1 → 0.65.2

package/dist/index.js

@@ -6298,10 +6298,12 @@ but a code-built site ships only what its own templates draw:
   itself, in order, each section root stamped \`data-bcms-block="<blockId>"\`. \`npx @bettercms-ai/convert
   --componentize\` writes that loop (\`src/lib/bcms-sections.ts\`) and the stamps. Until it ships, the canvas
   only ARRANGES the static build to match the draft (a section the build never rendered is stood in for
-  by a server render), the editor locks Add section and reordering on routes whose code sets the
-  sections, and each such route leads \`submit_conversion_receipt\`'s \`pending\` with a
-  \`SECTIONS_UNSTAMPED\` row, so \`complete\` stays false. Never hard-code a page's bands in a template
-  whose order the CMS owns.
+  by a server render); the editor still saves added, moved and swapped sections but says the live site
+  keeps its own order, and offers "Let BetterCMS control section order" (that same codemod, committed
+  to the connected repository); and each such route leads \`submit_conversion_receipt\`'s \`pending\`
+  with a \`SECTIONS_UNSTAMPED\` row, so \`complete\` stays false. Never hard-code a page's bands, or
+  literal \`data-bcms-block\` ids, in a template whose order the CMS owns: a release measures whether
+  the stamped roots come out in the CMS order (\`ordered\` on the binding report's structure row).
 - A placement the site never renders (a leftover nav, footer or modal its layout draws) moves
   nothing: the editor counts section moves in RENDERED sections only and locks that row. Remove
   such placements; do not reorder around them.