drivethrough-cli 0.1.21 → 0.1.23

package/dist/main.mjs

@@ -24209,7 +24209,7 @@ function registerTools(server, ctx) {
     {
       title: "Read site files & history",
       description: 'Read back a deployed site: file manifest, file contents, drivethrough.json \u2014 and the site\'s version history. Use this to resume work on a site from an earlier conversation. Read the minimum you need: `find` locates text without returning file contents, `manifest_only` lists what exists, `paths` fetches only named files \u2014 a bare call inlines every text file, so reserve it for genuinely reading a whole small site. Versions: every deploy is a numbered version the platform keeps. `history: true` lists them with what each one changed (the map for revert_site), `compare: {from, to}` returns line diffs between two versions ("what did v9\u2192v10 change?"), and `version` pins any read mode to a prior version instead of the live one. Modes are exclusive per call \u2014 compare wins over history, history over find/manifest_only. Entries come back deploy_site-compatible ({path, content, encoding}); binary files are listed but only inlined when named in `paths`. For small text changes you may not need this at all \u2014 edit_site applies find/replace to the deployed files directly.',
-      annotations: { readOnlyHint: true, openWorldHint: false },
+      annotations: { readOnlyHint: true, destructiveHint: false, openWorldHint: false },
       inputSchema: {
         site: external_exports.string().describe("Site name or id"),
         paths: external_exports.array(external_exports.string()).optional().describe(
@@ -24285,7 +24285,7 @@ function registerTools(server, ctx) {
     {
       title: "Preview site (screenshot)",
       description: "See a deployed site the way a visitor does: renders the page in a real browser server-side and returns a screenshot image you can look at directly. You have no browser of your own \u2014 this is your only view of rendered results, so use it to verify visual work (layout, styling, animations, responsive behavior) actually shipped correctly instead of assuming it did, and to eyeball a prior `version` before reverting to it. Works on private sites; nothing becomes public. Takes a few seconds \u2014 look once after a coherent batch of changes, not after every edit. Animations: the capture happens at page load; pass wait_ms to let one settle or reach mid-cycle.",
-      annotations: { readOnlyHint: true, openWorldHint: false },
+      annotations: { readOnlyHint: true, destructiveHint: false, openWorldHint: false },
       inputSchema: {
         site: external_exports.string().describe("Site name or id"),
         path: external_exports.string().optional().describe('Page to render, like "/about.html" (default "/")'),
@@ -24367,7 +24367,7 @@ function registerTools(server, ctx) {
     {
       title: "Query site database",
       description: 'Read the site\'s database as its owner (read-only \u2014 writes go through write_db). Same query surface the site\'s own pages use, so what works here works there. Every row is {seq, type, parent_seq, json, created_at, updated_at}: `seq` is the row number and its permanent identity (never reused, even after a delete), `json` is the document. Newest-first is the default and always free. Filtering, sorting and search need a matching entry in the site\'s "query" block in drivethrough.json \u2014 an undeclared query is refused with the exact line to add. As the owner you get a bounded 5,000-row scan instead of a refusal, marked "partial": true, so you can look at data you have not modelled yet; a visitor page gets the refusal.',
-      annotations: { readOnlyHint: true, openWorldHint: false },
+      annotations: { readOnlyHint: true, destructiveHint: false, openWorldHint: false },
       inputSchema: {
         site: external_exports.string().describe("Site name or id"),
         action: external_exports.enum(["types", "list", "get"]).describe("types = row counts per type; list = rows of a type; get = one row by seq"),
@@ -24453,7 +24453,9 @@ function registerTools(server, ctx) {
     {
       title: "Write site database",
       description: "Write to the site's database as its owner: insert one row, import many, update, or delete (reads go through query_db). Rows are addressed by `seq`, the row number query_db returns. To change a few fields of a row, `update` with `merge` \u2014 only the fields that change, no fetch needed. Reserve `json` (wholesale replacement) for rewriting the whole document. To load a catalogue, use `rows` for a handful and `rows_url` for thousands \u2014 never loop insert, and never try to emit 100,000 rows yourself. Writes are validated against the types declared in the site's drivethrough.json (unknown types and mismatched fields are rejected, and a bulk import is checked in full BEFORE the first row is written, so it is all-or-nothing); pass validate: false only for a deliberate migration. Deleted and overwritten rows are gone for good \u2014 there is no version history for data, so read a row (query_db) before destructive rewrites you might need to undo. Deleting a row also deletes its children. Every write counts against the account's monthly write allowance, and an import larger than what remains is refused before anything is written.",
-      annotations: { readOnlyHint: false, destructiveHint: true, idempotentHint: false, openWorldHint: false },
+      // Open-world for the same reason deploy_site is: rows_url makes the
+      // platform fetch an arbitrary external URL server-side.
+      annotations: { readOnlyHint: false, destructiveHint: true, idempotentHint: false, openWorldHint: true },
       inputSchema: {
         site: external_exports.string().describe("Site name or id"),
         action: external_exports.enum(["insert", "update", "delete"]).describe("What to do with the row"),
@@ -24630,7 +24632,7 @@ function registerTools(server, ctx) {
     {
       title: "List sites",
       description: "List the authenticated account's sites with their addresses, visibility, and status. Pass include_deleted to also see recently deleted sites (recoverable for 30 days via restore_site).",
-      annotations: { readOnlyHint: true, openWorldHint: false },
+      annotations: { readOnlyHint: true, destructiveHint: false, openWorldHint: false },
       inputSchema: {
         include_deleted: external_exports.boolean().optional().describe("Also list deleted sites still inside their 30-day recovery window")
       }
@@ -24688,7 +24690,10 @@ function registerTools(server, ctx) {
     {
       title: "Attach/detach custom domain",
       description: 'Attach or detach a custom domain the user already owns (paid plans). "attach": connect the domain to the site \u2014 returns the exact DNS records to add; afterwards use check_domain {action: "connect"} for a one-click registrar link and check_domain {action: "status"} to poll until active. "detach": remove the domain from the site. The site keeps its drivethrough.site address throughout.',
-      annotations: { readOnlyHint: false, destructiveHint: true, idempotentHint: false, openWorldHint: false },
+      // Open-world like check_domain: attach initiates certificate issuance
+      // with an external CA — the pipeline check_domain "status" then polls —
+      // and detach changes what the public domain serves.
+      annotations: { readOnlyHint: false, destructiveHint: true, idempotentHint: false, openWorldHint: true },
       inputSchema: {
         action: external_exports.enum(["attach", "detach"]).describe("Connect the domain, or remove it"),
         site: external_exports.string().describe("Site name or id"),
@@ -28157,9 +28162,10 @@ no repo (built in chat).
 CLI limit errors are machine-readable and include an \`url\` to relay:
 \`\`\`json
 { "ok": false, "error": { "code": "plan_limit_public_sites",
-  "message": "...", "next": "...", "url": "https://drivethrough.dev/upgrade?reason=public_sites" } }
+  "message": "...", "next": "...", "url": "https://drivethrough.dev/pricing?reason=public_sites" } }
 \`\`\`
-Relay that upgrade link once, at the moment of intent \u2014 don't nag.
+Relay that link once, at the moment of intent \u2014 don't nag. It describes the
+plans; upgrading itself happens from the user's dashboard.
 Custom domain (one the user already owns): \`drivethrough domain add <site> example.com\`,
 then \`drivethrough domain connect <site>\` for one-click setup where supported.
 

package/package.json

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