@sakupa/mcp 0.7.18 → 0.7.19

package/dist/bin.js

@@ -129,7 +129,7 @@ var FORBIDDEN_PATH_SEGMENTS = [
 var ALLOWED_HIDDEN_PATHS = [".well-known/"];
 
 // ../core/dist/domain/version.js
-var SAKUPA_MCP_VERSION = "0.7.18";
+var SAKUPA_MCP_VERSION = "0.7.19";
 
 // ../core/dist/domain/errors.js
 var HTTP_STATUS = {
@@ -2088,21 +2088,17 @@ ${res2.message}
 ` : "";
         return text(
           "domain_verification_started",
-          switchNotice + `Domain binding started for ${apex} (includes: ${res.includedHostnames.join(", ")} \u2014 both will serve this site).
+          switchNotice + `Domain binding started for ${apex} (will serve: ${res.includedHostnames.join(", ")}).
 
-STEP 1 of 2 \u2014 add ALL THREE records NOW:
+This is a STEP-BY-STEP setup \u2014 give the user ONE record at a time so they do not get overwhelmed and give up.
 
-  1) TXT    host: ${txtShort}   value: ${res.verificationRecord.value}
-  2) CNAME  host: www   value: ${res.servingTarget}
-  3) APEX   host: @   -> ${res.servingTarget}. Try a plain CNAME at host @ first (most panels accept it); if rejected use ALIAS / ANAME / CNAME-flattening; if the panel has neither, skip it \u2014 www alone works, and a URL redirect from @ to www covers bare-domain visitors.
+STEP 1 of 2 \u2014 prove ownership. Add ONE record:
 
-Host fields above are the SHORT form: most DNS panels append the domain automatically. After saving, the record list must NOT show ${apex} twice in one name \u2014 that means the full name was pasted into an auto-appending field.
+  TXT   host: ${txtShort}   value: ${res.verificationRecord.value}
 
-Ownership comes ONLY from DNS control; paying never grants it. The first verified request wins and this challenge expires after 72 hours.
+Host is the SHORT form: most panels append the domain automatically (the saved record must NOT show ${apex} twice in one name). Ownership comes ONLY from DNS control; paying never grants it. The first verified request wins and this challenge expires after 72 hours.
 
-STEP 2 (after ownership verifies): Sakupa issues certificate-validation TXT records \u2014 the verification result and bind "status" list them the moment they exist; relay each to the user and add them too (copy names and values EXACTLY as given). Everything then completes automatically.
-
-Drive the whole flow with bind "status": it live-checks every record and names the exact fix for anything wrong. Re-check every 5 minutes (up to 10 times). Any later session can resume with action "status" alone; the verificationId is optional.`,
+When the user says the TXT is set, run bind "status". It verifies ownership and then hands back STEP 2 \u2014 a SINGLE www CNAME (there are NO certificate TXT records; HTTPS validates automatically over that CNAME). Each "status" checks the previous step and, unless something is misconfigured, advances to the next \u2014 so run it whenever the user reports a step done, NOT on a timer. Any later session can resume with action "status" alone; the verificationId is optional.`,
           {
             verificationId: res.verificationId,
             apexDomain: apex,
@@ -2116,11 +2112,8 @@ Drive the whole flow with bind "status": it live-checks every record and names t
                 shortHost: txtShort,
                 name: res.verificationRecord.name,
                 value: res.verificationRecord.value
-              },
-              { type: "CNAME", shortHost: "www", name: `www.${apex}`, value: res.servingTarget },
-              { type: "ALIAS", shortHost: "@", name: apex, value: res.servingTarget }
+              }
             ],
-            servingInstructions: res.servingInstructions,
             retryAfterSeconds: DNS_RETRY_AFTER_SECONDS,
             maxAttempts: DNS_MAX_ATTEMPTS
           },

package/dist/index.js

@@ -124,7 +124,7 @@ var FORBIDDEN_PATH_SEGMENTS = [
 var ALLOWED_HIDDEN_PATHS = [".well-known/"];
 
 // ../core/dist/domain/version.js
-var SAKUPA_MCP_VERSION = "0.7.18";
+var SAKUPA_MCP_VERSION = "0.7.19";
 
 // ../core/dist/domain/errors.js
 var HTTP_STATUS = {
@@ -2154,21 +2154,17 @@ ${res2.message}
 ` : "";
         return text(
           "domain_verification_started",
-          switchNotice + `Domain binding started for ${apex} (includes: ${res.includedHostnames.join(", ")} \u2014 both will serve this site).
+          switchNotice + `Domain binding started for ${apex} (will serve: ${res.includedHostnames.join(", ")}).
 
-STEP 1 of 2 \u2014 add ALL THREE records NOW:
+This is a STEP-BY-STEP setup \u2014 give the user ONE record at a time so they do not get overwhelmed and give up.
 
-  1) TXT    host: ${txtShort}   value: ${res.verificationRecord.value}
-  2) CNAME  host: www   value: ${res.servingTarget}
-  3) APEX   host: @   -> ${res.servingTarget}. Try a plain CNAME at host @ first (most panels accept it); if rejected use ALIAS / ANAME / CNAME-flattening; if the panel has neither, skip it \u2014 www alone works, and a URL redirect from @ to www covers bare-domain visitors.
+STEP 1 of 2 \u2014 prove ownership. Add ONE record:
 
