@koda-sl/baker-cli 0.365.0-dev.846b2e487 → 0.365.0

package/README.md

@@ -110,21 +110,6 @@ question — and nothing in the output said so. Both spellings of an option work
 that lists every option: `baker schema <command>` (`check_schema`) when the command
 registers a schema, `baker <command> --help` (`check_help`) when it does not.
 
-### Narrowing a result: `--fields`
-
-`--fields a,b,c` works on every command that prints the JSON envelope. It keeps only
-those keys of each record in `data` — the rows when `data` is a list or wraps one
-(`baker chats list --fields id,title`), `data` itself when it is a single record
-(`baker experiment plan ... --fields traffic,warning`). `meta`, `hints` and warnings are
-kept, and a name no record carries is reported in `hints` alongside the keys that do
-exist. Commands that declare `--fields` themselves keep their own meaning
-(`ads meta insights` chooses which metrics to request; `ads linkedin creatives` takes dotted
-paths; `actions draft` picks the columns of `--output md|files` and leaves its JSON
-whole). A command whose default output is text needs `--output json` for there to be an
-envelope to narrow; without it a note on stderr says the flag changed nothing. A success
-that prints its result beside `ok` rather than under `data` (`canvas validate`,
-`canvas critique`) comes back whole, with a hint saying `--fields` was not applied.
-
 ### Fresh reads: `--no-cache`
 
 Every command that caches takes `--no-cache`, and it skips **both** cache layers — the
@@ -938,7 +923,7 @@ baker ads meta custom-conversions --account-id act_123 --full   # raw rule JSON,
 
 Meta writes mirror the Google/LinkedIn model: they **never hit the Graph API when you run them**. Each op is validated at stage time (field shapes, budget rules, page/Instagram identity ownership, CBO/ABO exclusivity, status-transition legality), shows in the dashboard chat as a pending Meta change, and applies only when the chat is published. Meta has no atomic batch mutate, so ops apply **sequentially** on publish — one failure skips its dependents but the publish completes.
 
-**That publish reaches the real ad account for every company** — Meta writes are generally available, with no per-company flag and no simulated mode to turn on. Discarding the chat before it completes is what undoes a staged change.
+**That publish reaches the real ad account for every company** — Meta writes are generally available, with no per-company flag. Discarding the chat before it completes is what undoes a staged change.
 
 Chain a full ad from scratch with `meta_temp_*` refs (each create returns one):
 
@@ -978,7 +963,7 @@ Status changes are `pause|resume|archive` subcommands on `campaigns`/`adsets`/`a
 - Identity columns (`campaign_name`, `ad_name`, etc.) appended automatically per `--level` so rows are self-describing.
 - Auto-async when the query is heavy (level=ad with breakdowns over an account, >2 breakdowns, >90-day range). Pass `--async` to force it or `--no-async` to refuse fallback.
 
-**Listings (`campaigns`/`adsets`/`ads`)** default to `effective_status=ACTIVE` — pass `--all-statuses` to widen, or `--effective-status ACTIVE,PAUSED` for a custom set.
+**Listings (`campaigns`/`adsets`/`ads`)** default to `effective_status=ACTIVE` — pass `--all-statuses` to widen, or `--effective-status ACTIVE,PAUSED` for a custom set. An empty filtered list carries a `hints` entry naming the filter and `--all-statuses` (on **stderr** for `--output csv|jsonl|md`), so "nothing active" is never read as "nothing there".
 
 **Pagination** is auto-drained (no manual cursor handling).
 
@@ -1155,7 +1140,7 @@ draft [list|remove <ref>|clear|amend <ref>|show <ref>]   # review/undo/amend sta
 
 Write commands never call the LinkedIn API at stage time. Each stages an op on the current chat's draft, fully validated at staging (field limits, enums, budget minimums, URN shapes, parent existence, Baker media readiness, status-transition legality). Validation errors are structured per-field; non-blocking warnings (Maximum Delivery when no `--bid`, budget below playbook floor, audience under 300 rows, >4 lead-form questions, audience expansion/LAN on) come back in the stage envelope. Ops apply when the chat is published.
 
-**That publish reaches the real ad account for every company** — LinkedIn writes are generally available, with no per-company flag and no simulated mode to turn on. Discarding the chat before it completes is what undoes a staged change.
+**That publish reaches the real ad account for every company** — LinkedIn writes are generally available, with no per-company flag. Discarding the chat before it completes is what undoes a staged change.
 
 ```bash
 # Chain creates via li_temp_* refs — group → campaign → creative in one chat
@@ -1475,7 +1460,7 @@ baker experiment fold                                            # make the page
 
 GA4 commands for multi-channel audits **and** for configuring what the property measures. Playbook-aligned report presets, property health audits, free-form Data API queries, and staged Admin API writes.
 
-Reads (`properties`, `config`, `audit`, `query`) happen immediately. Writes (`key-event`, `custom-dimension`, `custom-metric`, `custom-event`, `data-retention`, `audience`, `property`, `ads-link`, `enhanced-measurement`) are **staged** onto the chat, reviewed in the dashboard's Analytics tab, and applied when the chat completes — at which point they take effect on the property immediately. There is no simulated mode and no undo.
+Reads (`properties`, `config`, `audit`, `query`) happen immediately. Writes (`key-event`, `custom-dimension`, `custom-metric`, `custom-event`, `data-retention`, `audience`, `property`, `ads-link`, `enhanced-measurement`) are **staged** onto the chat, reviewed in the dashboard's Analytics tab, and applied when the chat completes — at which point they take effect on the real property immediately, with no undo.
 
 A Google Analytics connection made before writes shipped is read-only and every write command refuses with a message saying to reconnect. `baker ga4 config` reports `canWrite`.
 

package/dist/{chunk-K2IKLMCM.js → chunk-AI4HWQVN.js}

@@ -20,9 +20,9 @@ import {
   shouldEscalate
 } from "./chunk-2OKSJNLA.js";
 
-// ../../.pnpm-store/v10/links/@/safe-stable-stringify/2.5.0/766ad107c42df28eeadaf0ac2f9089c8a9e200f6ba0b2b1a817b8d536cbdcc49/node_modules/safe-stable-stringify/index.js
+// ../../node_modules/.pnpm/safe-stable-stringify@2.5.0/node_modules/safe-stable-stringify/index.js
 var require_safe_stable_stringify = __commonJS({
-  "../../.pnpm-store/v10/links/@/safe-stable-stringify/2.5.0/766ad107c42df28eeadaf0ac2f9089c8a9e200f6ba0b2b1a817b8d536cbdcc49/node_modules/safe-stable-stringify/index.js"(exports, module) {
+  "../../node_modules/.pnpm/safe-stable-stringify@2.5.0/node_modules/safe-stable-stringify/index.js"(exports, module) {
     "use strict";
     var { hasOwnProperty } = Object.prototype;
     var stringify = configure2();
@@ -1114,7 +1114,7 @@ function resolveAdaptFormats(params) {
   return params.formats ?? [];
 }
 
-// ../../.pnpm-store/v10/links/@/safe-stable-stringify/2.5.0/766ad107c42df28eeadaf0ac2f9089c8a9e200f6ba0b2b1a817b8d536cbdcc49/node_modules/safe-stable-stringify/esm/wrapper.js
+// ../../node_modules/.pnpm/safe-stable-stringify@2.5.0/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;
@@ -9904,4 +9904,4 @@ export {
   defaultRegistry,
   createEngineFromEnv
 };
-//# sourceMappingURL=chunk-K2IKLMCM.js.map
+//# sourceMappingURL=chunk-AI4HWQVN.js.map