@koda-sl/baker-cli 0.251.0-dev.e7a1a227e → 0.252.0-dev.e7a1a227e

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -5793,6 +5793,7 @@ This CLI is designed for AI agent consumption. Key patterns:
5793
5793
 
5794
5794
  - **0.250.1**: `--avatar <handle>` on `baker studio generate` and `baker studio animate` never worked. Both were declared in `registerSchema` and read at the call site, but neither was in the command's own citty `args` — and citty does not reject an undeclared flag, it keeps it and sets it to `true`. So `--avatar elena` reached the route as `avatar: true` with `elena` dropped as a stray positional, and the body schema (`z.string()`) refused it. Documented since 0.217.0, broken since 0.217.0: casting an avatar into a render was not possible from the CLI at all, which is why a clip of a named presenter came back with neither the identity sheet nor the voice. Both flags are now declared. A new test in `command-reference-integrity` compares every registered schema against the args of the command that parses it, so the two cannot drift again — it found a third case on the way, `actions status`, whose schema advertised a `--refs` flag for what the command actually takes as positionals.
5795
5795
  - **0.251.0**: `--accent` on `baker avatars create|update` — the region an avatar's voice comes from, e.g. `"Spanish from Spain, Madrid accent"`. Its own field rather than a sentence inside `--speech`, because that is where it went to die: asked for "pace, register, accent", the agent wrote *"clear Spanish accent"* for a Madrid presenter, the video model read that as no accent, and the clip came out sounding like nowhere. A place can be checked; an adjective cannot. It reaches the render through `buildDeliveryDirection` as its own `ACCENT:` instruction, and `thinProfileHint` now names it first among the missing fields since it is the only one that fails silently — a clip with no accent still looks finished.
5796
+ - **0.252.0**: avatar voices removed. `--voice-id` / `--voice-description` are gone from `baker avatars create|update`, and an avatar no longer holds a voice at all — every clip is voiced by the video model as it renders, directed by the profile's `--accent`. The picker they replaced offered a voice, played its preview, and then shipped a clip that did not sound like it: the re-voice was speech-to-speech, which replaces timbre and keeps pronunciation, so the accent the user picked could never survive. Three other routes were built and judged on video before removing it — TTS + lip-sync (mouth), audio-driven avatar models (picture), and Seedance 2.5 driven by audio (refuses AI faces). Reasoning and the re-open condition: `docs/adr/0005-an-avatar-is-a-face-not-a-voice.md`.
5796
5797
  ## Publishing
5797
5798
 
5798
5799
  ### Auto-publish (CI)
package/dist/cli.js CHANGED
@@ -3698,7 +3698,6 @@ var avatarSummarySchema = z7.object({
3698
3698
  /** The identity sheet to wire into `--reference`. Absent until the build settles. */
3699
3699
  sheetUrl: z7.string().optional(),
3700
3700
  coverUrl: z7.string().optional(),
3701
- hasVoice: z7.boolean(),
3702
3701
  errorMessage: z7.string().optional()
3703
3702
  });
3704
3703
  var avatarDetailSchema = avatarSummarySchema.extend({
@@ -24489,7 +24488,6 @@ function rosterRow(avatar) {
24489
24488
  status: avatar.status,
24490
24489
  likeness: avatar.likeness,
24491
24490
  sheetUrl: avatar.sheetUrl ?? null,
24492
- hasVoice: avatar.hasVoice,
24493
24491
  avatarId: avatar.avatarId,
24494
24492
  ...avatar.errorMessage ? { errorMessage: avatar.errorMessage } : {}
24495
24493
  };