@bettercms-ai/mcp 0.56.3 → 0.57.0

package/dist/index.js

@@ -2449,6 +2449,11 @@ var GIT_TEXT = {
   create_github_pull_request: "Open a pull request on the connected repository. `head` is the branch you pushed; `base` defaults to the build branch, so merging it is what ships the change. Use this instead of pushing straight to the build branch whenever a human should review first, or when that branch is protected. Returns the number and the url to hand the user.",
   list_github_pull_requests: "Pull requests on the connected repository: number, title, state, whether it merged, draft, head, base and url. `state` is 'open' (the default), 'closed' or 'all'. Poll it to find out whether the pull request you opened has landed."
 };
+var HOSTING_TEXT = {
+  list_hosting_connections: "The Vercel, Netlify and Cloudflare accounts connected to this workspace (id, provider, accountLabel, status; never a token), plus `connectUrl`, the dashboard page where a person connects one. Call it before deploy_to_host. If the provider the user wants has no connection with status `ok`, give the user `connectUrl` to connect it in their browser and stop until they have: you never handle OAuth or a host token yourself.",
+  deploy_to_host: "Deploy this project to the user's own Vercel or Netlify account through their connection. BetterCMS builds the site and the host serves that build, so there is no host CLI to run, no token to paste and no vercel.json rewrite to write; forms keep working because they post to the BetterCMS API. The first call creates the site on the host and makes it the project's host; a later call for the same provider redeploys that site (`redeployed: true`) instead of creating another. `connectionId` (from list_hosting_connections) defaults to the newest working one, `siteName` to the project's handle. A refusal carries a `code` and a `fixUrl` (not_connected, reconnect, pick_existing_site, grant_required, ADMIN_REQUIRED): each is fixed by the user at `fixUrl`, so relay it and stop. `deploymentQueued: false` means the project has no live build yet: deploy_project first, and that release reaches the host on its own. Never run the Vercel or Netlify CLI while a connection exists. Then poll get_host_deploy_status. Needs artifact:write, like deploy_project.",
+  get_host_deploy_status: "The connected project's recent deployments to Vercel, Netlify or Cloudflare, newest first: state (queued|deploying|live|failed), providerUrl, error, sha and targetName. Poll it after deploy_to_host until the newest one is `live`, whose `providerUrl` is the live URL to hand the user, or `failed`, whose `error` you read back to them."
+};
 function ok(summary, data) {
   return {
     content: [
@@ -2511,7 +2516,10 @@ function refusalDetail(err) {
   const lines = [
     code ? `code: ${code}` : "",
     body.readiness !== void 0 ? `readiness: ${JSON.stringify(body.readiness)}` : "",
-    body.issues !== void 0 ? `issues: ${JSON.stringify(body.issues)}` : ""
+    body.issues !== void 0 ? `issues: ${JSON.stringify(body.issues)}` : "",
+    // The link a person follows to fix it (connect a host, create a Vercel project): an agent
+    // that only sees the sentence has nothing to hand the user.
+    typeof body.fixUrl === "string" ? `fixUrl: ${body.fixUrl}` : ""
   ].filter(Boolean);
   return lines.length ? `
 ${lines.join("\n")}` : "";
@@ -3550,7 +3558,7 @@ ${d.outline}` : "Proposed Content structure.", d);
       def(
         "submit_conversion_receipt",
         "Record what the conversion codemod could and could not do",
-        "Hand BetterCMS the codemod's own account of a run, so the meter can say WHY a path is undeclared. 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?, kind? }`. `action` is `wrap-span`, `declare-attr`, `bind-expression`, `declare-richtext`, `bind-data` or `manual`; each row's `snippet` and `why` say what to change there. On a `declare-richtext` with `kind: document`, bind the ONE element wrapping every block of the Body, never the paragraph holding its first. Apply every fix, rerun, resubmit. `complete: true` is the only receipt that ends a conversion; do not report a site converted on 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. \u{1F534} SUBMIT THE `--forms` RECEIPT TOO, AS A SECOND CALL: A `npx @bettercms-ai/convert --forms` run writes a receipt whose `paths` are all zero and whose account is in a `forms` block. Write it to its own file (`--receipt forms-receipt.json`) and submit it under the same `briefDigest`: stored beside the binding receipt, never counted in coverage. Then read `forms.pending` and publish every form it names. Requires artifact:write, the same authority as set_binding_mode.",
+        "Hand BetterCMS the codemod's own account of a run, so the meter can say WHY a path is undeclared. 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?, kind? }`. `action` is `wrap-span`, `declare-attr`, `bind-expression`, `declare-richtext`, `bind-data` or `manual`; each row's `snippet` and `why` say what to change there. On a `declare-richtext` with `kind: document`, bind the ONE element wrapping every block of the Body, never the paragraph holding its first. Apply every fix, rerun, resubmit. `complete: true` is the only receipt that ends a conversion; do not report a site converted on 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. \u{1F534} SUBMIT THE `--forms` RECEIPT TOO, AS A SECOND CALL: A `npx @bettercms-ai/convert --forms` run writes a receipt whose `paths` are all zero and whose account is in a `forms` block. Write it to its own file (`--receipt forms-receipt.json`) and submit it under the same `briefDigest`: stored beside the binding receipt, never counted in coverage. Then read `forms.pending` and publish every form it names. \u{1F534} THE SITE'S DESIGN IS NOT YOURS TO CHANGE: run `npx @bettercms-ai/convert --verify-styles --base <commit before the conversion> --root .` and include its `styleEdits` in the receipt. A receipt listing any changed class, className or style is refused with 409 `style-edits` and every token \u2014 restore them; the CMS keeps inline markup exactly as written. Requires artifact:write, the same authority as set_binding_mode.",
         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.")
@@ -4149,6 +4157,34 @@ ${res.warnings.join("\n")}` : summary, res.data);
         "Get the connected project's deploy/build status: state (idle|queued|building|categorizing|failed), whether it's publishing, the live commit sha, when it went live, and any build error. `categorizing` means the bytes are live but the import's setup lanes (content, pages, bindings) are still running, so `publishing` is still true and the site is not ready to edit yet. Poll this after deploy_project until state is idle with your sha live. Also returns `canvas.lane` (the editor's live-preview lane for this site: `bridge` / `draft-route` / `none`) and `editorUrl`, the visual editor to hand the user.",
         z.object({}).shape,
         async (c) => ok("Deploy status.", await data(c, "GET", `/management/projects/deploy-status`))
+      ),
+      // ── Deploy to the user's own host (parity with remote /mcp) ──
+      // A person connects Vercel or Netlify in the dashboard; nothing here touches OAuth or a host
+      // token. deploy_to_host takes artifact:write like deploy_project. @see management/deploy-targets.ts
+      def(
+        "list_hosting_connections",
+        "List hosting connections",
+        HOSTING_TEXT.list_hosting_connections,
+        z.object({}).shape,
+        async (c) => ok("Hosting connections.", await data(c, "GET", `/management/hosting/connections`))
+      ),
+      def(
+        "deploy_to_host",
+        "Deploy to Vercel or Netlify",
+        HOSTING_TEXT.deploy_to_host,
+        z.object({
+          provider: z.enum(["vercel", "netlify"]),
+          connectionId: z.string().min(1).optional().describe("a connection id from list_hosting_connections; defaults to the newest working one"),
+          siteName: z.string().min(1).max(63).optional().describe("lowercase letters, numbers and hyphens; defaults to the project's handle")
+        }).shape,
+        async (c, a) => ok("Host deploy.", await data(c, "POST", `/management/deploy-targets/provision`, { provider: a.provider, connectionId: a.connectionId, siteName: a.siteName }))
+      ),
+      def(
+        "get_host_deploy_status",
+        "Get host deploy status",
+        HOSTING_TEXT.get_host_deploy_status,
+        z.object({}).shape,
+        async (c) => ok("Host deployments.", await data(c, "GET", `/management/hosting/external-deployments`))
       )
     ];
   }
@@ -5915,7 +5951,7 @@ disagrees with the array the moment anyone drags a row in the builder.
 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.
+Do not stop at the plan or at a partial receipt \u2014 finish the whole site, never editing a class or style.
 
 1. \`list_projects\`; pass \`projectId\`${projectId ? ` (${projectId})` : ""} on every project tool. Not listed = the grant is on
    another workspace: have the user re-authenticate there. Never convert a different project.
@@ -5931,14 +5967,14 @@ Do not stop at the plan or at a partial receipt \u2014 finish the whole site.
    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.`;
+6. \`npx @bettercms-ai/convert --verify-styles --base <commit before step 4>\`, restore what it lists, then
+   \`submit_conversion_receipt { briefDigest, receipt }\` with its \`styleEdits\`: only \`complete: true\` ends it (else step 5).
+7. Deploy the working tree (\`create_deploy_upload\` + \`deploy_from_upload\`); poll \`get_deploy_status\` until live. No git yet.
+8. \`get_binding_report\`: \`unmatched\` 0, \`unaddressable\` under 2% per route; fix the SOURCE, deploy, re-read (playbook \xA711).
+9. \`set_binding_mode { declaredBindings: true }\`, deploy AGAIN and poll, then confirm \`get_binding_report\`
+   reads mode "declared", unmatched 0, bound above 0, \`coverage.pending\` empty. Send me that report.
+10. Ask me whether to commit and push to my repository, commit only, or leave it uncommitted (unpushed, the
+   next rebuild from my repo drops it). Touch git only as I answer.`;
 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.