@koda-sl/baker-cli 0.148.0 → 0.149.0-dev.7b64ca6b5

package/README.md

@@ -492,8 +492,6 @@ Command groups: `budgets`, `campaigns`, `ad-groups`, `keywords` (add/update/remo
 
 **Amending a staged op** — `draft amend <ref> (--file patch.json | --patch '<json>')` merges a JSON patch into an already-staged op's payload (objects deep-merge, `null` deletes a key, arrays/scalars replace) and re-validates it in full. Always prefer this over removing and re-staging — it preserves the op's ref (so dependents don't break) and its position in the draft. `draft show <ref>` prints the full staged payload (including warnings/annotations) so you can verify a change looks right before publish.
 
-**Already-satisfied writes aren't staged** — an update or pause/resume whose every field already holds the requested value on the live account is dropped instead of staged: the envelope returns `"staged": false, "noop": true` with a `reason` ("this ad is already Paused on Google Ads"), plus a hint. This is a success, not an error — there is nothing to publish. Only a positively-read live snapshot can trigger it; a failed or empty read always stages. Batch responses list the dropped ops under `skipped`, and `count` reflects what actually entered the draft.
-
 **Batch keyword adds** — `keywords add`, `negative-keywords add`, and `keyword-lists add` take a whole batch in one command: comma-separate `--text` entries and/or pass `--file <list.txt>` (one keyword per line). A `:EXACT`/`:PHRASE`/`:BROAD` suffix per entry overrides the `--match-type` default. Batches stage all-or-nothing as one request (limit 500); each keyword still lands as its own draft op, so it stays individually removable/amendable.
 
 ---
@@ -1750,6 +1748,8 @@ Returns `{ images: [{ imageId, imageUrl, deduped, width, height }], model, costU
 
 Brand logo via Brandfetch CDN (`fallback/404`). Probes all 5 logo variants in parallel and returns whichever ones the domain actually publishes. Auto-ingests the first by default.
 
+**Variants are returned wordmark-first** (`logo` dark → `logo` light → `symbol` dark → `symbol` light → `icon`), so the default `--auto-ingest 1` gives you the wide lockup a "trusted by" strip needs. `icon` is deliberately last: for many brands (Salesforce, HubSpot) it is a solid coloured square with the mark knocked out of it, which renders as a filled box beside the wordmarks around it and cannot be rescued with CSS. Reach for it only in slots under ~32px, and then ask for it explicitly.
+
 ```bash
 baker images logo stripe.com                       # all available variants
 baker images logo linear.app --variant logo        # just full wordmark logos (light + dark)
@@ -1757,13 +1757,16 @@ baker images logo linear.app --variant icon        # just the square app icon
 baker images logo linear.app --variant symbol      # just the bare brand mark (no wordmark), light + dark
 baker images logo example.com --no-auto-ingest     # browse without writing to library
 baker images logo stripe.com --auto-ingest 5       # ingest every returned variant
+baker images logo stripe.com,intercom.com,notion.so --variant logo   # a whole strip in one call
 ```
 
+**Multiple domains.** Pass a comma-separated list (max 20) to source an entire logo row in one call. Domains are fetched in parallel and a failure on one never loses the rest, so a partial strip is still placeable. The response shape switches to `{ results: [{ domain, hits, error? }] }`, and domains Brandfetch didn't know come back in a `hints[]` entry naming the fallback ladder. A single domain returns the original shape unchanged.
+
 **The 5 variants — pick by use case:**
 
 | `--variant` | `providerMeta.type` | `providerMeta.theme` | What it is | Typical use |
 |---|---|---|---|---|
-| `icon` | `icon` | `null` (single) | App-style square icon (favicon-grade), often rounded | Favicon, social proof grid, app-tile mock |
+| `icon` | `icon` | `null` (single) | App-style square icon (favicon-grade), often a **solid coloured plate** with the mark knocked out | Favicon and nav slots under ~32px only — **never a logo strip** |
 | `logo` | `logo` | `light` | Full wordmark designed for **light backgrounds** (dark ink on transparent) | Logo on white page, light hero |
 | `logo` | `logo` | `dark` | Full wordmark designed for **dark backgrounds** (light ink on transparent) | Footer on dark, dark hero |
 | `symbol` | `symbol` | `light` | Brand mark/glyph only (no wordmark) for **light backgrounds** | Compact UI, avatar, small-space placement |
@@ -2027,7 +2030,7 @@ Inputs accept a single path, a quoted glob, or a comma-separated list. Writes in
 Pipeline stages, each opt-in via flag presence and idempotent on already-correct input:
 
 1. Rasterize SVG (only when raster ops are requested — pure resize keeps SVG)
-2. `--remove-bg` → two-pass background removal with gradient/solid branching (skipped when the source is already transparent)
+2. `--remove-bg` → two-pass background removal with gradient/solid branching (skipped when the source is already transparent). "Already transparent" is decided by **solidity** — how completely the opaque pixels fill their own bounding box — not by a raw transparent-pixel count. An app-icon tile is only 5–8% transparent (its rounded corners) while being a solid coloured plate everywhere else, so a global count treated it as already-transparent and left the plate on. Plates measure ~0.8–1.0 solidity; real wordmarks measure 0.2–0.45.
 3. `--color <hex>` → recolor foreground pixels to the target color. Single-fill assets stay monochrome; multi-fill SVGs preserve relative contrast with target-color tones so foreground/background fills do not collapse into a solid shape.
 4. `--shrink-to-content` → trim transparent borders
 5. Resize:

package/dist/{chunk-2F5SCTNS.js → chunk-ZBRVPPJP.js}

@@ -7,9 +7,9 @@ import {
   __toESM
 } from "./chunk-RK67WL4O.js";
 
-// ../../node_modules/.pnpm/safe-stable-stringify@2.5.0/node_modules/safe-stable-stringify/index.js
+// ../../.pnpm-store/v10/links/@/safe-stable-stringify/2.5.0/810146e81bae4e3a061fe487864f2fde80c4b03b886877dc0f1fffbc6480b67e/node_modules/safe-stable-stringify/index.js
 var require_safe_stable_stringify = __commonJS({
-  "../../node_modules/.pnpm/safe-stable-stringify@2.5.0/node_modules/safe-stable-stringify/index.js"(exports, module) {
+  "../../.pnpm-store/v10/links/@/safe-stable-stringify/2.5.0/810146e81bae4e3a061fe487864f2fde80c4b03b886877dc0f1fffbc6480b67e/node_modules/safe-stable-stringify/index.js"(exports, module) {
     "use strict";
     var { hasOwnProperty } = Object.prototype;
     var stringify = configure2();
@@ -1070,7 +1070,7 @@ function resolveAdaptFormats(params) {
   return params.formats ?? [];
 }
 
-// ../../node_modules/.pnpm/safe-stable-stringify@2.5.0/node_modules/safe-stable-stringify/esm/wrapper.js
+// ../../.pnpm-store/v10/links/@/safe-stable-stringify/2.5.0/810146e81bae4e3a061fe487864f2fde80c4b03b886877dc0f1fffbc6480b67e/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;
@@ -7898,4 +7898,4 @@ export {
   defaultRegistry,
   createEngineFromEnv
 };
-//# sourceMappingURL=chunk-2F5SCTNS.js.map
+//# sourceMappingURL=chunk-ZBRVPPJP.js.map