* feat!: collapse pipeline — Resolver emits a flat prompt, drop categories (v1.1) BREAKING CHANGE: the Category Splitter and Prompt Builder stages and nodes are removed. The Resolver is now the translator from Scene JSON to prompt: it resolves concepts to Knowledge Base tags and joins them into one flat comma-separated prompt string, in resolution order (which naturally leads with character concepts). Resolver node outputs are now (prompt, warnings, errors, json) — the json being the traceable resolved tags so a translation problem is inspectable. Node count drops from 8 to 6. The CategoryMap/PromptOutput models and their schemas are removed; the `category` field remains on entries and resolved tags for traceability only. Debug Viewer simplified to scene/warnings/errors. Goldens, example scenes/workflow, integration/performance/repo-layout/release tests, benchmark script, and the docs (README + wiki) are updated to the flat prompt. Version bumped to 1.1.0. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * build: drop removed splitter/builder packages from pyproject Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> --------- Co-authored-by: kunail0804 <kunail0804@gmail.com> Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
Examples
Ready-to-use examples for Scene Compiler.
Workflow
workflows/scene_compiler_pipeline.json
is a ComfyUI workflow wiring the full pipeline:
Configuration ─┬─▶ Scene Validator ─▶ Resolver ─▶ Category Splitter ─▶ Prompt Builder
├──────────────────────▶ (config) (config) ◀┘
Knowledge Base Loader ─────────────────▶ Resolver (knowledge_base)
Scene Analyzer ─▶ Scene Validator (scene)
Load it in ComfyUI (Load → pick the file). The Scene Analyzer requires a local Ollama instance; the rest of the pipeline runs offline.
Scene JSON examples
Each scenes/*.scene.json is a Scene JSON document (the Analyzer's output form),
and each matching scenes/*.prompts.json is the exact prompt output it compiles
to with the shipped Knowledge Base and default configuration:
| Scene | Highlights |
|---|---|
single_character |
one character, appearance, clothing, environment, camera, lighting |
couple_interaction |
two characters, an interaction, and an expansion (school_uniform → blazer, pleated_skirt) |
The *.prompts.json outputs are verified by tests/test_examples.py. To skip the
Analyzer and compile a Scene JSON directly, feed it through the Validator →
Resolver → Category Splitter → Prompt Builder nodes (or the compiler API).
Note: the workflow JSON is provided as a starting point; verify it loads in your ComfyUI and re-save if ComfyUI adjusts the layout.