@koda-sl/baker-cli 0.216.0-dev.843330ec0 → 0.216.0

package/README.md

@@ -100,6 +100,17 @@ question — and nothing in the output said so. Both spellings of an option work
 (`--run-id` and `--runId`), as they always did. Run `baker schema <command>` to see
 every option a command takes.
 
+### Fresh reads: `--no-cache`
+
+Every command that caches takes `--no-cache`, and it skips **both** cache layers — the
+CLI's own disk cache and the server's. The Google, GA4, GSC, research and X families
+used `--no-cache` while LinkedIn and Meta used `--skip-cache`, a split that named our
+two cache layers rather than anything a caller wanted to choose between. Once an
+unrecognised option started failing the call, it broke every consumer that could not
+know which family it was talking to — including report refresh, which appends
+`--no-cache` for any source. `--skip-cache` is still accepted as the old spelling and
+is rewritten to `--no-cache` before parsing; it will be removed.
+
 Use `--output` to change format:
 
 | Format  | Description                        | Best for           | Available on |
@@ -885,7 +896,7 @@ The HTTP backend exposes more endpoints (catalogs, ad-studies, ad-images, labels
 - Tokens auto-refresh server-side (60-day rolling long-lived user tokens). On `code 190` reconnect Meta from the dashboard.
 - Account scoping: backend rejects any call against an account not in the picker selection — pick accounts via Settings → Connections → Meta Ads first.
 - All cached actions are keyed per company; two companies that connect to the same Meta account never share cache entries.
-- `--skip-cache` on any command forces a re-fetch.
+- `--no-cache` on any command forces a re-fetch.
 
 #### Restricted pixel fields
 
@@ -1114,7 +1125,7 @@ Each finding: `{id, area, check, status, severity, evidence, fix: {explanation,
 - Account scoping: backend rejects calls against an account not in the picker selection.
 - Pinned API version: `Linkedin-Version: 202606` (declared in `oauth/constants.ts`). Bump as a coordinated change — LinkedIn deprecates monthly with a ~12-month support window. The floor is `TRACKING_PARAM_DYNAMIC_MIN_API_VERSION` (`CREATIVE_NAME` needs 202606), asserted in `ads/linkedin/utils.test.ts`.
 - Cache TTLs: accounts/account-detail 1h, listings 30m, analytics 15m–6h (depends on date range), facets 7d, urn-resolve 1h, bid-pricing/forecast 6h, audience-size 1h.
-- `--skip-cache` (server-side) and `--no-cache` (client-side, where supported) on any command.
+- `--no-cache` on any command skips both cache layers (the CLI's own and the server's).
 
 #### LinkedIn-specific gotchas
 
@@ -1824,7 +1835,7 @@ Research data is cached server-side (shared across all callers). No local cache
 
 ---
 
-### Assets (`baker images`, `baker videos`, `baker avatars`, `baker testimonials`)
+### Assets (`baker images`, `baker videos`, `baker testimonials`)
 
 #### Image sourcing — verb-per-provider overview
 
@@ -2591,69 +2602,6 @@ baker testimonials tags
 
 ---
 
-### Avatars (`baker avatars`)
-
-Reusable AI presenters a company casts into images and video. An avatar holds one settled identity: an **identity sheet** (`sheetUrl`, a generated multi-view turnaround) plus the **subject description** (`subjectDescription`) that person is described with. Every render grounds on the sheet via `--reference` and reuses the subject description verbatim — that pairing is what keeps the same face across a whole campaign.
-
-`status` is `generating | ready | error | archived`; only `ready` can be cast. `create` returns immediately with `generating` because the identity sheet renders in the background (~30s). `likeness` is `synthetic` (invented from a description) or `licensed` (built from photographs of a real person, which requires `--likeness-confirmed`).
-
-#### `baker avatars list`
-
-List the company's avatars. Retired ones are hidden unless you ask for them. Rows are compact and deliberately omit `subjectDescription` — read it with `get`.
-
-```bash
-baker avatars list
-baker avatars list --status ready --output md
-baker avatars list --status archived --limit 10
-```
-
-#### `baker avatars get <handle>`
-
-Read one avatar: status, `sheetUrl` for `--reference`, and the `subjectDescription` to reuse verbatim. `--full` adds the whole written profile (persona, speech, motion, wardrobe, setting, guardrails, voice, source photos, created date).
-
-```bash
-baker avatars get marta
-baker avatars get marta --full --output md
-```
-
-#### `baker avatars create`
-
-Cast a new presenter. `--name` and `--subject` are required; `--subject` describes one person plainly (age, build, hair, skin, face) with no scene, lighting, camera, or wardrobe.
-
-```bash
-baker avatars create --name "Marta" \
-  --subject "woman in her early 40s, shoulder-length dark brown hair, light olive skin, warm open face" \
-  --persona "friendly product expert" --wardrobe "plain knit sweater" \
-  --guardrails "no competitor logos, no medical claims"
-
-# From photographs of a real person — both flags required together
-baker avatars create --name "Marta" --subject "…" \
-  --source-image "<imageId1>,<imageId2>" --likeness-confirmed
-```
-
-Optional: `--handle`, `--speech`, `--motion`, `--setting`, `--voice-id`, `--voice-description`. Returns `{ avatarId, handle, likeness, status }`.
-
-#### `baker avatars update <handle>`
-
-Edit an avatar. Profile flags are merged over the stored profile, so `--persona` alone keeps the subject description intact; an empty value clears the field it names (except `--subject`, which can only be replaced). Changing `--subject` requires `--regenerate-sheet` in the same call — otherwise the sheet still shows the person described before.
-
-```bash
-baker avatars update marta --wardrobe "charcoal blazer over a white tee"
-baker avatars update marta --subject "woman in her early 50s, silver bob, …" --regenerate-sheet
-baker avatars update marta --new-handle marta-founder --voice-id <voiceId>
-```
-
-#### `baker avatars delete <handle>`
-
-Remove an avatar. `--archive` retires it — it leaves the roster but past work and `@handle` mentions keep resolving. Without `--archive` it is deleted for good.
-
-```bash
-baker avatars delete marta --archive --dry-run
-baker avatars delete marta --archive
-```
-
----
-
 ### Winning Ads (`baker winning-ads`)
 
 Search the **ad-dna** corpus of scored "winning" competitor ads for reference creatives to reproduce (e.g. with `baker canvas`), and manage the brands your library tracks (`follow` / `following` / `feed` / `unfollow`). Each result carries a presigned media URL (~1h TTL), the ad's DNA summary, and scores. The CLI authenticates with the normal `BAKER_API_KEY`; the Baker backend proxies the request to the ad-dna service with a server-held token — no extra credential in the sandbox.
@@ -5555,7 +5503,6 @@ This CLI is designed for AI agent consumption. Key patterns:
 - **0.119.0**: `draft amend`/`draft show` land on both `baker ads google` and `baker ads linkedin` — a generic JSON-merge-patch to update any staged op in place plus a full-payload receipt, replacing remove+recreate as the correction path. Google gains `assets update` and `asset-groups create|update` (Performance Max asset groups are now their own entity — `ads create --format performanceMaxAssetGroup` never worked and is gone); `ads create --format video` moves from a bare YouTube id to `--video-assets` refs (**breaking flag change** — stage the video as an asset first); `--format demandGen` gains `--image-assets`/`--square-image-assets`/`--logo-image-assets` and flag-building for headlines/descriptions. LinkedIn's `draft list` now renders a readable Campaign group ▸ Campaign ▸ Creative tree by default (`--json` for raw), `creatives update` gains `--campaign` (re-parent while staged), and `campaigns update` passes create-only fields (`--group`/`--type`/`--locale`/`--associated-entity`) through when amending a `li_temp_*` staged create instead of always stripping them.
 - **0.150.0**: `baker landing critique` gains an `agent-washing` rule in the `copy` family — an autonomy claim ("fully autonomous", "while you sleep", "no human intervention") with no signal anywhere on the page about who oversees the agent (approval, review, override, undo/rollback, audit log, escalation) scores a warn. Page-scope, so a hero may defer the trust story to a later section; generic privacy boilerplate does not clear it. `CRITIC_VERSION` bumps to `2`.
 - **0.152.0**: `baker ads linkedin campaigns url-params <ad-set-id>` stages an ad set's URL tracking parameters (LinkedIn's `adTrackingParameters`) — `--param key=value` for fixed values (repeatable or `&`-joined), `--dynamic key=PLACEHOLDER` for values LinkedIn fills in per ad (`CAMPAIGN_NAME`, `CREATIVE_ID`, …), `--clear` to remove them. LinkedIn appends these to the landing URL of every ad in the ad set, including ads already running, so this replaces stamping the same UTM onto each ad's `--landing-url` — which missed later ads and double-appended keys the ad set already set. Account-level parameters remain UI-only (LinkedIn exposes no API for them).
-- **0.155.0**: new family `baker avatars list|get|create|update|delete` — company-scoped reusable AI presenters, typed from the shared `@baker/api` avatars contract. `get` returns the identity-sheet URL to pass to `baker studio generate --reference` plus the subject description to reuse verbatim, and every command's `hints` carry the next move (still building → re-check with `get`; changed `--subject` without `--regenerate-sheet` → the sheet is stale). `create` refuses `--source-image` without `--likeness-confirmed` and returns an `error.fix` telling the agent to ask the user for that permission; an unknown handle returns an `error.fix` pointing at `baker avatars list`. Profile flags on `update` merge over the stored profile instead of replacing it.
 - **0.153.0**: `baker landing critique` accepts several slugs in one call (`baker landing critique a b c`). `data.landings[]` always carries one entry per slug; a single slug additionally keeps the old top-level `data.slug`/`counts`/`dimensions`/`findings` shape, so existing readers are unaffected. An invalid or missing slug anywhere in the batch still fails the whole call up front. The scaffold's Stop-hook critique gate now emits one batched command instead of one line per stale landing.
 - **0.159.0**: `baker ads google ads update` takes the same content flags as `ads create` (`--format` + `--headlines`/`--descriptions`/image refs/…), and `--format app` becomes a flag-buildable format on both, with `--image-assets` wiring an App campaign ad's images (`AppAdInfo.images`) the same way Responsive Display does. Content flags without `--format` now fail instead of being silently dropped. An ad content update replaces **every field it sends** — a list has to include the entries you want to keep, while an optional asset list you omit is left untouched on the ad — and a partial payload (only the images, or Google's read-shaped `{"appAd":{…}}`) is rejected at stage time with the fields it's missing, instead of staging cleanly and blocking publish later. Content updates also record the staged image assets they consume as dependencies, so discarding an asset no longer leaves the ad pointing at nothing.
 - **0.167.0**: `baker ads google conversions update` stops staging two conversion-action changes Google always rejects. `status: "HIDDEN"` leaves the write contract — Google denies it on every conversion action ("the field's value is on a deny-list for this field"), and offering it made it the obvious pick for retiring an action gently, so a whole cleanup published nothing; the refusal now names the two changes that do work (`--no-primary` to stop bidding toward it while it keeps measuring, `status: "REMOVED"` to stop it counting). `HIDDEN` is unchanged everywhere it is *read* — an action hidden long ago still reads back. And an update against a conversion action **Google owns** — Smart campaign calls/directions, the in-ad lead form's submit, YouTube subscriptions and follow-on views, Floodlight and Search Ads 360 imports, store visits, codeless webpage actions — is refused at stage time, renames included, since Google rejects every write against one and its own interface will not change them either. Both refusals name what to do instead and tell the agent to carry on with the rest of the job.

package/dist/{chunk-CMPAHYLB.js → chunk-54GMUYWN.js}

@@ -16,9 +16,9 @@ import {
   shouldEscalate
 } from "./chunk-DZUVUGEP.js";
 
-// ../../.pnpm-store/v10/links/@/safe-stable-stringify/2.5.0/810146e81bae4e3a061fe487864f2fde80c4b03b886877dc0f1fffbc6480b67e/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/810146e81bae4e3a061fe487864f2fde80c4b03b886877dc0f1fffbc6480b67e/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();
@@ -1092,7 +1092,7 @@ function resolveAdaptFormats(params) {
   return params.formats ?? [];
 }
 
-// ../../.pnpm-store/v10/links/@/safe-stable-stringify/2.5.0/810146e81bae4e3a061fe487864f2fde80c4b03b886877dc0f1fffbc6480b67e/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;
@@ -1192,9 +1192,6 @@ var KLING_DURATIONS = [3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15];
 var GEMINI_OMNI_DURATIONS = [3, 4, 5, 6, 7, 8, 9, 10];
 var GEMINI_OMNI_ASPECT_RATIOS = ["16:9", "9:16"];
 var GEMINI_OMNI_IMAGE_MIMES = ["image/png", "image/jpeg", "image/webp"];
-var GROK_IMAGINE_DURATIONS = [1, 2, 3, 4, 5, 6, 7, 8, 9, 10];
-var WAN_27_DURATIONS = [2, 3, 4, 5, 6, 7, 8, 9, 10];
-var HAPPYHORSE_DURATIONS = [3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15];
 var ELEVENLABS_OUTPUT_FORMATS = [
   "mp3_22050_32",
   "mp3_44100_32",
@@ -1227,20 +1224,13 @@ var VIDEO_GENERATE_MODELS = [
   "google/gemini-omni-flash",
   "google/veo-3.1",
   "google/veo-3.1-fast",
-  "google/veo-3.1-lite",
-  "kwaivgi/kling-v3.0-pro",
-  "x-ai/grok-imagine-video",
-  "alibaba/wan-2.7",
-  "alibaba/happyhorse-1.1"
+  "kwaivgi/kling-v3.0-pro"
 ];
 var DEFAULT_VIDEO_GENERATE_MODEL = "google/gemini-omni-flash";
 var REFERENCE_TO_VIDEO_MODELS = [
   "bytedance/seedance-2.0",
   "bytedance/seedance-2.5",
-  "google/gemini-omni-flash",
-  "x-ai/grok-imagine-video",
-  "alibaba/wan-2.7",
-  "alibaba/happyhorse-1.1"
+  "google/gemini-omni-flash"
 ];
 function supportsReferenceToVideo(model) {
   return REFERENCE_TO_VIDEO_MODELS.includes(model);
@@ -1691,89 +1681,6 @@ var MODEL_REGISTRY = {
         cfg_scale: { kind: "number", min: 0, max: 1 }
       }
     },
-    "x-ai/grok-imagine-video": {
-      // The avatar workhorse. Measured best of the reference-capable models on
-      // identity retention AND aspect-ratio obedience, at the lowest rate of any
-      // video model we carry ($0.05/s at 480p). No audio at all — `generate_audio`
-      // is absent from its OpenRouter listing, so a talking head goes to Wan 2.7.
-      // NOTE: `x-ai/grok-imagine-video-1.5` is NOT a drop-in upgrade — it is
-      // described as plain image-to-video and drops the reference conditioning
-      // this entry exists for.
-      label: "Grok Imagine Video",
-      inputs: [],
-      optional_inputs: [{ kind: "image", mimes: OPENROUTER_IMAGE_MIMES }],
-      required: ["prompt"],
-      params: {
-        prompt: { kind: "string" },
-        aspect_ratio: { kind: "string", enum: ["16:9", "9:16", "1:1", "4:3", "3:4", "3:2", "2:3"] },
-        resolution: { kind: "string", enum: ["480p", "720p"] },
-        duration: { kind: "number", enum: GROK_IMAGINE_DURATIONS }
-      }
-    },
-    "alibaba/wan-2.7": {
-      // Reference-to-video AND native audio — the only model we carry with both,
-      // which makes it the landscape talking-head option.
-      //
-      // LANDSCAPE ONLY, measured. It advertises 9:16, 1:1, 4:3 and 3:4, and
-      // delivers 16:9 regardless: asked for vertical via `aspect_ratio: "9:16"`
-      // it returned 1280x720, and asked again via an explicit
-      // `size: "720x1280"` from its own `supported_sizes` it returned 1280x720
-      // again. The enum below is therefore what it DOES, not what it claims, so
-      // nobody pays for a vertical clip that comes back landscape. For a vertical
-      // avatar clip use `x-ai/grok-imagine-video` (silent) or animate a generated
-      // still with `google/veo-3.1-lite` (native audio, honours 9:16).
-      label: "Alibaba Wan 2.7",
-      inputs: [],
-      optional_inputs: [{ kind: "image", mimes: OPENROUTER_IMAGE_MIMES }],
-      required: ["prompt"],
-      params: {
-        prompt: { kind: "string" },
-        negative_prompt: { kind: "string" },
-        aspect_ratio: { kind: "string", enum: ["16:9"] },
-        resolution: { kind: "string", enum: ["720p", "1080p"] },
-        duration: { kind: "number", enum: WAN_27_DURATIONS },
-        seed: { kind: "number" },
-        generate_audio: { kind: "boolean" }
-      }
-    },
-    "alibaba/happyhorse-1.1": {
-      // Third reference-capable option: strong identity, correct ratios, no audio.
-      // First-frame only (no `last_frame`), so it cannot close a beat on a
-      // specified end pose the way Wan and Veo can.
-      label: "Alibaba HappyHorse 1.1",
-      inputs: [],
-      optional_inputs: [{ kind: "image", mimes: OPENROUTER_IMAGE_MIMES }],
-      required: ["prompt"],
-      params: {
-        prompt: { kind: "string" },
-        aspect_ratio: { kind: "string", enum: ["16:9", "9:16", "1:1", "4:3", "3:4", "21:9", "9:21"] },
-        resolution: { kind: "string", enum: ["720p", "1080p"] },
-        duration: { kind: "number", enum: HAPPYHORSE_DURATIONS },
-        seed: { kind: "number" }
-      }
-    },
-    "google/veo-3.1-lite": {
-      // The cheapest way to animate a still that carries a real face: same Veo
-      // family and the same escape from ByteDance's filter, at $0.05/s with audio
-      // at 720p against Veo 3.1's $0.40. That 8x is the difference between an
-      // avatar clip you iterate on and one you think twice about.
-      label: "Google Veo 3.1 Lite",
-      inputs: [],
-      optional_inputs: [{ kind: "image", mimes: OPENROUTER_IMAGE_MIMES }],
-      required: ["prompt"],
-      params: {
-        prompt: { kind: "string" },
-        negative_prompt: { kind: "string" },
-        aspect_ratio: { kind: "string", enum: ["16:9", "9:16"] },
-        resolution: { kind: "string", enum: ["720p", "1080p"] },
-        duration: { kind: "number", enum: [4, 6, 8] },
-        seed: { kind: "number" },
-        generate_audio: { kind: "boolean" },
-        person_generation: { kind: "string", enum: ["allow_all", "allow_adult"] },
-        enhance_prompt: { kind: "boolean" },
-        conditioning_scale: { kind: "number" }
-      }
-    },
     "google/veo-3.1-fast": {
       // Cheap test/iteration model. Forwarded by the backend via
       // `provider.options.google-vertex.parameters` (camelCased on the wire).
@@ -2148,7 +2055,6 @@ function validateValue(key, value, schema, model) {
 
 // ../canvas-contract/src/videoCost.ts
 var CREDITS_PER_USD = 100;
-var OPENING_FRAME_CREDITS = Math.ceil(0.03 * CREDITS_PER_USD);
 var SEEDANCE_USD_PER_SECOND = {
   "480p": 0.18,
   "720p": 0.5,
@@ -2169,37 +2075,12 @@ function seedance25UsdPerSecond(resolution) {
   return SEEDANCE_25_USD_PER_SECOND[resolution ?? DEFAULT_VIDEO_RESOLUTION] ?? SEEDANCE_25_FALLBACK_USD_PER_SECOND;
 }
 var FALLBACK_USD_PER_SECOND = 0.5;
-var MIN_BILLED_SECONDS = 5;
-var MODELS_WITH_BILLING_FLOOR = /* @__PURE__ */ new Set(["alibaba/wan-2.7", "alibaba/happyhorse-1.1"]);
-function billedSeconds(model, duration) {
-  return MODELS_WITH_BILLING_FLOOR.has(model) ? Math.max(duration, MIN_BILLED_SECONDS) : duration;
-}
 function seedanceUsdPerSecond(resolution) {
   return SEEDANCE_USD_PER_SECOND[resolution ?? DEFAULT_VIDEO_RESOLUTION] ?? FALLBACK_USD_PER_SECOND;
 }
 var USD_PER_SECOND = {
   // Kling publishes one flat rate across every resolution and mode.
   "kwaivgi/kling-v3.0-pro": { silent: 0.112, audio: 0.168 },
-  // The three reference-capable avatar models. Rates are the published
-  // per-second SKUs; see MIN_BILLED_SECONDS below for why a short clip still
-  // costs more than rate x duration.
-  "x-ai/grok-imagine-video": {
-    silent: 0.07,
-    audio: 0.07,
-    byResolution: { "480p": { silent: 0.05, audio: 0.05 }, "720p": { silent: 0.07, audio: 0.07 } }
-  },
-  // Flat $0.10/s across resolutions and modes, audio included.
-  "alibaba/wan-2.7": { silent: 0.1, audio: 0.1 },
-  "alibaba/happyhorse-1.1": {
-    silent: 0.1278,
-    audio: 0.1278,
-    byResolution: { "720p": { silent: 0.0988, audio: 0.0988 } }
-  },
-  "google/veo-3.1-lite": {
-    silent: 0.05,
-    audio: 0.08,
-    byResolution: { "720p": { silent: 0.03, audio: 0.05 } }
-  },
   // Veo prices 4K far above the base tier — and 4K is a selectable resolution,
   // so folding it into the base rate under-quotes the dearest clip we can make.
   "google/veo-3.1": {
@@ -2236,7 +2117,7 @@ function falSeedanceUsdPerSecond(resolution, buildsOnSourceClip = false) {
 }
 function estimateVideoCostUsd(input) {
   const { model, duration, resolution, generateAudio, buildsOnSourceClip } = input;
-  const seconds = billedSeconds(model, duration ?? DEFAULT_VIDEO_DURATION_S);
+  const seconds = duration ?? DEFAULT_VIDEO_DURATION_S;
   const sourceClipPremium = buildsOnSourceClip ? VIDEO_SOURCE_COST_MULTIPLIER : 1;
   if (isGeminiOmniModel(model)) {
     return GEMINI_OMNI_WINDOW_SECONDS * GEMINI_OMNI_USD_PER_SECOND * GEMINI_OMNI_WINDOW_MARGIN;
@@ -9074,4 +8955,4 @@ export {
   defaultRegistry,
   createEngineFromEnv
 };
-//# sourceMappingURL=chunk-CMPAHYLB.js.map
+//# sourceMappingURL=chunk-54GMUYWN.js.map