@koda-sl/baker-cli 0.347.0-dev.043fc924c → 0.348.0-dev.78a35388f

package/README.md

@@ -37,6 +37,8 @@ export BAKER_CHAT_ID="<chat-id>"
 ```
 
 - `BAKER_API_KEY` must start with `bk_` (or `bkr_` for the read-only credential a Session review runs with)
+- A missing or malformed `BAKER_API_KEY` / `BAKER_API_URL` ends any command that talks to Baker with `NOT_CONFIGURED` (non-retryable, with a `fix`) naming the variable and the rule it broke — never its value
+- A malformed `BAKER_GOOGLE_ADS_CUSTOMER_ID`, `BAKER_LINKEDIN_AD_ACCOUNT_ID` or `BAKER_X_ADS_ACCOUNT_ID` ends it with `VALIDATION_ERROR` instead, whose `fix` says to correct or unset the variable
 - `BAKER_API_URL` is your Convex site URL — the deployment the CLI talks to, not an address to show anybody
 - `BAKER_PUBLIC_API_URL` — Baker's own host for the public API (`https://api.withbaker.com`). Set for you; not one to export by hand. It is what `analytics sending-events` publishes the `POST /v1/events` contract on, so that an integration written by a client's developers never names a deployment. Where it is unset the contract falls back to `BAKER_API_URL`, which keeps the printed request runnable against a deployment that fronts itself.
 - `BAKER_GOOGLE_ADS_CUSTOMER_ID` — default Google Ads customer ID (10 digits). Used when `--customer-id` is not passed. If neither is set and the account has exactly one Google Ads customer, it is auto-selected.
