@koda-sl/baker-cli 0.370.0 → 0.372.0

package/README.md

@@ -110,6 +110,22 @@ 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`). Naming a key of the wrapper beside
+keys of its rows narrows both. `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
@@ -3914,12 +3930,19 @@ baker canvas validate my-canvas.json
 #    or the same ad rendered once per aspect ratio instead of one hero + a terminal
 #    image_aspect_adapt (IMAGE_PARALLEL_FORMAT_RENDERS — separate renders drift in type,
 #    crop, and color, so the sizes stop matching).
+#    A generator prompt is measured with its {{slots}} filled from text nodes and local
+#    prompt.json/text ingests: past the model's character cap it is refused as
+#    PROMPT_OVER_MODEL_LIMIT, naming the node and the overshoot, before anything bills.
+#    `scaffold-static-ad` runs the same check on the prompt.json it writes and, when it is over,
+#    still writes the canvas and returns the overshoot in `hints[]` — trim prompt.json, then validate.
 
 # 2. Run (executes nodes, writes files to ./canvas/<run_id>/)
 baker canvas run my-canvas.json
 #    Advisory warnings print as `[warn] <CODE>: …` before anything bills.
 #    Only nodes reachable from the declared output execute (orphaned nodes are skipped,
 #    not billed). Add --keep-runs N to prune old r_* run dirs, keeping the N newest.
+#    A failed run reports `error.code: "input_invalid"` when the backend refused a node's
+#    own input (it fails the same way until the input changes), `"runtime"` otherwise.
 
 # 2b. Independent nodes ALREADY fan out in parallel — every node in the same
 #     topological layer (e.g. all the per-clip video_generate nodes) runs concurrently

package/dist/{chunk-L4QXAYIC.js → chunk-4ACU7GBN.js}

@@ -2,13 +2,13 @@ import {
   handleConnectionError,
   needsConnectionFix,
   writeAdsJson
-} from "./chunk-FXVELNAS.js";
+} from "./chunk-ZI7TPBXB.js";
 import {
   ApiError
-} from "./chunk-MZQC4LII.js";
+} from "./chunk-MF7YA62W.js";
 import {
   getEnv
-} from "./chunk-2OKSJNLA.js";
+} from "./chunk-HJEMOSPH.js";
 
 // src/commands/ads/meta/shared.ts
 var DAY_MS = 864e5;
@@ -120,4 +120,4 @@ export {
   resolveEffectiveStatus,
   statusFilterHints
 };
-//# sourceMappingURL=chunk-L4QXAYIC.js.map
+//# sourceMappingURL=chunk-4ACU7GBN.js.map