@koda-sl/baker-cli 0.345.0-dev.9f4314fa9 → 0.346.0

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.
@@ -118,12 +120,14 @@ Use `--output` to change format:
 
 | Format  | Description                        | Best for           | Available on |
 |---------|------------------------------------|--------------------|--------------|
-| `json`  | Structured JSON envelope (default) | AI agents          | every command |
-| `files` | Tab-separated, one row per result  | Piping / shell     | every command |
-| `md`    | Markdown table                     | Human reading      | every command |
+| `json`  | Structured JSON envelope (default) | AI agents          | every command that prints the envelope |
+| `files` | Tab-separated, one row per result  | Piping / shell     | commands whose `baker schema` lists `output` |
+| `md`    | Markdown table                     | Human reading      | commands whose `baker schema` lists `output` |
 | `csv`   | RFC 4180 comma-separated values    | Analysis tools     | `baker research …` only |
 | `jsonl` | One JSON object per line           | Streaming/appending | `baker research …` only |
 
+`--output json` is accepted even by a command that declares no `--output`: the envelope is already what it prints, and on a command whose default is a readable view (`baker tags list`, the `draft` commands) it becomes that command's `--json`. The few commands that print only text — `baker analytics sending-events`, `baker canvas run` and `rerun` — refuse it, as a command without its own `--output` refuses `md` and `files`.
+
 `csv` and `jsonl` are implemented by the research family alone. Asking any other command for them — or for a format that does not exist — falls back to the JSON envelope and says so on stderr, rather than printing nothing and exiting 0.
 
 `files` and `md` print rows and nothing else, so any `hints` or data-quality note the envelope carries is written to **stderr** instead. Reading stdout alone still gives you clean, parseable rows.
@@ -1277,7 +1281,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 --output md  # everything these pages do, and which of it is counted, as tables
+baker analytics conversions --candidates  # everything these pages do, and which of it is counted
 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

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