drivethrough-cli 0.1.31 → 0.1.32

package/dist/main.mjs

@@ -40013,7 +40013,7 @@ var init_remote_assets = __esm({
 });
 
 // ../mcp-tools/src/output-schemas.ts
-var ok, site, deployResult, dataDoc, dnsRecord, fileEntry, testResult, OUTPUT_SCHEMAS;
+var ok, site, deployResult, dataDoc, dnsRecord, fileEntry, testResult, renderedRequest, OUTPUT_SCHEMAS;
 var init_output_schemas = __esm({
   "../mcp-tools/src/output-schemas.ts"() {
     "use strict";
@@ -40088,6 +40088,12 @@ var init_output_schemas = __esm({
       error: external_exports.string().nullish(),
       next: external_exports.string().optional()
     });
+    renderedRequest = external_exports.looseObject({
+      method: external_exports.string(),
+      url: external_exports.string(),
+      headers: external_exports.record(external_exports.string(), external_exports.string()),
+      body: external_exports.string().nullable()
+    }).describe("The request exactly as it would be sent, secret values replaced by [secret]");
     OUTPUT_SCHEMAS = {
       deploy_site: external_exports.looseObject({
         ok,
@@ -40255,7 +40261,8 @@ var init_output_schemas = __esm({
         actions: external_exports.record(external_exports.string(), external_exports.unknown()).optional().describe("Declared actions, their fields and triggering types"),
         schedules: external_exports.record(external_exports.string(), external_exports.unknown()).optional().describe("Each schedule's enabled, next_at, last_run_at, last_status, failures, disabled_reason"),
         webhooks: external_exports.record(external_exports.string(), external_exports.unknown()).optional().describe("Each webhook's url (what the other service POSTs to), verify, secret_set, last_event_at, last_status and setup steps"),
-        action_log: external_exports.array(external_exports.unknown()).optional().describe("The latest 20 outcomes, newest first"),
+        action_log: external_exports.array(external_exports.unknown()).optional().describe("The latest 20 outcomes, newest first \u2014 actions, schedules, webhooks and sampled page use of routes"),
+        reference: external_exports.string().optional().describe("With reference: true \u2014 the drivethrough.json integrations format and two complete examples"),
         next: external_exports.string().optional()
       }).describe("Everything declared plus recent outcomes"),
       request_secrets: external_exports.looseObject({
@@ -40271,6 +40278,13 @@ var init_output_schemas = __esm({
       test_route: testResult.describe("One GET through the route"),
       run_action: testResult.describe("One real run of the action"),
       run_schedule: testResult.describe("One real run of the schedule"),
+      preview_action: testResult.extend({ request: renderedRequest.nullish() }).describe("The request the action would send, secrets redacted; nothing was sent"),
+      preview_schedule: testResult.extend({
+        request: renderedRequest.nullish(),
+        next_row_seq: external_exports.number().nullish().describe("rotate: the row the next run would send"),
+        into: external_exports.string().optional().describe("pull: the type a response would be saved as"),
+        map: external_exports.record(external_exports.string(), external_exports.string()).optional().describe("pull: field \u2192 $.path in the response")
+      }).describe("What the next run would send, secrets redacted; nothing was sent"),
       preview_webhook: testResult.extend({
         url: external_exports.string().optional().describe("The URL the other service POSTs to"),
         row: external_exports.record(external_exports.string(), external_exports.unknown()).nullish().describe("The row an event like the sample would store (nothing is written)")
@@ -41156,24 +41170,27 @@ function registerTools(server, ctx) {
       }
     }
   );
-  const testTarget = (site2, kind, target, fields) => ctx.api.request("POST", `${sitePath(site2)}/integrations/test`, {
-    body: { target, kind, ...fields ? { fields } : {} }
+  const testTarget = (site2, kind, target, opts = {}) => ctx.api.request("POST", `${sitePath(site2)}/integrations/test`, {
+    body: { target, kind, ...opts.fields ? { fields: opts.fields } : {}, ...opts.dry ? { dry: true } : {} }
   });
   const fieldValues = external_exports.record(external_exports.string(), external_exports.union([external_exports.string(), external_exports.number(), external_exports.boolean()]));
+  const liveCheck = "To see a real run, ask the user to use the page once (submit the form, press the button, load the page), then read get_integrations' action_log.";
   server.registerTool(
     "get_integrations",
     {
       outputSchema: OUTPUT_SCHEMAS.get_integrations,
       title: "Get integrations",
-      description: `Show a site's connections to other services' APIs (Pro plan) and how they ran: which secrets are set (never their values), the declared routes and actions, each schedule's next run, last result and failures, each webhook's URL and last event, and the latest 20 outcomes. Read-only. THE CONFIGURATION FORMAT \u2014 integrations are declared in the site's drivethrough.json and deployed with deploy_site; once deployed, the platform runs them for the site, and the only operations you can perform on them are this tool, request_secrets, test_route, run_action, run_schedule and preview_webhook. A site can declare: "secrets" names the keys; "routes" proxies same-origin paths under /api/ext/<name> to an upstream, allowing only the listed methods and path prefixes and adding secret headers server-side (\${NAME}); "actions" POST a JSON body ({{field}} reads a row's field) when a type with "on_write" gets a row; "schedules" run every 1h/3h/6h/12h/1d/1w/1mo \u2014 "rotate" sends the next row of a type through an action, "pull" saves a route's JSON response as a new row ("map" uses $.dotted.paths; numeric strings become numbers); "webhooks" receive events another service POSTs to https://<site>/api/hook/<name> \u2014 "verify" is "stripe", "github", "standard" (Standard Webhooks: Resend, Clerk, Svix\u2026), "hmac_sha256" (with "header": the signature header's name) or, only for services that can't sign, "url_token"; "secret" names the declared secret; each verified event is mapped ("map", same $.paths) into a row of "into", which fires that type's on_write. Unverified, duplicate and replayed deliveries are never stored. No cron strings, no times of day, no timezones. Two complete examples \u2014 a read-only brokerage dashboard that also snapshots equity hourly for a chart: \`${INTEGRATION_EXAMPLE_A}\` \u2014 and a display that shows a quote when the owner clicks, and cycles through saved quotes every 3 hours: \`${INTEGRATION_EXAMPLE_B}\`. Every mistake is refused at deploy time with the corrected snippet \u2014 follow it. Keys are set with request_secrets; each piece is checked with test_route, run_action, run_schedule or preview_webhook. WHEN A DEPLOYED ACTION RUNS: when a visitor's form (or the owner's own button) on the page writes a row of a type with "on_write" \u2014 never from write_db, imports or schedule pulls. The only way for you to run one is run_action. Route access defaults to the owner only; set "access": "viewers" or "public" for pages others use. Schedules pause after 10 failures in a row (the owner gets one email); a deploy or a successful run_schedule re-enables them.`,
+      description: `Show a site's connections to other services' APIs (Pro plan) and how they last went: which secrets are set (never their values), the declared routes, actions, schedules (next run, last result, failures) and webhooks (URL, last event), and the latest 20 outcomes, including real page use. Read-only. Pass reference: true for the drivethrough.json format these are declared in, with two complete examples \u2014 read it before adding one to a site.`,
       annotations: { readOnlyHint: true, destructiveHint: false, idempotentHint: true, openWorldHint: false },
       inputSchema: {
-        site: external_exports.string().describe("Site name or id")
+        site: external_exports.string().describe("Site name or id"),
+        reference: external_exports.boolean().optional().describe("true: also return the drivethrough.json integrations format and two complete examples")
       }
     },
-    async ({ site: site2 }) => {
+    async ({ site: site2, reference }) => {
       try {
-        return ok2(await ctx.api.request("GET", `${sitePath(site2)}/integrations`));
+        const status = await ctx.api.request("GET", `${sitePath(site2)}/integrations`);
+        return ok2(reference ? { ...status, reference: INTEGRATION_REFERENCE } : status);
       } catch (error62) {
         return toolError(error62);
       }
@@ -41216,7 +41233,7 @@ function registerTools(server, ctx) {
             session,
             set: Object.fromEntries(secrets2.map((s2) => [s2.name, s2.set])),
             all_set: unset.length === 0,
-            next: unset.length ? `Still unset: ${unset.join(", ")}. Ask the user to finish on the page \u2014 or, if the link was used or expired, call request_secrets again without a session for a fresh one.` : "Every declared secret is set. Deploy (or redeploy) the site, then check each piece with test_route, run_action, run_schedule or preview_webhook."
+            next: unset.length ? `Still unset: ${unset.join(", ")}. Ask the user to finish on the page \u2014 or, if the link was used or expired, call request_secrets again without a session for a fresh one.` : "Every declared secret is set. Deploy (or redeploy) the site, then check each piece with preview_action, preview_schedule or preview_webhook, and have the user use the page once."
           });
         }
         const link = await ctx.api.request("POST", `${sitePath(site2)}/secrets/link`, {
@@ -41231,6 +41248,69 @@ function registerTools(server, ctx) {
       }
     }
   );
+  server.registerTool(
+    "preview_action",
+    {
+      outputSchema: OUTPUT_SCHEMAS.preview_action,
+      title: "Preview action",
+      description: `Show the exact request one of a site's declared actions would send for a sample row (Pro plan) \u2014 method, URL, headers and JSON body, with every secret value redacted \u2014 or why it can't be built (a secret not set, a bad URL). Nothing is sent, stored or charged. Check that the {{field}} values landed where they should. ${liveCheck}`,
+      annotations: { readOnlyHint: true, destructiveHint: false, idempotentHint: true, openWorldHint: false },
+      inputSchema: {
+        site: external_exports.string().describe("Site name or id"),
+        action: external_exports.string().describe(`The action's name under "actions" in drivethrough.json`),
+        fields: fieldValues.describe("Sample row values for its {{field}} references; {} when it uses none")
+      }
+    },
+    async ({ site: site2, action, fields }) => {
+      try {
+        return ok2(await testTarget(site2, "action", action, { fields, dry: true }));
+      } catch (error62) {
+        return toolError(error62);
+      }
+    }
+  );
+  server.registerTool(
+    "preview_schedule",
+    {
+      outputSchema: OUTPUT_SCHEMAS.preview_schedule,
+      title: "Preview schedule",
+      description: `Show what a site's declared schedule would send on its next run (Pro plan), with every secret value redacted: for "rotate", the row that comes next and the request its action would send; for "pull", the GET it would make and the type and map its response would fill. Nothing is sent, stored or charged, and the rotation doesn't move. get_integrations shows when it next runs and how its last run went.`,
+      annotations: { readOnlyHint: true, destructiveHint: false, idempotentHint: true, openWorldHint: false },
+      inputSchema: {
+        site: external_exports.string().describe("Site name or id"),
+        schedule: external_exports.string().describe(`The schedule's name under "schedules" in drivethrough.json`)
+      }
+    },
+    async ({ site: site2, schedule }) => {
+      try {
+        return ok2(await testTarget(site2, "schedule", schedule, { dry: true }));
+      } catch (error62) {
+        return toolError(error62);
+      }
+    }
+  );
+  server.registerTool(
+    "preview_webhook",
+    {
+      outputSchema: OUTPUT_SCHEMAS.preview_webhook,
+      title: "Preview webhook",
+      description: `Dry-run one of a site's declared webhooks (Pro plan): builds an event from sample field values, takes it through the same mapping and validation a real delivery gets, and returns the row it would store and the URL the other service must POST to. Nothing is stored, sent or charged. Real delivery is proven by the other service's own "send test event", then get_integrations (last event).`,
+      annotations: { readOnlyHint: true, destructiveHint: false, idempotentHint: true, openWorldHint: false },
+      inputSchema: {
+        site: external_exports.string().describe("Site name or id"),
+        webhook: external_exports.string().describe(`The webhook's name under "webhooks" in drivethrough.json (the <name> in /api/hook/<name>)`),
+        fields: fieldValues.describe("Sample values for the fields its map fills")
+      }
+    },
+    async ({ site: site2, webhook, fields }) => {
+      try {
+        return ok2(await testTarget(site2, "webhook", `/api/hook/${webhook.replace(/^\/?api\/hook\//, "")}`, { fields }));
+      } catch (error62) {
+        return toolError(error62);
+      }
+    }
+  );
+  if (!canDeployDirectory) return;
   server.registerTool(
     "test_route",
     {
@@ -41258,7 +41338,7 @@ function registerTools(server, ctx) {
     {
       outputSchema: OUTPUT_SCHEMAS.run_action,
       title: "Run action",
-      description: `Run one of a site's declared actions now, for real (Pro plan): it sends the action's POST to the other service with fields standing in for the row that would normally trigger it, and returns that service's HTTP status and a redacted preview of its response. The other service acts on it as it would on any request \u2014 a display shows the text, a message is sent \u2014 so confirm with the user before running anything that can't be taken back. This is the way to trigger an action by hand: write_db, imports and schedule pulls never fire actions.`,
+      description: `Run one of a site's declared actions now, for real (Pro plan): it sends the action's POST to the other service with fields standing in for the row that would normally trigger it, and returns that service's HTTP status and a redacted preview of its response. The other service acts on it as it would on any request \u2014 a display shows the text, a message is sent \u2014 so confirm with the user before running anything that can't be taken back. preview_action shows the same request without sending it.`,
       // Destructive + open-world: the other service may act irreversibly on the request.
       annotations: { readOnlyHint: false, destructiveHint: true, idempotentHint: false, openWorldHint: true },
       inputSchema: {
@@ -41269,7 +41349,7 @@ function registerTools(server, ctx) {
     },
     async ({ site: site2, action, fields }) => {
       try {
-        return ok2(await testTarget(site2, "action", action, fields));
+        return ok2(await testTarget(site2, "action", action, { fields }));
       } catch (error62) {
         return toolError(error62);
       }
@@ -41280,7 +41360,7 @@ function registerTools(server, ctx) {
     {
       outputSchema: OUTPUT_SCHEMAS.run_schedule,
       title: "Run schedule",
-      description: `Run one of a site's declared schedules once, now, for real (Pro plan), and return the outcome. A "pull" schedule calls its route and saves the response as a new row; a "rotate" schedule sends the next row through its action (the other service acts on it) and advances the rotation. A successful run also re-enables a schedule that was paused after repeated failures. The regular timetable is unchanged.`,
+      description: `Run one of a site's declared schedules once, now, for real (Pro plan), and return the outcome. A "pull" schedule calls its route and saves the response as a new row; a "rotate" schedule sends the next row through its action (the other service acts on it) and advances the rotation. A successful run also re-enables a schedule that was paused after repeated failures. The regular timetable is unchanged. preview_schedule shows the same run without sending anything.`,
       // Destructive + open-world: a rotate run fires an action the other service acts on.
       annotations: { readOnlyHint: false, destructiveHint: true, idempotentHint: false, openWorldHint: true },
       inputSchema: {
@@ -41296,29 +41376,8 @@ function registerTools(server, ctx) {
       }
     }
   );
-  server.registerTool(
-    "preview_webhook",
-    {
-      outputSchema: OUTPUT_SCHEMAS.preview_webhook,
-      title: "Preview webhook",
-      description: `Dry-run one of a site's declared webhooks (Pro plan): builds an event from sample field values, takes it through the same mapping and validation a real delivery gets, and returns the row it would store and the URL the other service must POST to. Nothing is stored, sent or charged. Real delivery is proven by the other service's own "send test event", then get_integrations (last event).`,
-      annotations: { readOnlyHint: true, destructiveHint: false, idempotentHint: true, openWorldHint: false },
-      inputSchema: {
-        site: external_exports.string().describe("Site name or id"),
-        webhook: external_exports.string().describe(`The webhook's name under "webhooks" in drivethrough.json (the <name> in /api/hook/<name>)`),
-        fields: fieldValues.describe("Sample values for the fields its map fills")
-      }
-    },
-    async ({ site: site2, webhook, fields }) => {
-      try {
-        return ok2(await testTarget(site2, "webhook", `/api/hook/${webhook.replace(/^\/?api\/hook\//, "")}`, fields));
-      } catch (error62) {
-        return toolError(error62);
-      }
-    }
-  );
 }
-var MAX_BUNDLE_MB, SERVER_INSTRUCTIONS, INTEGRATION_EXAMPLE_A, INTEGRATION_EXAMPLE_B;
+var MAX_BUNDLE_MB, SERVER_INSTRUCTIONS, INTEGRATION_EXAMPLE_A, INTEGRATION_EXAMPLE_B, INTEGRATION_REFERENCE;
 var init_tools = __esm({
   "../mcp-tools/src/tools.ts"() {
     "use strict";
@@ -41399,7 +41458,7 @@ RECIPE \u2014 a searchable, filterable list (catalogue, directory, archive)
    whose query the config doesn't declare (it will render empty for visitors),
    and a declaration no page uses (pure cost on every insert).
 
-Connecting a site to another service's API (Pro plan): this is site configuration, not something you run. The site's drivethrough.json declares it and deploy_site deploys it, like any other file; the format and two complete examples are in get_integrations' description. Every integration operation you can perform is its own tool: get_integrations (what is declared and how it ran), request_secrets (a one-time link where the user sets API keys \u2014 never ask for a key in the chat), test_route, run_action, run_schedule (one real run each) and preview_webhook (a dry run). Check each piece with them before telling the user it works.
+Connecting a site to another service's API (Pro plan): this is site configuration, not something you run. The site's drivethrough.json declares it and deploy_site deploys it, like any other file; get_integrations {reference: true} returns the format with two complete examples. The integration tools: get_integrations (what is declared and how it went), request_secrets (a one-time link where the user sets API keys \u2014 never ask for a key in the chat), and preview_action, preview_schedule, preview_webhook (show what would be sent or stored; nothing is sent). Preview each piece, then have the user use the page once and confirm the outcome in get_integrations before telling them it works.
 
 Custom domains (paid plans): manage_domain attaches a domain the user already owns. After attaching, check_domain {action: "connect"} looks up one-click setup at their registrar (relay the URL when offered, else the exact DNS records from attach), and check_domain {action: "status"} polls until "active" \u2014 DNS seen, then TLS issued.`;
     INTEGRATION_EXAMPLE_A = JSON.stringify({
@@ -41438,6 +41497,7 @@ Custom domains (paid plans): manage_domain attaches a domain the user already ow
       },
       schedules: { cycle: { every: "3h", rotate: "quote", action: "show" } }
     });
+    INTEGRATION_REFERENCE = `Integrations are declared in the site's drivethrough.json and deployed with deploy_site, like any other file. Keys: "secrets" lists the key names (values are set by the user via request_secrets, never in chat or a file). "routes" maps a same-origin path under /api/ext/<name> to an upstream, allowing only the listed "methods" and "paths" prefixes, adding "headers" server-side (\${NAME} inserts a secret); "access" is "owner" (default), "viewers" or "public"; "cache" and "query" are optional. "actions" declare a POST ("post" URL, "headers", JSON "body" where {{field}} inserts a row's field); a type with "on_write": "<action>" sends it when a visitor's form or the owner's button on the page saves a row \u2014 never for write_db, imports or schedule pulls. "schedules" repeat every 1h/3h/6h/12h/1d/1w/1mo (no cron strings, times of day or timezones): "rotate": "<type>" with "action" sends the next row of the type through the action; "pull": {route, path, into, map} saves a route's JSON response as a new row ("map" uses $.dotted.paths; numeric strings become numbers). They pause after 10 failures in a row (the owner gets one email) until the next deploy. "webhooks" receive events another service POSTs to https://<site>/api/hook/<name>: "verify" is "stripe", "github", "standard" (Standard Webhooks: Resend, Clerk, Svix\u2026), "hmac_sha256" (with "header": the signature header's name) or, only for services that can't sign, "url_token"; "secret" names the declared secret; "map" (same $.paths) fills a row of "into". Unverified, duplicate and replayed deliveries are never stored. Every mistake is refused at deploy time with the corrected snippet \u2014 follow it. Two complete examples \u2014 a read-only brokerage dashboard that also snapshots equity hourly for a chart: ${INTEGRATION_EXAMPLE_A} \u2014 and a display that shows a quote when the owner clicks, and cycles through saved quotes every 3 hours: ${INTEGRATION_EXAMPLE_B}.`;
   }
 });
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "drivethrough-cli",
-  "version": "0.1.31",
+  "version": "0.1.32",
   "description": "Agent-first hosting CLI. Say what you want. Stay in the car.",
   "type": "module",
   "license": "MIT",