pixelkiln 0.91.0 → 0.91.1

package/docs/CHARACTERS.md

@@ -286,10 +286,15 @@ character from it, with no template to pick. `frames` takes PixelLab's own
     `plan` says so; its `motionShare.animationGroupId` is `null`. If the
     leader's recorded group is gone from the character, the follower fails
     before spending and asks you to regenerate the leader.
-  - Verified against mocked HTTP only; not yet run live. A single south
-    direction was verified live through PixelKiln on an adopted v3 character:
-    "jumping with joy and pumping both fists", 8 frames at 96×96, billed 3,
-    with `animationId` and `animationGroupId` saved in the lock.
+  - **Verified live** (October 2026, an adopted v3 character): a south loop
+    ("jumping with joy and pumping both fists", 8 frames at 96×96, billed 3),
+    then `west` added to `directions`. Only `west` was planned and drawn; it
+    went into the south loop's recorded group, billed 3, and came back at
+    96×96 with the same timing as south: a crouch, both fists rising overhead,
+    and a return. PixelLab's character record then listed one group, named
+    after the leader, holding `south` and `west`, and its other animations
+    were untouched. Its free `east` mirror generated locally. Replacing one
+    direction (deleting it from a shared group) has not been run live.
 
 ### Pose frames and other loop controls
 

package/docs/ENDPOINTS.md

@@ -925,9 +925,15 @@ generations and finished in about two minutes:
   per direction asset. The first direction of a `directions` loop is sent
   without `animation_group_id`; each later one is sent after it with the
   leader's recorded `animation_group_id` and the group's own `animation_name`
-  (not inherited, so omitting it would rename the group). That append is
-  **mock-verified only**: the request shape follows the tool's documentation
-  and a live append has not been run. Verified live twice
+  (not inherited, so omitting it would rename the group). That append was
+  **verified live once** (October 2026): adding `west` to a generated `south`
+  loop sent the leader's `animation_group_id` and `animation_name`, the submit
+  and the finished job both answered with that same group, the job billed 3,
+  and `GET /characters/{id}` then listed the group under the leader's name
+  with `directions` `south` and `west` (each animation there is
+  `{ display_name, animation_group_id, directions: { <direction>: ... } }`),
+  with the character's other animations untouched. Deleting one direction of
+  a shared group has not been run live. Verified live twice
   with one south direction on a v3 character, once by a direct call and once
   through `pixelkiln gen` (a manifest loop on an `adopt`ed character, 8
   frames at 96×96, billed 3, then `pick` and `fetch`); a standard-engine

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pixelkiln",
-  "version": "0.91.0",
+  "version": "0.91.1",
   "description": "Manifest-driven pixel-art generation, review, recovery, and packaging with deterministic provenance.",
   "type": "module",
   "sideEffects": false,

package/skills/pixelkiln/references/pixellab-roadmap.md

@@ -43,8 +43,10 @@ and which tutorial(s) demonstrated real (not hypothetical) demand for it.
   (`animation.motionFrom`, lock `motionShare`). Adding a direction to a
   generated loop appends into its group, a regenerated leader marks followers
   stale, and a leader with no recorded group falls back to one request per
-  direction. **Mock-verified only; live proof pending** (a live append, and that
-  deleting one direction leaves the group and the others' motion intact).
+  direction. **A live append is verified** (adding `west` to a generated `south`
+  loop billed 3, joined the leader's group, and moved with the same timing).
+  Still unverified: that deleting one direction leaves the group and the
+  others' motion intact.
 
 - **Skeleton-v3 template loops** — `/characters/animations`'
   `mode: "skeleton-v3"` poses a template with the skeleton video model

package/skills/pixelkiln/references/pixellab.md

@@ -401,7 +401,8 @@ and came back at 96×96, so the canvas can grow. The plan still budgets 4. One
 request goes out per direction asset: the first direction of `directions`
 leads, and each later one follows in the next wave, sent into the leader's
 `animation_group_id` so every direction moves the same way (`animation.motionFrom`,
-lock `motionShare`; mock-verified only, docs/CHARACTERS.md, "Loops from a
+lock `motionShare`; a live append billed 3 and joined the group, deleting
+one direction of a group is unverified, docs/CHARACTERS.md, "Loops from a
 sentence"). The
 `prompt` is required and gets no style prefix or suffix.