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

package/README.md

@@ -5792,6 +5792,7 @@ This CLI is designed for AI agent consumption. Key patterns:
 - **0.217.0**: new family `baker avatars list|get|create|update|delete`, plus `--avatar <handle>` on `baker studio generate` and `baker studio animate` — company-scoped reusable presenters, typed from the shared `@baker/api` avatars contract. `--avatar` is the way to cast one: it grounds the render on the identity sheet, reuses the subject description verbatim, and records the avatar on the batch. Passing the sheet through `--reference` instead does none of those and leaves the batch unattributed, so the avatar can never show what it has appeared in; the route refuses a handle that is not `ready`, because generating a stranger is worse than an error. `get` returns the sheet URL and that description; 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, since only they can give it; 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.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.
+- **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.
 ## Publishing
 
 ### Auto-publish (CI)

package/dist/cli.js

@@ -3682,6 +3682,7 @@ var avatarProfileSchema = z7.object({
   subjectDescription: z7.string().trim().min(1).max(2e3),
   persona: z7.string().trim().max(2e3).optional(),
   speech: z7.string().trim().max(2e3).optional(),
+  accent: z7.string().trim().max(2e3).optional(),
   motion: z7.string().trim().max(2e3).optional(),
   wardrobe: z7.string().trim().max(2e3).optional(),
   setting: z7.string().trim().max(2e3).optional(),
@@ -24517,11 +24518,11 @@ function rosterHints(roster, statusFilter) {
   return hints;
 }
 function thinProfileHint(profile, handle) {
-  const missing = ["motion", "persona", "speech", "wardrobe", "setting"].filter(
+  const missing = ["motion", "persona", "speech", "accent", "wardrobe", "setting"].filter(
     (field) => !profile?.[field]?.trim()
   );
   if (missing.length === 0) return null;
-  return `MISSING ${missing.map((field) => `--${field}`).join(" ")}. A bare subject description holds the face still and nothing else, so clips of @${handle} come out stiff and generic \u2014 measured, filling these in nearly doubled the movement in the same brief. The user almost certainly told you how this person talks and carries themselves; put it in: \`baker avatars update ${handle} ${missing.map((field) => `--${field} "\u2026"`).join(" ")}\`.`;
+  return `MISSING ${missing.map((field) => `--${field}`).join(" ")}. A bare subject description holds the face still and nothing else, so clips of @${handle} come out stiff and generic \u2014 measured, filling these in nearly doubled the movement in the same brief. --accent is the one nobody guesses and the only one that fails silently: it decides the accent the avatar SPEAKS with in every clip, so name the region the user is writing to you from ("Spanish from Spain, Madrid accent") \u2014 "Spanish" on its own renders as no accent at all. The user almost certainly told you how this person talks and carries themselves; put it in: \`baker avatars update ${handle} ${missing.map((field) => `--${field} "\u2026"`).join(" ")}\`.`;
 }
 function creationHints(created, profile) {
   const thin = thinProfileHint(profile, created.handle);
@@ -24614,6 +24615,7 @@ var TEXT_FIELDS = [
   ["subject", "subjectDescription"],
   ["persona", "persona"],
   ["speech", "speech"],
+  ["accent", "accent"],
   ["motion", "motion"],
   ["wardrobe", "wardrobe"],
   ["setting", "setting"]
@@ -24702,7 +24704,12 @@ registerSchema({
       required: true
     },
     persona: { type: "string", description: "Who they are on camera \u2014 role, attitude, energy", required: false },
-    speech: { type: "string", description: "How they speak \u2014 pace, register, accent, verbal habits", required: false },
+    speech: { type: "string", description: "How they speak \u2014 pace, register, verbal habits", required: false },
+    accent: {
+      type: "string",
+      description: "Where their voice is FROM, as a place: 'Spanish from Spain, Madrid accent', 'Mexican Spanish', 'British English, London'. Name the region \u2014 an adjective like 'clear Spanish accent' is read by the video model as NO accent, and the clip comes out sounding like nowhere. Set it whenever the avatar will speak; the user's own language is the default to assume, not English.",
+      required: false
+    },
     motion: { type: "string", description: "Body language and gesture in video", required: false },
     wardrobe: { type: "string", description: "Default outfit when the brief does not name one", required: false },
     setting: { type: "string", description: "Default surroundings when the brief leaves them open", required: false },
@@ -24736,6 +24743,11 @@ var createCommand2 = defineCommand89({
     subject: { type: "string", description: "The person, plainly described \u2014 reused verbatim", required: false },
     persona: { type: "string", description: "Who they are on camera", required: false },
     speech: { type: "string", description: "How they speak", required: false },
+    accent: {
+      type: "string",
+      description: "Where their voice is FROM \u2014 name the region, e.g. 'Spanish from Spain, Madrid accent'",
+      required: false
+    },
     motion: { type: "string", description: "Body language in video", required: false },
     wardrobe: { type: "string", description: "Default outfit", required: false },
     setting: { type: "string", description: "Default surroundings", required: false },