pixelkiln 0.85.0 → 0.86.0

package/docs/MANIFEST.md

@@ -472,7 +472,8 @@ their own page: [Characters](./CHARACTERS.md) and
 | Revision field | Type | Meaning |
 |---|---|---|
 | `mode` | enum, required | `image-to-image`, `inpaint`, `outpaint`, `reduce-colors`, `correct-pixelart`, `remove-background`, `animate`, `animate-pixminimax`, `animate-skeleton`, `interpolate`, or `edit-animation`. The selected provider must opt into the mode. |
-| `from` | asset id, required | Parent asset in the same style. Self-references, unknown ids, and cycles are rejected. A parent written as a set (a character's directions, an animation's frames) is read as every member: `reduce-colors`, `correct-pixelart`, and `edit-animation` take the whole set in one call; the other modes refuse it. See [Revising a whole set at once](./REVISIONS.md#revising-a-whole-set-at-once). |
+| `from` | asset id, required | Parent asset, in this asset's style unless `fromStyle` names another. Self-references, unknown ids, and cycles are rejected. A parent written as a set (a character's directions, an animation's frames) is read as every member: `reduce-colors`, `correct-pixelart`, and `edit-animation` take the whole set in one call; the other modes refuse it. See [Revising a whole set at once](./REVISIONS.md#revising-a-whole-set-at-once). |
+| `fromStyle` | style id | The style the parent lives in, when it is not this asset's own. The parent must be an asset in that style, and styles may depend on one another but not in a cycle. See [Across styles](./REVISIONS.md#across-styles). |
 | `mask` | string | Manifest-relative PNG required for `inpaint`; rejected for the other modes. Its dimensions must match an available source. |
 | `strength` | number 0–1 | Workflow edit/denoise strength (`image-to-image`, `correct-pixelart`); rejected for `reduce-colors`, `remove-background`, `animate`, `animate-pixminimax`, `interpolate`, and `edit-animation`. Interpretation is provider- and model-specific. |
 | `numColors` | integer 2–256 | `reduce-colors` only. Target palette size; mutually exclusive with `paletteImage`. |

package/docs/REVISIONS.md

@@ -43,15 +43,10 @@ Keep the parent as its own asset and point the child at its stable asset id:
 }
 ```
 
-`from` names another asset in the same style. A source and its revision cannot
-be the same asset, and revision chains cannot contain a cycle. `source` and
-`revision` are mutually exclusive on one asset.
-
-Revision edges do not cross styles or providers in this version. To use output
-from another provider, commit or retain that PNG and declare it as a separate
-`source` asset in the ComfyUI revision style. The child still records the exact
-source hash, but the cross-provider handoff is a file boundary rather than one
-automatic lock dependency.
+`from` names another asset. It lives in the child's own style unless
+`fromStyle` names another (see [Across styles](#across-styles)). A source and its
+revision cannot be the same asset, and revision chains cannot contain a cycle.
+`source` and `revision` are mutually exclusive on one asset.
 
 Start with a low strength. Values around `0.2`–`0.4` give the workflow room to
 change texture and lighting while retaining more of the source. Higher values
@@ -104,6 +99,41 @@ poses" opens the same editor on its keypoints file. Saving rewrites the file
 only if it still holds what the page loaded (an edit made elsewhere since is
 refused, not overwritten), and the animation is stale until generated again.
 
+### Across styles
+
+A style has one provider and one model, so a chain that generates with one model
+and cleans up with another spans styles. Name the parent's style:
+
+```jsonc
+{
+  "styles": {
+    "gen": { "generator": "map", "outDir": "art/gen", "providerOptions": { "scenario": { "modelId": "model_bfl-flux-2-klein-9b", "maxComputeUnits": 1 } } },
+    "pixelate": { "generator": "map", "outDir": "art/pixelate", "providerOptions": { "scenario": { "modelId": "model_sc-pixelate", "maxComputeUnits": 5, "referenceParameter": "image", "referenceArray": false } } }
+  },
+  "assets": {
+    "knight": { "prompt": "a knight, isolated on white", "styles": ["gen"] },
+    "knight-px": {
+      "prompt": "pixelate",
+      "styles": ["pixelate"],
+      "revision": { "mode": "image-to-image", "from": "knight", "fromStyle": "gen" }
+    }
+  }
+}
+```
+
+The child starts from the parent's output file, however that style produced it
+(any provider, or a placed `source`), and the dependency gate is unchanged: the
+child is `blocked` until the parent is downloaded, current, and untouched, and
+`gen` takes the whole chain to the end in one run, one wave per link. The parent
+must be an asset in the named style. Styles may depend on one another but not
+in a cycle, and `fromStyle` naming the asset's own style is the ordinary case.
+`--style` still selects which specs a run returns; a parent style it excludes is
+resolved, not generated.
+
+A `quality` profile gates the style it is on. Put it on the last style of a
+chain, whose parents are in other styles, and only that style's output is gated.
+A profile on a style that also holds the raw parent would block the child.
+
 ## Inpainting
 
 An inpaint revision also declares a manifest-relative mask:

package/docs/SCENARIO.md

@@ -186,7 +186,13 @@ quoted and billed identically; see the
 [tool-model smoke](../benchmarks/provider-scenario-tools/README.md)). Pixel
 Snapper returned an 83×83, exactly-16-colour native-grid version of a 512×512
 image, a different size than the manifest's canvas, and Birefnet's cutout kept
-its subject at alpha 254 rather than 255. The other tools were only quoted. They overlap PixelKiln's own offline work: `pixelkiln refine` snaps
+its subject at alpha 254 rather than 255. Pixelate (5 CU) was run too and returned a 23-colour, crisp pixel version at the
+source's size; of the upscalers, Topaz smoothed the art, Upscale V3 repainted it
+as a photoreal castle, and Recraft Crisp returned WebP, which the adapter refuses,
+so none of them suits pixel art. Pixelate's output also passed `pixelkiln refine`'s
+high-confidence grid gate as a 102×102, 23-colour asset, where the raw image
+(low confidence) and Pixel Snapper's output (medium) did not: GPT Image 2,
+then Pixelate, then free refinement made one gate-passing asset for 16 CU. They overlap PixelKiln's own offline work: `pixelkiln refine` snaps
 the grid and palette for free, and PixelLab's `remove-background` revision costs
 one generation. Reach for these when the art is already on Scenario.
 
@@ -223,6 +229,29 @@ upgrading should be one `model_retrodiffusion-plus` still at 64×64 with the
 default style: quote, billed amount, dimensions, and whether it comes back as
 PNG.
 
+### Chaining models and tools
+
+The [pipeline run](../benchmarks/provider-scenario-pipeline/README.md)
+generated a character, pixelated it to a palette, cut out its background, and
+refined it, for 8 CU on the cheapest path and 18 CU with GPT Image 2, ending in
+a 64×64 transparent sprite that passed the `refine` gate. Three rules came out
+of it:
+
+- A revision's parent must be in the same style, and a style has one model. To
+  chain steps, restate the previous output in the next style as a placed
+  `source`: `"source": "outputs/gen-klein/knight.png"`. Run each step with
+  `gen --style <id>`; nothing orders them yet.
+- A `quality` profile gates every asset in its style, parents included, so a raw
+  parent blocks its own child. Put `quality` only on a final style whose asset is
+  the last output placed as a `source`, then run `pixelkiln refine --style`.
+- Pass the same palette to the tool (Pixelate's `colorPalette`) and to
+  `quality.palette`. The output then stays inside it. Pixelate's
+  `pixelGridSize` also set the detected native grid closely (48, 64 and 128
+  asked, 46, 64 and 128 found).
+
+A palette that is too small for the art costs fidelity (a bright blue cape
+became navy under a 32-colour palette), so passing the gate is not approval.
+
 ## Plan before spending
 
 Scenario prices depend on model, size, steps, and output count, so PixelKiln

package/package.json

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

package/schema/manifest.schema.json

@@ -1022,6 +1022,10 @@
                     "type": "string",
                     "minLength": 1
                   },
+                  "fromStyle": {
+                    "type": "string",
+                    "minLength": 1
+                  },
                   "mask": {
                     "type": "string",
                     "minLength": 1

package/skills/pixelkiln/references/revisions.md

@@ -2,8 +2,10 @@
 
 Read this reference when an asset declares `revision`.
 
-- Treat the parent and child as separate assets. `revision.from` must name a
-  parent in the same style.
+- Treat the parent and child as separate assets. `revision.from` names the
+  parent, in the child's own style unless `revision.fromStyle` names another, so
+  a chain can generate with one provider and refine with another. A `quality`
+  profile gates its own style; put it on the last style of a chain.
 - Run `pixelkiln plan --only <child>` first. If it reports `blocked`, do not try
   to submit the child or work around the gate.
 - A generated parent must be current and downloaded. When the parent has a