@@ -302,7 +304,7 @@ Read it before interpreting any null. Field coverage is folded page by page on t
 }
 ```
 
-Never total or count from a response carrying it — re-run with `--all --limit 10000 --out data.csv` (the API accepts page sizes up to 10,000) and check the re-run came back without the warning. A read that returns one row by construction — `FROM customer` with no segment selected, such as `--preset account-summary` — has no page to fill, so it never carries `TRUNCATED_RESULTS`, nor `CONVERSION_MIX`, since one account-wide row has no campaigns to total or compare. Warnings reach every output format, so no `--output` choice can hide one:
+Never total or count from a response carrying it — re-run with `--all --limit 8192 --out data.csv` (one read returns at most 8,192 rows; split a bigger data set into narrower queries — a shorter date range or one campaign each) and check the re-run came back without the warning. A read that returns one row by construction — `FROM customer` with no segment selected, such as `--preset account-summary` — has no page to fill, so it never carries `TRUNCATED_RESULTS`, nor `CONVERSION_MIX`, since one account-wide row has no campaigns to total or compare. Warnings reach every output format, so no `--output` choice can hide one:
 
 | `--output` | Where warnings land |
 |------------|---------------------|
@@ -341,11 +343,11 @@ The same lines also go to stderr. A read with nothing to report prints none of i
 |-----------------|--------------------------------------------------------------|
 | `--customer-id` | Google Ads customer ID (10 digits, no dashes). Falls back to `BAKER_GOOGLE_ADS_CUSTOMER_ID` env var. |
 | `--preset`      | Named query template (see presets below)                     |
-| `--date-range`  | Override preset date range (LAST_7_DAYS, LAST_30_DAYS, etc.) |
+| `--date-range`  | Override preset date range: a Google literal (LAST_7_DAYS, LAST_30_DAYS, LAST_MONTH, etc.) or `BETWEEN 'YYYY-MM-DD' AND 'YYYY-MM-DD'` — there is no LAST_90_DAYS |
 | `--include-paused` | Include paused entities in preset results. Off by default: presets return only actually-serving entities (enabled campaign **and** ad group **and** ad). Google Ads has no single serving flag, so the whole chain must be `ENABLED` for an entity to serve. |
-| `--limit`       | Max rows per page (default 200)                              |
+| `--limit`       | Max rows per page (default 200, at most 8,192)               |
 | `--cursor`      | Pagination cursor from previous response                     |
-| `--all`         | Auto-paginate all results. Exhausts the pages, not the statement's `LIMIT` — pair it with a `--limit` above the expected row count, and a read that still fills its cap is flagged `TRUNCATED_RESULTS` either way |
+| `--all`         | Auto-paginate all results. Exhausts the pages, not the statement's `LIMIT` — pair it with a `LIMIT` in the statement above the expected row count (at most 8,192 — split bigger reads into narrower queries), and a read that still fills its cap is flagged `TRUNCATED_RESULTS` either way |
 | `--out`         | Write data to file (format from extension: .csv, .jsonl, .json) |
 | `--append`      | Append to existing file (skip CSV headers)                   |
 | `--output`      | Output format: `json` \| `csv` \| `jsonl` \| `md`           |
@@ -389,6 +391,8 @@ The CLI rejects or automatically corrects common GAQL mistakes before hitting th
 | `shopping_performance_view.product_*` | Rewrites to `segments.product_*` | Field renamed |
 | `campaign.status = 'ACTIVE'` | Rewrites to `= 'ENABLED'` | Enum corrected |
 | `segments.conversion_action_name` with `metrics.cost_micros` | Rejects; split into separate conversion-action and spend queries | `INCOMPATIBLE_FIELDS` with `fix.action: "split_query"` |
+| `DURING` with a literal Google does not accept (`LAST_90_DAYS`, `LAST_12_MONTHS`, `THIS_YEAR` …) | Rejects before any request; `DURING` takes only `TODAY`, `YESTERDAY`, `LAST_7_DAYS`, `LAST_14_DAYS`, `LAST_30_DAYS`, `LAST_BUSINESS_WEEK`, `THIS_MONTH`, `LAST_MONTH`, `THIS_WEEK_SUN_TODAY`, `THIS_WEEK_MON_TODAY`, `LAST_WEEK_SUN_SAT`, `LAST_WEEK_MON_SUN` | `INVALID_DATE_RANGE`, with `fix.correctedCommand` spelling the same window as `BETWEEN 'YYYY-MM-DD' AND 'YYYY-MM-DD'` |
+| `--limit` outside 1–8,192, or a statement `LIMIT` above 8,192 | Rejects before any request — one read returns at most 8,192 rows | `VALIDATION_ERROR` naming the cap and how to split a bigger read; a statement `LIMIT` also gets `fix.correctedCommand` at `LIMIT 8192` |
 | `FROM ad_group_criterion` without `negative` field | Warns | `"ad_group_criterion returns BOTH positive and negative keywords. Use --preset positive-keywords or negative-keywords."` |
 
 Auto-fixed queries proceed normally. Warnings appear in the response:
@@ -1279,7 +1283,7 @@ baker analytics tracking --platform meta  # the same for one platform, read from
 baker analytics map --platform google --set kw=keyword    # name a parameter, seen or not yet
 baker analytics map --platform google --remove kw         # take that answer back
 baker analytics conversions               # what counts, what each produced, and which Forms count nothing
-baker analytics conversions --candidates  # everything these pages do, and which of it is counted
+baker analytics conversions --candidates --output md  # everything these pages do, and which of it is counted, as tables
 baker analytics conversions --flow contact          # one Form's endings as event keys, traffic or not
 baker analytics conversions --event page:request_demo --name "Demo requested"
 baker analytics conversions --event page:a --event submit:b --name "Lead"   # both, as one number
@@ -3458,9 +3462,7 @@ baker actions update <tempId> --description "..."   # a tempId from `create` in
 # ...folds into the staged create op — flesh out a task you just created instead of removing and recreating it
 baker actions complete <action-id-or-tempId> --note "What was done"  # stages — applies on chat publish
 # --note is REQUIRED (≥20 chars): what changed, where, and the outcome. It is the durable, client-facing
-# record surfaced by `baker actions log` and shown on the Task, so it is written in product terms: a note carrying
-# a file path, a platform account id, an error code or a `baker` command is rejected with a VALIDATION_ERROR naming them,
-# as is a missing/too-short note.
+# record surfaced by `baker actions log`. A missing/too-short note is rejected with a VALIDATION_ERROR.
 baker actions discard <action-id> --reason "obsolete"
 
 # Tags — taxonomy is built-in defaults + company custom tags; --tags is STRICT (unknown slugs are rejected)
@@ -3924,8 +3926,9 @@ baker canvas sync-definition src/creatives/<slug>/
 # 3. Inspect a finished run (per-node timing, file list, optional video thumbs)
 baker canvas inspect <run_id>
 
-# 4. Discover what's available (all node types, all models, all compositions)
-baker canvas catalog | jq
+# 4. Discover what's available: a one-line index of every node, then one node's full schema
+baker canvas catalog
+baker canvas catalog --node video_generate
 
 # 5. Safely edit a node's prompt without hand-jq (UTF-8 safe — use --text-file for
 #    multi-line / accented copy; the edit is re-validated before it is written back)
@@ -5228,8 +5231,8 @@ The tables above mirror `packages/canvas-contract/src/registry.ts` at the time o
 
 ```bash
 baker canvas catalog | jq '.categories | keys'
