@koda-sl/baker-cli 0.111.0 → 0.113.0-dev.78e242dda

package/README.md

@@ -653,6 +653,47 @@ baker ads google library search-competitors "crm software" --location uk
 
 ---
 
+### Staged writes (`baker ads google budgets|campaigns|...`)
+
+Write commands **never touch the Google Ads API at stage time**. Each command stages a create/update/pause/resume/remove op against the current chat's draft (`BAKER_CHAT_ID`); the dashboard shows it as a pending "Google Ads" change, and the whole draft applies as one atomic `GoogleAdsService.Mutate` when the chat is published. Feature-flagged per company (`companies.googleAdsWriteEnabled`) — off by default = a fully simulated publish with zero real API calls.
+
+Reference not-yet-created resources with `g_temp_*` refs returned by earlier `create` commands (they map to Google's temporary negative-ID resource names inside one atomic batch).
+
+```bash
+# Build a Search campaign bottom-up, chaining temp refs
+baker ads google budgets create --customer-id 1234567890 --name "Search budget" --amount 50
+# → { ref: "g_temp_ab12", ... }
+baker ads google campaigns create --customer-id 1234567890 --name "Brand — Search" \
+  --channel-type SEARCH --budget-ref g_temp_ab12 --bidding-strategy MANUAL_CPC
+baker ads google ad-groups create --customer-id 1234567890 --name "Brand terms" --campaign-ref g_temp_<campaign>
+baker ads google keywords add --customer-id 1234567890 --ad-group-ref g_temp_<adgroup> --text "brand name" --match-type EXACT
+# Shared negative keyword list → attach to the campaign
+baker ads google keyword-lists create --customer-id 1234567890 --name "Brand exclusions"
+baker ads google keyword-lists add --customer-id 1234567890 --list-ref g_temp_<list> --text "free" --match-type BROAD
+baker ads google keyword-lists attach --customer-id 1234567890 --campaign-ref g_temp_<campaign> --list-ref g_temp_<list>
+
+# Batch keywords — one command stages the whole set as ONE request (up to 500)
+baker ads google keywords add --customer-id 1234567890 --ad-group-ref g_temp_<adgroup> \
+  --text "brand name, brand shop:PHRASE, brand store" --match-type EXACT
+baker ads google keyword-lists add --customer-id 1234567890 --list-ref <list-id> --file negatives.txt
+# negatives.txt: one keyword[:MATCH_TYPE] per line; blank lines and "# comments" are skipped
+# Responsive search ad
+baker ads google ads create --customer-id 1234567890 --ad-group-ref g_temp_<adgroup> \
+  --headlines "Fast Widgets,Buy Online,Free Shipping" --descriptions "Best widgets around.,Ships tomorrow." \
+  --final-url https://example.com
+
+# Review / undo staged changes
+baker ads google draft list
+baker ads google draft remove g_temp_ab12   # cascades to dependents
+baker ads google draft clear
+```
+
+Command groups: `budgets`, `campaigns`, `ad-groups`, `keywords` (add/update/remove), `negative-keywords`, `keyword-lists`, `ads`, `assets`, `audiences`, `conversions`, `bidding-strategies`, `labels`, `campaign-criteria`, and `draft`. Amounts are in major currency units (converted to micros). Money/bids: `--amount`, `--cpc-bid`, `--target-cpa` take major units; `--target-roas` a ratio. Less-common ops accept a `--file <payload.json>` (flags override file keys). Updates target a resource name or bare id as the positional argument; a target that names an op staged earlier **amends it in place**.
+
+**Batch keyword adds** — `keywords add`, `negative-keywords add`, and `keyword-lists add` take a whole batch in one command: comma-separate `--text` entries and/or pass `--file <list.txt>` (one keyword per line). A `:EXACT`/`:PHRASE`/`:BROAD` suffix per entry overrides the `--match-type` default. Batches stage all-or-nothing as one request (limit 500); each keyword still lands as its own draft op, so it stays individually removable/amendable.
+
+---
+
 ### Caching
 
 Google Ads data is cached at two levels:
@@ -2487,6 +2528,24 @@ Permissions enforced server-side:
 
 ---
 
+### `baker mcp list | add | remove`
+
+Manage **custom MCP servers** — point the agent at any remote HTTPS MCP endpoint. Registered tools appear as `mcp__<name>__*` on the next chat message.
+
+```bash
+baker mcp list
+baker mcp add --name weather --url https://mcp.example.com/mcp
+baker mcp add --name acme --url https://acme.dev/mcp --header "Authorization: Bearer sk-…"
+baker mcp add --name mine --url https://my.dev/mcp --scope user
+baker mcp remove --name weather
+```
+
+- `--url` must be HTTPS and public; loopback / private / cloud-metadata hosts are rejected.
+- `--scope company` (default) shares with every chat in the company; `--scope org` needs an admin API key; `--scope user` binds to the current message sender (requires running inside a chat turn — the bridge supplies the sender via `BAKER_ACTING_USER_ID`).
+- Repeat `--header "Key: Value"` for multiple auth headers. Header values are stored server-side and ride the MCP transport — `list` returns only the header keys, never the values.
+
+---
+
 ### `baker schema [command]`
 
 Inspect command argument schemas for AI agent introspection.
@@ -3822,6 +3881,8 @@ The two scaffold passes are billed (the full `video_deconstruct` is the heavy on
 
 #### `baker canvas scaffold-static-ad <image> [flags]`
 
+`<image>` is a **local path or an `http(s)` URL** (e.g. a presigned S3 link from ad-dna). A URL is passed straight into the `original` ingest node as `source: "url"` — do not `curl` it to a file first. Note a presigned URL embedded in the emitted canvas will **expire** (the `original` node is composition-only, so a later re-run just skips it); pass a stable URL or a local file if you need the canvas to stay runnable. For the URL case, `--out` defaults to the current directory — pass `--out` to scaffold two URL sources into distinct files, or the second run overwrites the first.
+
 Turn a source/inspiration image into a **runnable, self-validated static-ad canvas** — the static counterpart of `scaffold-video`. Like the video scaffold, this runs **billed Gemini passes** up front:
 
 1. **`image_describe`** (`~google/gemini-pro-latest`) — reverse-engineers the image into a blueprint JSON, written next to the canvas as **`prompt.json`**. This is the editable "prompt": you rewrite it by hand into the ad you want (palette, copy, claims, subjects). It feeds the generator directly — there is **no automatic brand-transform step**. The blueprint also names the **`winning_mechanisms`** — the special sauce that makes the ad a candidate winner, each tagged `kind` (verbal: rhyme/pun/rhythm; visual: unexpected crop, visual gag, juxtaposition, pattern interrupt, before/after; structural: hook order/reveal) with a `device` and `why_it_works` — so your rewrite rebuilds the mechanism that makes the ad win instead of adapting only the surface and losing it.
@@ -3841,7 +3902,7 @@ baker canvas run ./static-ad.canvas.json
 | Flag | Default | Effect |
 |---|---|---|
 | `--context <text>` | — | Known provenance (advertiser, category, market) to ground the describe. |
-| `--out <path>` | `<image-dir>/static-ad.canvas.json` | Where to write the canvas (`prompt.json` is written alongside). |
+| `--out <path>` | `<image-dir>/static-ad.canvas.json` (cwd when `<image>` is a URL) | Where to write the canvas (`prompt.json` is written alongside). |
 | `--describe-model <id>` | registry default (`~google/gemini-pro-latest`) | Override the `image_describe` model. |
 | `--select-model <id>` | registry default (`~google/gemini-flash-latest`) | Override the element-selection `text_generate` model. |
 | `--layout-model <id>` | registry default (`~google/gemini-flash-latest`) | Override the global-layout `text_generate` model. |

package/dist/{chunk-3JVYU72O.js → chunk-26K7V346.js}

@@ -24,9 +24,9 @@ var __toESM = (mod, isNodeMode, target) => (target = mod != null ? __create(__ge
   mod
 ));
 
-// ../../node_modules/.pnpm/safe-stable-stringify@2.5.0/node_modules/safe-stable-stringify/index.js
+// ../../.pnpm-store/v10/links/@/safe-stable-stringify/2.5.0/810146e81bae4e3a061fe487864f2fde80c4b03b886877dc0f1fffbc6480b67e/node_modules/safe-stable-stringify/index.js
 var require_safe_stable_stringify = __commonJS({
-  "../../node_modules/.pnpm/safe-stable-stringify@2.5.0/node_modules/safe-stable-stringify/index.js"(exports, module) {
+  "../../.pnpm-store/v10/links/@/safe-stable-stringify/2.5.0/810146e81bae4e3a061fe487864f2fde80c4b03b886877dc0f1fffbc6480b67e/node_modules/safe-stable-stringify/index.js"(exports, module) {
     "use strict";
     var { hasOwnProperty } = Object.prototype;
     var stringify = configure2();
@@ -890,7 +890,7 @@ function describeCause(c) {
   }
 }
 
-// ../../node_modules/.pnpm/safe-stable-stringify@2.5.0/node_modules/safe-stable-stringify/esm/wrapper.js
+// ../../.pnpm-store/v10/links/@/safe-stable-stringify/2.5.0/810146e81bae4e3a061fe487864f2fde80c4b03b886877dc0f1fffbc6480b67e/node_modules/safe-stable-stringify/esm/wrapper.js
 var import__ = __toESM(require_safe_stable_stringify(), 1);
 var configure = import__.default.configure;
 var wrapper_default = import__.default;
@@ -6252,4 +6252,4 @@ export {
   defaultRegistry,
   createEngineFromEnv
 };
-//# sourceMappingURL=chunk-3JVYU72O.js.map
+//# sourceMappingURL=chunk-26K7V346.js.map