@koda-sl/baker-cli 0.347.0-dev.043fc924c → 0.347.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.
@@ -1279,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  # 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 +3460,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)

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