@koda-sl/baker-cli 0.231.0 → 0.232.1

package/README.md

@@ -2198,6 +2198,8 @@ baker images ingest https://img.freepik.com/free-photo/xyz.jpg --source magnific
 baker images ingest https://acme.com/hero.png --source firecrawl --external-url https://acme.com/pricing --context "competitor pricing hero"
 ```
 
+`--source` is a closed set, validated before the request so a wrong value costs nothing: `uploaded`, `website`, `google_testimonial`, `trustpilot_testimonial`, `instagram`, `magnific`, `brandfetch`, `google_images`, `firecrawl`, `screenshotone`, `iconify`, `giphy`, `pinterest`, `ai_generated`, `layer_edit`. Use `website` for an asset pulled off a company's own site.
+
 Returns `{ imageId, deduped, contentHash }`. When `deduped: true`, an existing library row is returned — no new bytes are stored. Max ingest size 25MB.
 
 **Flags:**
@@ -2404,8 +2406,11 @@ Width, height, aspect ratio, and format — read from the image header without f
 ```bash
 baker images dimensions ./logo.png
 baker images dimensions https://acme.com/hero.png
+baker images dimensions ./logo.png --output md --fields width,height
 ```
 
+Takes `--output json|md` and `--fields <a,b>` like the other image reads. As everywhere else in the CLI, `--fields` projects only the `md` and `files` formats — the default `json` output always returns the whole envelope.
+
 Response:
 
 ```json
@@ -2980,6 +2985,7 @@ baker actions list                         # default: bucketed (claimable, myCla
 # then most recent. The `blocked` bucket is ordered closest-to-ready first.
 baker actions list --bucketed=false --status pending
 baker actions list --bucketed=false --sort priority   # flat list, do-first order (default); use --sort recent for newest-first
+baker actions list --output md             # id-first Markdown; works for both the bucketed and flat shapes
 # With BAKER_CHAT_ID, the bucketed list folds in THIS chat's draft: staged creates appear in
 # `draftCreates`; published actions being completed/discarded/updated carry a `draftStatus` marker.
 # Only the caller's own chat draft is reflected — never another chat's staged work.
@@ -3000,6 +3006,9 @@ baker actions release <action-id>
 
 baker actions create --name "Build hero" --priority high --tags landing,creative --description "..."
 # → returns { ok, data: { tempId, draftCreateCount }, hints: [...] } — check hints for tags/priority/dependencies/description reminders
+# --temp-id is optional; use the returned tempId. A custom one must start with `temp_`
+# (temp_hero_copy, not hero_copy) and is rejected with a VALIDATION_ERROR otherwise — the prefix is
+# what tells a task staged in this chat apart from a published action id in link/update/complete/draft remove.
 # If the name/description reads as recurring or future-dated (e.g. "weekly", "every Monday", "schedule"),
 # create emits a hint to use `baker scheduled-actions create` instead of a Work Action.
 # If it instead names work a surface executes in-chat (a GTM container change, a site tag, an ad-platform