-Host fields above are the SHORT form: most DNS panels append the domain automatically. After saving, the record list must NOT show ${apex} twice in one name \u2014 that means the full name was pasted into an auto-appending field.
+  TXT   host: ${txtShort}   value: ${res.verificationRecord.value}
 
-Ownership comes ONLY from DNS control; paying never grants it. The first verified request wins and this challenge expires after 72 hours.
+Host is the SHORT form: most panels append the domain automatically (the saved record must NOT show ${apex} twice in one name). Ownership comes ONLY from DNS control; paying never grants it. The first verified request wins and this challenge expires after 72 hours.
 
-STEP 2 (after ownership verifies): Sakupa issues certificate-validation TXT records \u2014 the verification result and bind "status" list them the moment they exist; relay each to the user and add them too (copy names and values EXACTLY as given). Everything then completes automatically.
-
-Drive the whole flow with bind "status": it live-checks every record and names the exact fix for anything wrong. Re-check every 5 minutes (up to 10 times). Any later session can resume with action "status" alone; the verificationId is optional.`,
+When the user says the TXT is set, run bind "status". It verifies ownership and then hands back STEP 2 \u2014 a SINGLE www CNAME (there are NO certificate TXT records; HTTPS validates automatically over that CNAME). Each "status" checks the previous step and, unless something is misconfigured, advances to the next \u2014 so run it whenever the user reports a step done, NOT on a timer. Any later session can resume with action "status" alone; the verificationId is optional.`,
           {
             verificationId: res.verificationId,
             apexDomain: apex,
@@ -2182,11 +2178,8 @@ Drive the whole flow with bind "status": it live-checks every record and names t
                 shortHost: txtShort,
                 name: res.verificationRecord.name,
                 value: res.verificationRecord.value
-              },
-              { type: "CNAME", shortHost: "www", name: `www.${apex}`, value: res.servingTarget },
-              { type: "ALIAS", shortHost: "@", name: apex, value: res.servingTarget }
+              }
             ],
-            servingInstructions: res.servingInstructions,
             retryAfterSeconds: DNS_RETRY_AFTER_SECONDS,
             maxAttempts: DNS_MAX_ATTEMPTS
           },

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sakupa/mcp",
-  "version": "0.7.18",
+  "version": "0.7.19",
   "description": "Sakupa MCP server: publish AI-made static sites from your AI tool. AI-made pages, live in seconds.",
   "type": "module",
   "main": "dist/index.js",