@bettercms-ai/mcp 0.41.0 → 0.42.0

package/dist/index.js

@@ -3107,7 +3107,7 @@ function buildToolDefs(deps) {
       def(
         "submit_conversion_receipt",
         "Record what the conversion codemod could and could not do",
-        "Hand BetterCMS the codemod's own account of a conversion run, so the coverage meter can say WHY a path is not declared instead of only that it is not. Submit the receipt `npx @bettercms-ai/convert` wrote (`--receipt out.json`) for the SAME `briefDigest` get_conversion_brief { complete: true } returned: `{ briefDigest, receipt }`, where the receipt carries `paths: { declared, rewritten, alreadyDeclared, pending[{ route, scope, path, kind, file, reason, message }] }`. `paths.declared` must equal rewritten + alreadyDeclared + pending.length, and each pending `reason` is one of the converter's own (IN_EXPRESSION, AMBIGUOUS_LITERAL, REPEATER_FIXED_LENGTH, PARSE_ERROR, \u2026) \u2014 a path with no receipt row simply reads `not-declared`. It is a RECORD, not a release: it changes nothing about the site, and the meter picks it up on the next get_binding_report after the next deploy. A 404 `unknown-brief` means that digest was never issued here, so convert against a brief this project actually returned. \u{1F534} SUBMIT THE BINDING RECEIPT, NOT THE `--forms` ONE. A run of `npx @bettercms-ai/convert --forms` writes a receipt whose `paths` are all zero and whose account is in a `forms` block (`{ wired, alreadyWired, pending[{ id, name, reason }], notes }`); it passes this endpoint's arithmetic and would overwrite the real coverage with zeros. Write it to its own file (`--receipt forms-receipt.json`), read `forms.pending` and publish every form `forms.notes` names in the Forms tab, and submit the binding run's receipt here. Requires artifact:write, the same authority as set_binding_mode; on a workspace-wide connection pass `projectId`.",
+        "Hand BetterCMS the codemod's own account of a conversion run, so the coverage meter can say WHY a path is not declared instead of only that it is not. Submit the receipt `npx @bettercms-ai/convert` wrote (`--receipt out.json`) for the SAME `briefDigest` get_conversion_brief { complete: true } returned: `{ briefDigest, receipt }`, where the receipt carries `paths: { declared, rewritten, alreadyDeclared, pending[{ route, scope, path, kind, file, reason, message, fix }] }`. `paths.declared` must equal rewritten + alreadyDeclared + pending.length, and each pending `reason` is one of the converter's own (IN_EXPRESSION, AMBIGUOUS_LITERAL, REPEATER_FIXED_LENGTH, PARSE_ERROR, \u2026) \u2014 a path with no receipt row simply reads `not-declared`. \u{1F534} A RECEIPT WITH PENDING PATHS IS A PROGRESS REPORT, NOT A FINISH LINE. The response answers `complete` and `pendingTotal`, and echoes the first 40 pending rows WITH their `fix` \u2014 `{ action, file, line, col?, snippet, why? }`, where `action` is one of `wrap-span` (wrap the literal in a `<span data-bcms-field=\u2026>`), `declare-attr` (add `data-bcms-field=\u2026` to the element at file:line), `bind-expression` (replace the expression with the framework's bcmsField helper), `declare-richtext` (bind the container with the richtext helper), `bind-data` (the literal comes from the data file at file:line \u2014 bind that field) or `manual` (with a one-sentence `why`). Apply every fix in the source, rerun the codemod, resubmit. `complete: true` is the only receipt that ends a conversion \u2014 do not report a site converted on anything less. It is a RECORD, not a release: it changes nothing about the site, and the meter picks it up on the next get_binding_report after the next deploy. A 404 `unknown-brief` means that digest was never issued here, so convert against a brief this project actually returned. \u{1F534} SUBMIT THE BINDING RECEIPT, NOT THE `--forms` ONE. A run of `npx @bettercms-ai/convert --forms` writes a receipt whose `paths` are all zero and whose account is in a `forms` block (`{ wired, alreadyWired, pending[{ id, name, reason }], notes }`); it passes this endpoint's arithmetic and would overwrite the real coverage with zeros. Write it to its own file (`--receipt forms-receipt.json`), read `forms.pending` and publish every form `forms.notes` names in the Forms tab, and submit the binding run's receipt here. Requires artifact:write, the same authority as set_binding_mode; on a workspace-wide connection pass `projectId`.",
         z.object({
           briefDigest: z.string().min(1).describe("The `briefDigest` get_conversion_brief { complete: true } returned. Must match the receipt's own."),
           receipt: z.record(z.string(), z.unknown()).describe("The receipt `npx @bettercms-ai/convert --receipt out.json` wrote, verbatim.")
@@ -3171,7 +3171,20 @@ function buildToolDefs(deps) {
         "Edit a page",
         "Edit a page: title, slug, SEO metaTitle/metaDescription, publish status (draft|published), and `blockJson` (its block composition \u2014 passing it REPLACES the whole array, so read get_page first). It does NOT change the field SCHEMA \u2014 use add_page_field / set_page_content for that. Renaming the slug keeps content intact. Publishing copies the draft blocks live in the same call. " + SECTION_DOCTRINE,
         z.object({ pageId: z.string().min(1), title: z.string().optional(), slug: z.string().optional(), blockJson: z.array(blockObject).optional().describe("REPLACES the page's block composition"), metaTitle: z.string().optional(), metaDescription: z.string().optional(), status: z.enum(["draft", "published"]).optional() }).shape,
-        async (c, a) => ok("Updated page.", await data(c, "PATCH", `/management/pages/${s(a.pageId)}/meta`, { title: a.title, slug: a.slug, blockJson: a.blockJson, metaTitle: a.metaTitle, metaDescription: a.metaDescription, status: a.status }))
+        async (c, a) => {
+          const res = await c.fetchJSON(
+            c.url(`/management/pages/${s(a.pageId)}/meta`),
+            {
+              method: "PATCH",
+              body: JSON.stringify({ title: a.title, slug: a.slug, blockJson: a.blockJson, metaTitle: a.metaTitle, metaDescription: a.metaDescription, status: a.status })
+            }
+          );
+          const note = res.redirectNote;
+          return ok(
+            note ? `Updated page. An existing redirect from ${note.source} already points to ${note.existingDestination}; it wasn't changed, so the old address does not redirect to the new one.` : "Updated page.",
+            res.data
+          );
+        }
       ),
       // ── Code + deploy (parity with remote /mcp; needs artifact:write) ──
       // Both grant shapes carry that scope now; a workspace-wide one names its target per
@@ -4790,8 +4803,14 @@ an empty string on the live site.
 
 ## 13. Convert an imported repo into a CMS-backed, editable site
 
-\xA711 says a deploy does not make a site editable. This is the recipe that does, and it ends in a
-receipt you can read: \`get_binding_report\` says \`mode: "declared"\` with zero unmatched paths.
+\xA711 says a deploy does not make a site editable. This is the recipe that does.
+
+\u{1F534} **A CONVERSION ENDS ONLY WHEN NOTHING IS PENDING.** The codemod's first pass never
+declares every path \u2014 measured on a real site, one pass declared 282 of 767 \u2014 and every path it
+leaves in \`paths.pending\` carries a \`fix\` naming the file, the line and the one edit. Apply
+them, rerun, resubmit, and repeat until \`submit_conversion_receipt\` answers \`complete: true\`.
+That boolean is the finish line; a receipt with pending paths is a progress report. The
+\`convert_site\` MCP prompt walks exactly this loop.
 
 **Scope, before you start.**
 
@@ -4865,21 +4884,30 @@ hand. THE ORDER, and every step of it matters:
    could not match are in \`forms.pending\` with a reason (\`FORM_NOT_IN_SOURCE\`,
    \`FIELD_UNMATCHED\`, \`FORM_AMBIGUOUS\`, \u2026) \u2014 it refuses rather than guessing, because a form
    wired to the wrong id delivers the customer's leads into another form's inbox.
-3. REVIEW THE PENDING LIST. Every path the codemod could not do is in \`paths.pending\` with a
-   reason (\`IN_EXPRESSION\`, \`AMBIGUOUS_LITERAL\`, \`REPEATER_FIXED_LENGTH\`, \`PARSE_ERROR\`, \u2026).
-   Do those by hand, or decide they are genuinely not convertible \u2014 do not skip past them.
-4. \`submit_conversion_receipt { briefDigest, receipt }\` with the receipt file, verbatim. This is
-   what lets the coverage meter say WHY a path is undeclared instead of only that it is; without
-   it every one of them reads \`not-declared\`, which looks like a broken site rather than work
-   with a reason. It records and releases nothing.
+3. APPLY EVERY PENDING FIX, THEN RERUN. Each entry of \`paths.pending\` carries its reason
+   (\`IN_EXPRESSION\`, \`AMBIGUOUS_LITERAL\`, \`REPEATER_FIXED_LENGTH\`, \`PARSE_ERROR\`, \u2026) and,
+   where the codemod could work one out, a \`fix\`: \`{ action, file, line, col?, snippet, why? }\`.
+   Go to \`file\`:\`line\` and do what \`action\` says \u2014 \`wrap-span\` (wrap the literal in
+   \`<span data-bcms-field="\u2026">\`), \`declare-attr\` (add \`data-bcms-field="\u2026"\` to that element),
+   \`bind-expression\` (replace the expression with the framework's bcmsField helper),
+   \`declare-richtext\` (bind the container with the richtext helper), \`bind-data\` (bind the field
+   in the data file or collection entry it names) or \`manual\` (do what its \`why\` says). A row
+   with no \`fix\` is still yours. Then RERUN step 2 and repeat until \`paths.pending\` is empty \u2014
+   the codemod is idempotent, so a second run over converted source rewrites nothing.
+4. \`submit_conversion_receipt { briefDigest, receipt }\` with the receipt file, verbatim. It
+   answers \`complete\`, \`pendingTotal\` and the first 40 pending rows with their \`fix\`. \`complete: true\` \u2014 nothing
+   pending \u2014 is the ONLY receipt that ends a conversion; on anything less go back to step 3. It
+   is also what lets the coverage meter say WHY a path is undeclared instead of only that it is.
+   It records and releases nothing.
 5. Push, or \`deploy_project\`. A PLAIN HTML repo \u2014 no \`package.json\` \u2014 deploys by PUSH ONLY:
    \`deploy_project\` refuses such an archive by design, so pushing is the whole lane. Either way,
    poll \`get_deploy_status\` until \`slot\` is \`current\` (or \`awaitingPromote\` is false) before you
    read the report in step 6 \u2014 a report read against the previous release is the previous
    release's verdict.
 6. \`get_binding_report\`. Alongside \`unmatched\` it now carries \`coverage\` \u2014 \`declared\` (what the
-   brief listed), \`bound\` (what the build declares) and \`pending\` with the reasons. Fix what it
-   names and release again until \`coverage.pending\` is empty.
+   brief listed), \`bound\` (what the build declares) and \`pending\` with the reasons. It must read
+   \`unmatched\` 0 and \`unaddressable\` under 2% of each route's visible text (\xA711). Fix what it
+   names IN THE SOURCE and release again until \`coverage.pending\` is empty.
 7. \`set_binding_mode { declaredBindings: true }\` and release ONE MORE TIME \u2014 the mode applies to
    the next release, not to the one already out.
 
@@ -5108,6 +5136,31 @@ disagrees with the array the moment anyone drags a row in the builder.
 // src/prompts.ts
 var STRUCTURE_RULE = `### Page structure (non-negotiable)
 ${SECTION_DOCTRINE}`;
+var CONVERT_SITE_TEXT = (projectId) => `Convert my site so every visible element is editable in BetterCMS${projectId ? `, project ${projectId}` : ""}.
+Do not stop at the plan or at a partial receipt \u2014 finish the whole site.
+
+1. \`list_projects\`; pass \`projectId\`${projectId ? ` (${projectId})` : ""} on every project tool from here on. If the project
+   is not listed the grant is on another workspace \u2014 stop and say so.
+2. \`get_conversion_plan\`. On a 404 \`no-approved-plan\`, call
+   \`get_conversion_brief { complete: true }\` and follow \`cursor\` to the LAST page, keeping every
+   page \u2014 a codemod fed the capped brief converts a truncated site. Write them to \`brief.json\`.
+3. \`pull_project_source\` (or clone the \`github\` remote it names) and work from the SOURCE, never
+   from the deployed HTML.
+4. \`npx @bettercms-ai/convert --brief brief.json --root . --receipt receipt.json\`; read \`git diff\`.
+5. For EVERY entry of \`paths.pending\`, go to its \`fix.file\`:\`fix.line\` and do what \`fix.action\`
+   says: \`wrap-span\` wrap the literal in \`<span data-bcms-field="\u2026">\`; \`declare-attr\` add
+   \`data-bcms-field="\u2026"\` to that element; \`bind-expression\` replace the expression with the
+   framework's bcmsField helper; \`declare-richtext\` bind the container with the richtext helper;
+   \`bind-data\` bind the field in the data file it names; \`manual\` do what its \`why\` says. A row
+   with no \`fix\` is still yours. Then rerun step 4 until \`paths.pending\` is EMPTY.
+6. \`submit_conversion_receipt { briefDigest, receipt }\`. It must answer \`complete: true\`; if it
+   does not, go back to step 5 \u2014 that is the only receipt that ends a conversion.
+7. Deploy (push, or \`deploy_project\`) and poll \`get_deploy_status\` until the release is live.
+8. \`get_binding_report\` must read \`unmatched\` 0 and \`unaddressable\` under 2% of each route's
+   visible text. Fix what it names in the SOURCE, deploy, re-read (playbook section 11).
+9. \`set_binding_mode { declaredBindings: true }\`, deploy AGAIN and poll \u2014 the mode applies to the
+   NEXT release \u2014 then confirm \`get_binding_report\` reads mode "declared", unmatched 0, bound
+   above 0, \`coverage.pending\` empty. That report is your final answer to me.`;
 var SCHEMA_PROPOSAL_FLOW = `### Whole-project design (confirm-first) \u2192 \`create_component\` / \`create_page\` / \`create_content_model\`
 Design the WHOLE project from its brief or its code, and **confirm the shape with the user
 BEFORE creating anything**. Never silently guess.
@@ -5487,6 +5540,19 @@ in the dashboard \u2014 those render as an empty string until they are published
       ]
     })
   );
+  server.registerPrompt(
+    "convert_site",
+    {
+      title: "Convert a site so nothing is left pending (guided)",
+      description: "Run the conversion end to end: pull the source, run @bettercms-ai/convert, apply every fix it lists as pending, rerun until nothing is pending, and finish only when submit_conversion_receipt returns complete and get_binding_report reads unmatched 0.",
+      argsSchema: {
+        projectId: z2.string().optional().describe("the project to convert; omit if this connection is scoped to one")
+      }
+    },
+    ({ projectId }) => ({
+      messages: [{ role: "user", content: { type: "text", text: CONVERT_SITE_TEXT(projectId) } }]
+    })
+  );
   server.registerPrompt(
     "build_site",
     {