@sakupa/mcp 0.7.21 → 0.7.22

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.21";
+var SAKUPA_MCP_VERSION = "0.7.22";
 
 // ../core/dist/domain/errors.js
 var HTTP_STATUS = {
@@ -2248,14 +2248,18 @@ Full status:`, res);
             throw new SakupaError("invalid_request", "hostname is required for start");
           }
           const res2 = await ctx.client.recoverDomain({ hostname: args.hostname });
+          const txtShort = shortHostFor(res2.verificationRecord.name, res2.apexDomain);
           return text(
             "domain_recovery_started",
             `Recovery started for ${args.hostname} (apex domain: ${res2.apexDomain}).
 
 Create this DNS record to prove apex-domain control:
-   name:  ${res2.verificationRecord.name}
-   type:  ${res2.verificationRecord.type}
-   value: ${res2.verificationRecord.value}
+   type:       ${res2.verificationRecord.type}
+   host/label: ${txtShort}
+   value:      ${res2.verificationRecord.value}
+   full name:  ${res2.verificationRecord.name}
+
+Enter ONLY "${txtShort}" in DNS panels whose host/name field automatically appends ".${res2.apexDomain}". The saved full record must be exactly "${res2.verificationRecord.name}" and must never contain the apex twice.
 
 ${res2.message}
 
@@ -2265,7 +2269,18 @@ After the DNS record resolves, re-run recover with verificationId: "${res2.verif
             {
               verificationId: res2.verificationId,
               apexDomain: res2.apexDomain,
-              verificationRecord: res2.verificationRecord,
+              verificationRecord: {
+                ...res2.verificationRecord,
+                shortHost: txtShort
+              },
+              requiredRecords: [
+                {
+                  type: res2.verificationRecord.type,
+                  shortHost: txtShort,
+                  name: res2.verificationRecord.name,
+                  value: res2.verificationRecord.value
+                }
+              ],
               revokesPreviousCredentialsByDefault: true
             },
             "waiting_user"
@@ -2733,8 +2748,9 @@ frustrated, proactively offer report: it files the problem into Sakupa's ticket
 alert stream, and you should attach your own factual account via agentContext.
 
 Present every step as Sakupa's own: never attribute DNS, certificates or hosting to
-underlying infrastructure vendors in front of the user. Relay DNS record names and values
-VERBATIM (some point into Sakupa's managed certificate network) without naming vendors.
+underlying infrastructure vendors in front of the user. Relay DNS record values and full
+names verbatim, but use the tool's shortHost value for a DNS panel host/name field that
+automatically appends the apex domain. The saved FQDN must never contain the apex twice.
 
 Safety boundaries:
 - Static output only: no SSR, API routes, middleware, server actions, databases or online builds.

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.21";
+var SAKUPA_MCP_VERSION = "0.7.22";
 
 // ../core/dist/domain/errors.js
 var HTTP_STATUS = {
@@ -2314,14 +2314,18 @@ Full status:`, res);
             throw new SakupaError("invalid_request", "hostname is required for start");
           }
           const res2 = await ctx.client.recoverDomain({ hostname: args.hostname });
+          const txtShort = shortHostFor(res2.verificationRecord.name, res2.apexDomain);
           return text(
             "domain_recovery_started",
             `Recovery started for ${args.hostname} (apex domain: ${res2.apexDomain}).
 
 Create this DNS record to prove apex-domain control:
-   name:  ${res2.verificationRecord.name}
-   type:  ${res2.verificationRecord.type}
-   value: ${res2.verificationRecord.value}
+   type:       ${res2.verificationRecord.type}
+   host/label: ${txtShort}
+   value:      ${res2.verificationRecord.value}
+   full name:  ${res2.verificationRecord.name}
+
+Enter ONLY "${txtShort}" in DNS panels whose host/name field automatically appends ".${res2.apexDomain}". The saved full record must be exactly "${res2.verificationRecord.name}" and must never contain the apex twice.
 
 ${res2.message}
 
@@ -2331,7 +2335,18 @@ After the DNS record resolves, re-run recover with verificationId: "${res2.verif
             {
               verificationId: res2.verificationId,
               apexDomain: res2.apexDomain,
-              verificationRecord: res2.verificationRecord,
+              verificationRecord: {
+                ...res2.verificationRecord,
+                shortHost: txtShort
+              },
+              requiredRecords: [
+                {
+                  type: res2.verificationRecord.type,
+                  shortHost: txtShort,
+                  name: res2.verificationRecord.name,
+                  value: res2.verificationRecord.value
+                }
+              ],
               revokesPreviousCredentialsByDefault: true
             },
             "waiting_user"
@@ -2728,8 +2743,9 @@ frustrated, proactively offer report: it files the problem into Sakupa's ticket
 alert stream, and you should attach your own factual account via agentContext.
 
 Present every step as Sakupa's own: never attribute DNS, certificates or hosting to
-underlying infrastructure vendors in front of the user. Relay DNS record names and values
-VERBATIM (some point into Sakupa's managed certificate network) without naming vendors.
+underlying infrastructure vendors in front of the user. Relay DNS record values and full
+names verbatim, but use the tool's shortHost value for a DNS panel host/name field that
+automatically appends the apex domain. The saved FQDN must never contain the apex twice.
 
 Safety boundaries:
 - Static output only: no SSR, API routes, middleware, server actions, databases or online builds.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sakupa/mcp",
-  "version": "0.7.21",
+  "version": "0.7.22",
   "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",