-baker canvas catalog | jq '.categories.image_generate[].id'
-baker canvas catalog | jq '.categories.video_generate[]'
+baker canvas catalog --node image_generate | jq '.entries[0].params'
+baker canvas catalog --node video_generate | jq '.entries[0].params'
 ```
 
 The validator surfaces unknown models / illegal aspect ratios / out-of-range params / missing required inputs with `did_you_mean` hints **before** the run starts.
@@ -5549,11 +5552,18 @@ Resolves the run dir against `--outputs-dir` (default `./canvas`) or accepts an
 
 #### `baker canvas catalog`
 
-Prints the agent-facing node + composition catalog as JSON Schema. Every node has `id`, `version`, `location`, `category`, `summary`, `inputs`/`params`/`outputs` schemas, `cost_estimate_credits`, `runtime_estimate_seconds`, and (when present) `when_to_use`. Grouped by `category`. The `compositions` array enumerates every `@baker/*` composition with its full `meta.json`.
+Prints the agent-facing node catalog. By default it is a compact index (a few KB): `categories` (category → node ids) and `nodes` (node id → one line), plus `hints`. Ask for full JSON Schemas by name:
+
+- `--node <id>[,<id>…]` — those nodes' full entries: `id`, `version`, `location`, `category`, `summary`, `when_to_use`, `inputs`/`params`/`outputs` schemas, `cost_estimate_credits`, `runtime_estimate_seconds`.
+- `--category <name>` — narrow the index to one category; add `--full` for that category's full entries.
+- `--full` — every node's full entry (~160 KB).
+
+An unknown node or category exits 1 with `{ ok: false, error: { code: "NOT_FOUND", fix } }` naming the valid ones.
 
 ```bash
-baker canvas catalog | jq '.categories | keys'
-baker canvas catalog | jq '.compositions[].id'
+baker canvas catalog
+baker canvas catalog --node video_generate
+baker canvas catalog --category audio --full
 ```
 
 ---

package/dist/{chunk-KGDL7F7M.js → chunk-2IC3CGQO.js}

@@ -1,10 +1,10 @@
 import {
   ApiError,
   apiGet
-} from "./chunk-XPUSSDLR.js";
+} from "./chunk-4QXKWIFC.js";
 import {
   getEnv
-} from "./chunk-4VP5WWPR.js";
+} from "./chunk-2OKSJNLA.js";
 
 // src/error-handler.ts
 var REQUEST_CONNECTION_PLATFORM = {
@@ -294,4 +294,4 @@ export {
   writeAdsOutput,
   resolveCustomerId
 };
-//# sourceMappingURL=chunk-KGDL7F7M.js.map
+//# sourceMappingURL=chunk-2IC3CGQO.js.map