pixelkiln 0.89.2 → 0.89.4

package/docs/CHARACTERS.md

@@ -209,6 +209,15 @@ higher, and it is sent to `/characters/animations`, the endpoint that
 documents it; every other mode keeps using `/animate-character`. Like a
 template loop it takes no `frames` and needs no prompt of its own.
 
+It needs a character PixelLab stored a 3D skeleton for. A `v3` base has
+one (a `skeleton-v3` loop on it billed 3 generations live). A `standard`
+base has none: PixelLab answers `POST /characters/animations` with a bare
+500 (`Failed to start any animation jobs`, nothing billed) and, asked,
+says to use `mode: "template"` for that character. `plan` and `validate`
+refuse the combination and name the engine. `pro` and `pro-flash` bases
+are not refused, but a `skeleton-v3` loop on one is unverified; try a
+single direction before a batch.
+
 ```jsonc
 "mira.walk": { "animation": { "of": "mira", "template": "walk", "mode": "skeleton-v3", "directions": ["south", "west", "north"] } }
 ```

package/docs/ENDPOINTS.md

@@ -406,8 +406,8 @@ normal-map` ([REVISIONS.md](./REVISIONS.md#normal-maps)).
 Called out separately because these are the most capable endpoints for level art
 and they are relevant to the disc-golf game. pixelkiln plans a top-down set
 at PixelLab's own quote (Pro 15 for tiles up to 32px, 25 at 64px; standard 4,
-the top of its quoted 1 to 4). Pro at 32px and the sidescroller are measured
-below; Pro at 64px and standard are not.
+the top of its quoted 1 to 4). Every kind is measured below: Pro billed
+exactly its quote at 32px and 64px, and standard billed 3, under the plan.
 
 `POST /tilesets` (top-down) and `/tilesets-sidescroller` are the current
 versions; `/create-tileset*` are the older aliases with identical schemas.
@@ -437,6 +437,32 @@ are the base tile ids, so set A's `upper` id sent as set B's
 `lower_base_tile_id` makes the two share that terrain. pixelkiln records them
 as `terrainIds` when it polls a set.
 
+### Pro at 64px, edge slope, and standard sets, measured
+
+A second round on the same showcase project billed 46 generations in all
+(balance 5055 to 5009), each set exactly as below:
+
+- `lava-floor`: Pro, 64px, `terrainTransitionSize: 0.5`,
+  `terrainRaggedness: 0.4`, `terrainBoundaryAmplitude: 0.15`,
+  `terrainBoundarySeed: 3`, prompt `1). glowing lava texture 2). dark dungeon
+  stone floor texture 3). crumbling dungeon brick wall`. Billed **exactly
+  25** and returned **25 tiles** covering **21** distinct corner
+  combinations, which confirms that Pro switches to the tall-wall layout at
+  0.5, not only at 1, and that four tiles are corner twins. The third
+  description became the brick wall dropping into the lava.
+- `swamp-marsh`: Pro, 32px, `terrainTransitionSize: 0.25`,
+  `terrainStepSlope: 1.5`, `terrainRaggedness: 0.8`. Billed **exactly 15**,
+  16 tiles, with a ragged bank between the water and the marsh grass.
+- `lake-grass` and `path-grass`: standard, 32px. Each billed **3**, under the
+  planned 4. `path-grass` used `connect: { upper: { of: "lake-grass",
+  terrain: "upper" } }`, sent `upper_base_tile_id`, and its recorded
+  `terrain_ids.upper` came back identical to `lake-grass`'s upper id. The
+  standard sets look flatter, with a hard edge, as PixelLab's tilesets
+  tutorial describes.
+
+pixelkiln keeps connected sets in one style, and a style fixes
+`terrainMode`, so a standard set cannot connect to a Pro set.
+
 ### Pro top-down and a connected pair, measured
 
 October 2026, through `pixelkiln gen` on the website's showcase project
@@ -755,6 +781,14 @@ one size; the higher cost tiers are still unconfirmed under
   carries `usage` once the job is gone, completed or not. `poll` reads the
   object/character for the result but would need this same job id, still
   polled separately today, to learn what it actually cost.
+- **A v3 character base once recorded `billed: {amount: 0, unit: "usd"}`**
+  against an estimate of 2 generations while the submit reported 1
+  generation consumed. Its job record had expired before the shape could be
+  read (jobs are deleted 8 hours after finishing, and the lock had dropped
+  the job id), so the real `usage` is unseen; `GET /characters/{id}` carries
+  none. `poll` now treats a dollar-denominated zero as not known, tries
+  `last_response.billing_usage`, and keeps `backgroundJobId` in the
+  character's lock metadata.
 - **`inpaint-v3` and `edit-images-v2` both confirmed live at their floor
   size**: a 32×32 masked inpaint and a separate 32×32 whole-image edit each
   billed exactly 20 generations, both matching a balance diff taken after.

package/docs/GENERATORS.md

@@ -12,7 +12,7 @@ account; [ENDPOINTS.md](./ENDPOINTS.md) contains the detailed experiments.
 | Exact fixed palette | `pixflux`, or `imagePro` for a larger or non-square canvas | 1 generation (`imagePro`: 10–25) | 1 inline image (`imagePro`: 1–64 by size) |
 | Candidate variety, richer rendering, future rotation/animation | `1dir` | 10–25 generations | 4–64 by size |
 | Ground tiles or connectable structural sets | `tiles` | 10–25 generations | variations or complete set |
-| Two-terrain Wang tileset for elevation (grass to water, floor to cliff), or a sidescroller platform set | `terrain` | Pro 15 at 32px and sidescroller 3 (measured); Pro 25 at 64px, standard plans at 4 (PixelLab's quotes) | 16 or 25 tiles |
+| Two-terrain Wang tileset for elevation (grass to water, floor to cliff), or a sidescroller platform set | `terrain` | Pro 15 at 32px and sidescroller 3, Pro 25 at 64px, standard 3 (all measured; standard plans at 4) | 16 or 25 tiles |
 | Platform tileset for a sidescroller (stone body, grass top) | `terrain`, `terrainOrientation: "sidescroller"` | 3 generations | 16 tiles |
 | A single elevation tile — a raised mesa, a cliff block | `isometricTile` | 1 generation | 1 |
 | Larger or non-square scene or background, up to 792 wide and 688 tall | `imagePro` | 10–25 generations by canvas | 1–64 by size |

package/docs/PIXELLAB.md

@@ -71,7 +71,7 @@ unapproved files. See [Manifest quality profiles](./MANIFEST.md#quality-profiles
 | `pixflux` | You need a closed palette or a full-bleed background | 1 generation |
 | `1dir` | You need references or several candidates for human review | 10 to 25 generations |
 | `tiles` | You need ground variations or a connected structural set | 10 to 25 generations |
-| `terrain` | You need a two-terrain Wang tileset (grass to water, floor to cliff), sets that share a terrain, or a sidescroller platform set | Pro 15 at 32px and sidescroller 3 (measured); Pro 25 at 64px and standard up to 4 (PixelLab's quote) |
+| `terrain` | You need a two-terrain Wang tileset (grass to water, floor to cliff), sets that share a terrain, or a sidescroller platform set | Pro 15 at 32px, 25 at 64px, standard 3, sidescroller 3 (all measured; standard plans at 4) |
 | `isometricTile` | You need one standalone isometric tile, 16 to 64px | 1 generation (measured once) |
 | `imagePro` | You need a larger or non-square scene, up to 792 wide and 688 tall, optionally held to the style's `palette` | 10 to 25 generations |
 | `imageProFlash` | You need a still on the Pro Flash model, optionally styled from one image, 16 to 256px | 5 to 9 generations (provisional quote) |
@@ -121,11 +121,12 @@ PixelLab 0.4.130 (October 2026) added four things. PixelKiln covers each:
   loop at 0.5 generations, and `pixelkiln normal-map` does it for a loose
   file. See [Controlled asset revisions](./REVISIONS.md#normal-maps).
 
-Each has been billed live and matched the plan: a Pro 32px set (15) and a
-second set connected to it (15), a sidescroller set (3), a 64×64 `imagePro`
+Each has been billed live and matched the plan: Pro sets at 32px (15) and
+64px (25, 25 tiles at transition 0.5), a second set connected to the first
+(15), standard sets (3 each), a sidescroller set (3), a 64×64 `imagePro`
 call with the Game Boy palette (10, every pixel one of its four colours), a
-lite described effect (1), and normal maps (0.5 each). The home page shows
-the results.
+lite described effect (1), and normal maps (0.5 each). The home page's latest
+updates section shows the results.
 
 ## Learn from PixelLab's tutorials
 

package/package.json

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

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

@@ -461,9 +461,12 @@ connecting different tilesets") are now mostly covered; see the closed
 - **Measured once:** a Pro 32px set billed exactly 15, and a second set
   connected to it through `lower_base_tile_id` billed exactly 15 and shared
   its sand (docs/ENDPOINTS.md). `terrainRoundness: 2` with
-  `terrainConnectDiagonals` gave clean 45° edges. **Unexercised live:**
-  Pro at 64px, standard sets, `upper_base_tile_id`, and the other shape
-  controls. Sidescroller tile counts at transition
+  `terrainConnectDiagonals` gave clean 45° edges. A second round confirmed
+  Pro at 64px (exactly 25, and 25 tiles at transition 0.5), edge slope and
+  an uneven boundary (15 at 32px), standard sets (3 each, under the planned
+  4), and connecting through `upper_base_tile_id`. **Still open:** a
+  standard set cannot connect to a Pro set, because connected sets share a
+  style and a style fixes the mode. Sidescroller tile counts at transition
   sizes other than 0.25 are assumed to be 16. The one sidescroller call
   returned `metadata.transition_size: 0.0` although 0.25 was sent.
 - **Prompting advice** lives in the skill reference: end each terrain on

package/skills/pixelkiln/references/pixellab.md

@@ -24,7 +24,7 @@ providers, or before any PixelLab account operation.
 | `pixflux` | Closed palettes or full-bleed backgrounds up to 400×400 | 1 generation |
 | `1dir` | Reference-guided work or several candidates | 10–25 generations |
 | `tiles` | Ground variations or connected structures | 10–25 generations |
-| `terrain` | A two-terrain Wang tileset for elevation (grass-to-water, floor-to-cliff), or a sidescroller platform set | Sidescroller **3**, measured. Pro **15** at 32px, measured (a connected second set also billed 15). Pro 25 at 64px and standard 4 (quoted 1–4) are PixelLab's quotes |
+| `terrain` | A two-terrain Wang tileset for elevation (grass-to-water, floor-to-cliff), or a sidescroller platform set | Sidescroller **3**, measured. Pro **15** at 32px, measured (a connected second set also billed 15). Pro **25** at 64px and standard **3** measured too; standard plans at 4, the top of PixelLab's quoted 1–4 |
 | `imagePro` | A larger or non-square background/scene, or real style transfer; takes the style `palette` as a hard constraint | **10–25 generations** by canvas (64px billed 10; a flat 40 before October 2026) |
 | `character` | A character in 4 or 8 directions, its poses (`state`), its loops (`animation`), bust `portrait`s, and `outfit` transfers onto a loop | 1 per standard base, 6 per pro-flash base at 64px (1 from a `reference`), 20–40 per pose or portrait, 1 per template loop per direction (2–4 as `skeleton-v3`), 20 per outfit (measured once) |
 | `objectPro` | A prop, creature, or vehicle that needs rotations, states, or loops but has no character rig | 6 per base at 64px (1 from a `reference`), **unmeasured**; assumed to match `character` pro-flash |
@@ -146,7 +146,8 @@ the next wave), PixelLab draws the shared terrain from its base tile, and
 regenerating the other set makes this one stale. Sharing a terrain makes it
 available, not blendable: two terrains with no set of their own between
 them still meet with a hard (in PixelLab's map tool, black) edge, so plan a
-set for every pair that touches.
+set for every pair that touches. Connected sets share one style, and a style
+fixes `terrainMode`, so a standard set cannot connect to a Pro one.
 
 **Sidescroller sets.** `terrainOrientation: "sidescroller"` switches to
 `/create-tileset-sidescroller`: a platform seen from the side. The prompt is
@@ -387,7 +388,11 @@ character with PixelLab's skeleton video model instead of redrawing each
 frame: the steadiest template loop, 2 to 4 generations and 3 to 5 minutes
 per direction (plan budgets 4), beta, Tier 1 plans and up. Prefer it over a
 plain template loop when identity drift matters and the account qualifies;
-plain `template` stays the 1-generation option.
+plain `template` stays the 1-generation option. It needs a base with a
+stored 3D skeleton: a `v3` base has one (measured, 3 generations); a
+`standard` base has none, so PixelLab answers a bare 500 and pixelkiln
+refuses the loop at `plan`/`validate`, pointing at `mode: "template"`. `pro`
+and `pro-flash` bases are not refused but are unverified.
 
 A named `template` loop (`walk`, `breathing-idle`, and similar) is trained
 mostly on characters with empty hands, and reliably struggles once a