pixelkiln 0.40.0 → 0.41.0

package/docs/CLI.md

@@ -177,9 +177,13 @@ changed upstream, after editing it in the provider's own editor, for
 example. Unchanged objects are reported as such and left alone; a changed
 object replaces the local file only if that file still hashes to what
 PixelKiln wrote, so a local hand edit is never overwritten without `--force`.
-The lockfile then records the new bytes as this generation. Objects with no
-durable reference (PixelLab pixflux images, for one) are not eligible; use
-`pixelkiln edit` for those.
+The lockfile then records the new bytes as this generation. A character's
+rotations and frames are re-resolved from the character itself first, since
+PixelLab stamps their URLs with the last edit time and a cache can keep
+serving an old stamp; a character deleted upstream fails its entry instead
+of silently keeping the old bytes. Objects with no durable reference
+(PixelLab pixflux images, for one) are not eligible; use `pixelkiln edit`
+for those.
 
 When a style sets `enforcePalette`, `fetch` snaps each downloaded PNG to the
 style's palette before writing it and records the raw hash and the palette on
@@ -401,9 +405,10 @@ lock entry is shown at integer zoom on a transparency checkerboard, grouped by
 style, with its provenance one click away: the prompt actually sent, provider
 and generator, dimensions, recorded cost, lock status and plan state, submit
 and download times, job and object ids, every output with its path, SHA-256,
-size, and on-disk status, revision lineage, the quality record (palette,
-native-grid detection, audit, named approval), the manifest asset as declared,
-and raw provider metadata.
+size, and on-disk status, revision lineage, a character's parent and the
+states and loops that hang off it, the quality record (palette, native-grid
+detection, audit, named approval), the manifest asset as declared, and raw
+provider metadata.
 
 ```bash
 pixelkiln gallery

package/docs/ENDPOINTS.md

@@ -289,6 +289,13 @@ once a 1-generation re-roll exists: forty re-rolls cost one `1dir` call.
 - `pixflux`/`pixen`/`bitforge` results are **not account objects** at all.
   Bytes come back inline and are never listed. `adopt` and `salvage` cannot see
   them, and they cannot be tagged.
+- Character rotation and frame URLs live at a stable path under
+  `backblaze.pixellab.ai/file/pixellab-characters/...` but carry
+  `?t=<updated_at as epoch seconds>`, and the response is
+  `cache-control: public, max-age=31536000`. The path serves the current
+  bytes with any `t` (checked September 2026), but a cache between you and
+  the bucket may not, so `fetch --refresh` reads `GET /characters/{id}` for
+  the current stamp before comparing. Object URLs carry no stamp.
 
 ---
 

package/docs/GENERATORS.md

@@ -182,7 +182,10 @@ canvas lands in. Every direction of a base or state is one file
 (`<asset>-south.png`, ...); an animation's frames are `<asset>-frame-00.png`
 onwards, with the resting pose as frame 0 unless `keepFirstFrame` is off.
 `enforcePalette` snaps all of them. `pack --format godot` writes each base
-direction as a still and each animation as a looping set. See
+direction as a still and each animation as a looping set. The gallery
+labels a state or loop with its parent ("state of hero", "loop of
+hero.sit, east"), links parent and children in the record, and counts the
+family in the style header ("3 characters, 4 states, 6 loops"). See
 [Characters](./MANIFEST.md#characters).
 
 ## Style variants

package/docs/PIXELLAB.md

@@ -108,6 +108,13 @@ new bytes as this generation. A `pixflux` image is returned inline and keeps no
 account object, so it cannot be edited upstream; use `pixelkiln edit` to touch
 it up locally.
 
+A character edited in PixelLab's character editor comes back the same way.
+Its rotation and frame URLs carry the last edit time (`?t=`), so a refresh
+asks `GET /characters/{id}` for the current URLs before comparing bytes
+rather than trusting the ones the lockfile recorded, and records the new
+URLs. A refreshed base makes its states and animations stale, because their
+identity hashes the base's south file; `pixelkiln gen` regenerates them.
+
 PixelLab's official
 [MCP server](https://github.com/pixellab-code/pixellab-mcp) gives agents direct
 access to PixelLab generation tools. It complements PixelKiln: the MCP handles

package/package.json

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