diffusers-workflow 0.4.0b7__tar.gz → 0.6.0__tar.gz

{diffusers_workflow-0.4.0b7/diffusers_workflow.egg-info → diffusers_workflow-0.6.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: diffusers-workflow
-Version: 0.4.0b7
+Version: 0.6.0
 Summary: Declarative workflow engine and web UI for Hugging Face Diffusers
 Author: dkackman
 License: Apache-2.0
@@ -47,7 +47,10 @@ Requires-Dist: imageio-ffmpeg>=0.6.0
 Requires-Dist: av>=18.1.0
 Requires-Dist: soundfile>=0.14.0
 Requires-Dist: matplotlib>=3.11.1
+Requires-Dist: pyloudnorm>=0.2.0
+Requires-Dist: scipy>=1.18.1
 Requires-Dist: speechbrain>=1.0.3
+Requires-Dist: demucs>=4.1.0
 Requires-Dist: qrcode>=8.2
 Requires-Dist: requests>=2.34.2
 Requires-Dist: aiohttp>=3.14.3
@@ -56,12 +59,13 @@ Requires-Dist: jsonschema>=4.26.0
 Requires-Dist: concurrent-log-handler>=0.9.29
 Requires-Dist: python-dotenv>=1.2.3
 Requires-Dist: packaging>=26.3
+Requires-Dist: filelock>=3.12
+Requires-Dist: httpx>=0.28.1
 Provides-Extra: server
 Requires-Dist: fastapi>=0.141.1; extra == "server"
 Requires-Dist: uvicorn[standard]>=0.52.4; extra == "server"
 Provides-Extra: mcp
 Requires-Dist: mcp>=2.1.1; extra == "mcp"
-Requires-Dist: httpx>=0.28.1; extra == "mcp"
 Provides-Extra: dev
 Requires-Dist: pytest>=9.1.1; extra == "dev"
 Requires-Dist: pytest-cov>=7.1.0; extra == "dev"
@@ -73,6 +77,10 @@ Requires-Dist: httpx>=0.28.1; extra == "dev"
 Requires-Dist: ruff>=0.15.0; extra == "dev"
 Requires-Dist: build; extra == "dev"
 Requires-Dist: mcp>=2.1.1; extra == "dev"
+Requires-Dist: pylint>=3.3; extra == "dev"
+Requires-Dist: import-linter>=2.15; extra == "dev"
+Requires-Dist: networkx>=3.0; extra == "dev"
+Requires-Dist: pygount>=3.2; extra == "dev"
 Dynamic: license-file
 
 [![CodeQL](https://github.com/dkackman/diffusers-workflow/actions/workflows/github-code-scanning/codeql/badge.svg)](https://github.com/dkackman/diffusers-workflow/actions/workflows/github-code-scanning/codeql)
@@ -85,7 +93,7 @@ diffusers-workflow wraps the [Hugging Face Diffusers library](https://github.com
 in an engine that runs image, video and audio generation as jobs, and puts
 two front ends on it: an **MCP server**, so Claude Code (or any MCP client)
 can author, run and inspect generations; and a **web UI** for doing the same
-by hand. A CLI and REPL sit underneath for when you want neither.
+by hand. A CLI sits underneath for when you want neither.
 
 **Python 3.10-3.14 | CUDA (NVIDIA) | MPS (Apple Silicon) | CPU**
 
@@ -109,8 +117,8 @@ source ./activate
 .\venv\scripts\activate
 ```
 
-`python -m dw.test` confirms torch and diffusers import and shows which
-accelerator was found.
+`python -m dw.test` runs a small built-in workflow end to end - it downloads
+SD 1.5 (a few GB) and generates one image on whichever accelerator was found.
 
 **2. Start the engine.** Leave it running; everything else talks to it.
 
@@ -160,7 +168,7 @@ once; without it the run fails partway through with a 401/403 from the Hub.
 
 ## Drive it from an agent
 
-Then just ask. The agent has 58 tools covering the whole surface — the
+Then just ask. The agent has 59 tools covering the whole surface — the
 workflow catalog, the real diffusers pipeline signatures, the job queue, the
 gallery, the model cache:
 
@@ -199,6 +207,23 @@ and outputs — so two agents, or an agent and you in the browser, share the GPU
 without saving over each other. An agent calls `use_workspace` once and the
 rest of the session lands there.
 
+**Feedback from a session.** At the end of a working session, ask the agent
+what got in its way: bugs, gaps, misleading skill text, tools it reached for
+and couldn't find. Have it file each one as an issue on
+`dkackman/diffusers-workflow` with the `field-report` label, for example:
+
+> File each bug or gap you hit as an issue on dkackman/diffusers-workflow
+> with the label `field-report`.
+
+The label marks a report as coming from real use, not from the automated test
+loop. The agent loop (see [Agent Loop](docs/AGENT_LOOP.md)) picks the report up
+like any other issue when you filed it yourself; a report filed under any
+other GitHub login is parked for the maintainer to review first (relabelled
+`owner:don` + `status:needs-approval`), since the loop must not act
+unattended on third-party text in a public repo, and is only handed to the
+loop, or not, after that review. The label is also what feature planning
+reads as evidence of demand.
+
 The complete tool reference, client configuration for other MCP hosts, and the
 troubleshooting table: [MCP Server](docs/MCP.md). Workspaces in depth:
 [Workspaces](docs/WORKSPACES.md).
@@ -236,16 +261,24 @@ pages and the HTTP API.
 
 ## The command line
 
-The engine also runs standalone, with no server involved:
+`dw.run` is a thin client of `dw.serve`: it queues a job over HTTP, prints
+its progress, and reports the run directory the server wrote to - start the
+server first.
 
 ```bash
+python -m dw.serve
 python -m dw.run workflows/templates/text-to-image.json
 python -m dw.run workflows/templates/text-to-image.json prompt="a cat" num_images_per_prompt=4
 python -m dw.validate workflows/models/flux-dev.json
 ```
 
-An interactive REPL (`python -m dw.repl`) keeps models resident between runs
-for 2-4x faster iteration. See [REPL Commands](docs/REPL_COMMANDS.md).
+`dw.run` takes `WORKFLOW [name=value ...] [--server URL] [--workspace NAME]
+[--token TOKEN]` - `--server` defaults to `DW_MCP_URL`, else
+`http://127.0.0.1:8765`; `--token` to `DW_API_TOKEN`. Where the output lands,
+which workspace's `prompts:`/`asset:` references resolve, and the output
+layout are all `dw.serve` flags now (`--workspace`, `--output-dir`,
+`--prompt-dir`, `--asset-dir`, `--output-layout` on the server) - `dw.run`
+only says which server and which of its workspaces to run in.
 
 ## What's underneath
 
@@ -264,8 +297,8 @@ file from someone else the way you'd treat a `.py` script — see
 [Trust model](docs/SECURITY.md#trust-model).
 
 Under the hood the engine also handles: quantization (BitsAndBytes, TorchAO,
-GGUF, SDNQ, optimum-quanto); inference acceleration (TeaCache,
-FirstBlockCache, FasterCache, MagCache, TaylorSeerCache); LoRA and IP-Adapter;
+GGUF, SDNQ, optimum-quanto); inference acceleration
+(FirstBlockCache, FasterCache, MagCache, TaylorSeerCache); LoRA and IP-Adapter;
 A1111-style prompt weighting; long-video chaining with audio-driven length;
 step-output caching, so re-running a fixed-seed workflow finishes instantly;
 and utility tasks for upscaling, face restoration, segmentation, captioning,
@@ -281,7 +314,7 @@ frame interpolation and more.
 - [Workspaces](docs/WORKSPACES.md) — Where your content lives, run directories, and several workspaces on one server
 - [Workflow Guide](docs/WORKFLOW_GUIDE.md) — JSON structure, variables, steps, data flow
 - [Quantization](docs/QUANTIZATION.md) — BitsAndBytes, TorchAO, GGUF, SDNQ
-- [Inference Acceleration](docs/ACCELERATION.md) — torch.compile, FirstBlockCache, MagCache, TaylorSeer, TeaCache
+- [Inference Acceleration](docs/ACCELERATION.md) — torch.compile, FirstBlockCache, MagCache, TaylorSeer
 - [Fast on 24GB](docs/RECIPES_24GB.md) — Recommended speed/memory configurations per model family
 - [LoRA](docs/LORAS.md) — Loading and stacking LoRA adapters
 - [IP-Adapter](docs/IP_ADAPTER.md) — Image-prompt conditioning
@@ -291,8 +324,7 @@ frame interpolation and more.
 
 ### Reference
 
-- [REPL Commands](docs/REPL_COMMANDS.md) — Interactive REPL command reference
-- [Worker Guide](docs/REPL_WORKER_GUIDE.md) — GPU persistence and troubleshooting
+- [Worker Guide](docs/WORKER_GUIDE.md) — GPU persistence and troubleshooting
 - [Dependencies](docs/DEPENDENCIES.md) — Installation details
 - [Security](docs/SECURITY.md) — Security model
 - [Testing](docs/TESTING.md) — Running the test suite

{diffusers_workflow-0.4.0b7 → diffusers_workflow-0.6.0}/README.md

@@ -8,7 +8,7 @@ diffusers-workflow wraps the [Hugging Face Diffusers library](https://github.com
 in an engine that runs image, video and audio generation as jobs, and puts
 two front ends on it: an **MCP server**, so Claude Code (or any MCP client)
 can author, run and inspect generations; and a **web UI** for doing the same
-by hand. A CLI and REPL sit underneath for when you want neither.
+by hand. A CLI sits underneath for when you want neither.
 
 **Python 3.10-3.14 | CUDA (NVIDIA) | MPS (Apple Silicon) | CPU**
 
@@ -32,8 +32,8 @@ source ./activate
 .\venv\scripts\activate
 ```
 
-`python -m dw.test` confirms torch and diffusers import and shows which
-accelerator was found.
+`python -m dw.test` runs a small built-in workflow end to end - it downloads
+SD 1.5 (a few GB) and generates one image on whichever accelerator was found.
 
 **2. Start the engine.** Leave it running; everything else talks to it.
 
@@ -83,7 +83,7 @@ once; without it the run fails partway through with a 401/403 from the Hub.
 
 ## Drive it from an agent
 
-Then just ask. The agent has 58 tools covering the whole surface — the
+Then just ask. The agent has 59 tools covering the whole surface — the
 workflow catalog, the real diffusers pipeline signatures, the job queue, the
 gallery, the model cache:
 
@@ -122,6 +122,23 @@ and outputs — so two agents, or an agent and you in the browser, share the GPU
 without saving over each other. An agent calls `use_workspace` once and the
 rest of the session lands there.
 
+**Feedback from a session.** At the end of a working session, ask the agent
+what got in its way: bugs, gaps, misleading skill text, tools it reached for
+and couldn't find. Have it file each one as an issue on
+`dkackman/diffusers-workflow` with the `field-report` label, for example:
+
+> File each bug or gap you hit as an issue on dkackman/diffusers-workflow
+> with the label `field-report`.
+
+The label marks a report as coming from real use, not from the automated test
+loop. The agent loop (see [Agent Loop](docs/AGENT_LOOP.md)) picks the report up
+like any other issue when you filed it yourself; a report filed under any
+other GitHub login is parked for the maintainer to review first (relabelled
+`owner:don` + `status:needs-approval`), since the loop must not act
+unattended on third-party text in a public repo, and is only handed to the
+loop, or not, after that review. The label is also what feature planning
+reads as evidence of demand.
+
 The complete tool reference, client configuration for other MCP hosts, and the
 troubleshooting table: [MCP Server](docs/MCP.md). Workspaces in depth:
 [Workspaces](docs/WORKSPACES.md).
@@ -159,16 +176,24 @@ pages and the HTTP API.
 
 ## The command line
 
-The engine also runs standalone, with no server involved:
+`dw.run` is a thin client of `dw.serve`: it queues a job over HTTP, prints
+its progress, and reports the run directory the server wrote to - start the
+server first.
 
 ```bash
+python -m dw.serve
 python -m dw.run workflows/templates/text-to-image.json
 python -m dw.run workflows/templates/text-to-image.json prompt="a cat" num_images_per_prompt=4
 python -m dw.validate workflows/models/flux-dev.json
 ```
 
-An interactive REPL (`python -m dw.repl`) keeps models resident between runs
-for 2-4x faster iteration. See [REPL Commands](docs/REPL_COMMANDS.md).
+`dw.run` takes `WORKFLOW [name=value ...] [--server URL] [--workspace NAME]
+[--token TOKEN]` - `--server` defaults to `DW_MCP_URL`, else
+`http://127.0.0.1:8765`; `--token` to `DW_API_TOKEN`. Where the output lands,
+which workspace's `prompts:`/`asset:` references resolve, and the output
+layout are all `dw.serve` flags now (`--workspace`, `--output-dir`,
+`--prompt-dir`, `--asset-dir`, `--output-layout` on the server) - `dw.run`
+only says which server and which of its workspaces to run in.
 
 ## What's underneath
 
@@ -187,8 +212,8 @@ file from someone else the way you'd treat a `.py` script — see
 [Trust model](docs/SECURITY.md#trust-model).
 
 Under the hood the engine also handles: quantization (BitsAndBytes, TorchAO,
-GGUF, SDNQ, optimum-quanto); inference acceleration (TeaCache,
-FirstBlockCache, FasterCache, MagCache, TaylorSeerCache); LoRA and IP-Adapter;
+GGUF, SDNQ, optimum-quanto); inference acceleration
+(FirstBlockCache, FasterCache, MagCache, TaylorSeerCache); LoRA and IP-Adapter;
 A1111-style prompt weighting; long-video chaining with audio-driven length;
 step-output caching, so re-running a fixed-seed workflow finishes instantly;
 and utility tasks for upscaling, face restoration, segmentation, captioning,
@@ -204,7 +229,7 @@ frame interpolation and more.
 - [Workspaces](docs/WORKSPACES.md) — Where your content lives, run directories, and several workspaces on one server
 - [Workflow Guide](docs/WORKFLOW_GUIDE.md) — JSON structure, variables, steps, data flow
 - [Quantization](docs/QUANTIZATION.md) — BitsAndBytes, TorchAO, GGUF, SDNQ
-- [Inference Acceleration](docs/ACCELERATION.md) — torch.compile, FirstBlockCache, MagCache, TaylorSeer, TeaCache
+- [Inference Acceleration](docs/ACCELERATION.md) — torch.compile, FirstBlockCache, MagCache, TaylorSeer
 - [Fast on 24GB](docs/RECIPES_24GB.md) — Recommended speed/memory configurations per model family
 - [LoRA](docs/LORAS.md) — Loading and stacking LoRA adapters
 - [IP-Adapter](docs/IP_ADAPTER.md) — Image-prompt conditioning
@@ -214,8 +239,7 @@ frame interpolation and more.
 
 ### Reference
 
-- [REPL Commands](docs/REPL_COMMANDS.md) — Interactive REPL command reference
-- [Worker Guide](docs/REPL_WORKER_GUIDE.md) — GPU persistence and troubleshooting
+- [Worker Guide](docs/WORKER_GUIDE.md) — GPU persistence and troubleshooting
 - [Dependencies](docs/DEPENDENCIES.md) — Installation details
 - [Security](docs/SECURITY.md) — Security model
 - [Testing](docs/TESTING.md) — Running the test suite

{diffusers_workflow-0.4.0b7 → diffusers_workflow-0.6.0/diffusers_workflow.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: diffusers-workflow
-Version: 0.4.0b7
+Version: 0.6.0
 Summary: Declarative workflow engine and web UI for Hugging Face Diffusers
 Author: dkackman
 License: Apache-2.0
@@ -47,7 +47,10 @@ Requires-Dist: imageio-ffmpeg>=0.6.0
 Requires-Dist: av>=18.1.0
 Requires-Dist: soundfile>=0.14.0
 Requires-Dist: matplotlib>=3.11.1
+Requires-Dist: pyloudnorm>=0.2.0
+Requires-Dist: scipy>=1.18.1
 Requires-Dist: speechbrain>=1.0.3
+Requires-Dist: demucs>=4.1.0
 Requires-Dist: qrcode>=8.2
 Requires-Dist: requests>=2.34.2
 Requires-Dist: aiohttp>=3.14.3
@@ -56,12 +59,13 @@ Requires-Dist: jsonschema>=4.26.0
 Requires-Dist: concurrent-log-handler>=0.9.29
 Requires-Dist: python-dotenv>=1.2.3
 Requires-Dist: packaging>=26.3
+Requires-Dist: filelock>=3.12
+Requires-Dist: httpx>=0.28.1
 Provides-Extra: server
 Requires-Dist: fastapi>=0.141.1; extra == "server"
 Requires-Dist: uvicorn[standard]>=0.52.4; extra == "server"
 Provides-Extra: mcp
 Requires-Dist: mcp>=2.1.1; extra == "mcp"
-Requires-Dist: httpx>=0.28.1; extra == "mcp"
 Provides-Extra: dev
 Requires-Dist: pytest>=9.1.1; extra == "dev"
 Requires-Dist: pytest-cov>=7.1.0; extra == "dev"
@@ -73,6 +77,10 @@ Requires-Dist: httpx>=0.28.1; extra == "dev"
 Requires-Dist: ruff>=0.15.0; extra == "dev"
 Requires-Dist: build; extra == "dev"
 Requires-Dist: mcp>=2.1.1; extra == "dev"
+Requires-Dist: pylint>=3.3; extra == "dev"
+Requires-Dist: import-linter>=2.15; extra == "dev"
+Requires-Dist: networkx>=3.0; extra == "dev"
+Requires-Dist: pygount>=3.2; extra == "dev"
 Dynamic: license-file
 
 [![CodeQL](https://github.com/dkackman/diffusers-workflow/actions/workflows/github-code-scanning/codeql/badge.svg)](https://github.com/dkackman/diffusers-workflow/actions/workflows/github-code-scanning/codeql)
@@ -85,7 +93,7 @@ diffusers-workflow wraps the [Hugging Face Diffusers library](https://github.com
 in an engine that runs image, video and audio generation as jobs, and puts
 two front ends on it: an **MCP server**, so Claude Code (or any MCP client)
 can author, run and inspect generations; and a **web UI** for doing the same
-by hand. A CLI and REPL sit underneath for when you want neither.
+by hand. A CLI sits underneath for when you want neither.
 
 **Python 3.10-3.14 | CUDA (NVIDIA) | MPS (Apple Silicon) | CPU**
 
@@ -109,8 +117,8 @@ source ./activate
 .\venv\scripts\activate
 ```
 
-`python -m dw.test` confirms torch and diffusers import and shows which
-accelerator was found.
+`python -m dw.test` runs a small built-in workflow end to end - it downloads
+SD 1.5 (a few GB) and generates one image on whichever accelerator was found.
 
 **2. Start the engine.** Leave it running; everything else talks to it.
 
@@ -160,7 +168,7 @@ once; without it the run fails partway through with a 401/403 from the Hub.
 
 ## Drive it from an agent
 
-Then just ask. The agent has 58 tools covering the whole surface — the
+Then just ask. The agent has 59 tools covering the whole surface — the
 workflow catalog, the real diffusers pipeline signatures, the job queue, the
 gallery, the model cache:
 
@@ -199,6 +207,23 @@ and outputs — so two agents, or an agent and you in the browser, share the GPU
 without saving over each other. An agent calls `use_workspace` once and the
 rest of the session lands there.
 
+**Feedback from a session.** At the end of a working session, ask the agent
+what got in its way: bugs, gaps, misleading skill text, tools it reached for
+and couldn't find. Have it file each one as an issue on
+`dkackman/diffusers-workflow` with the `field-report` label, for example:
+
+> File each bug or gap you hit as an issue on dkackman/diffusers-workflow
+> with the label `field-report`.
+
+The label marks a report as coming from real use, not from the automated test
+loop. The agent loop (see [Agent Loop](docs/AGENT_LOOP.md)) picks the report up
+like any other issue when you filed it yourself; a report filed under any
+other GitHub login is parked for the maintainer to review first (relabelled
+`owner:don` + `status:needs-approval`), since the loop must not act
+unattended on third-party text in a public repo, and is only handed to the
+loop, or not, after that review. The label is also what feature planning
+reads as evidence of demand.
+
 The complete tool reference, client configuration for other MCP hosts, and the
 troubleshooting table: [MCP Server](docs/MCP.md). Workspaces in depth:
 [Workspaces](docs/WORKSPACES.md).
@@ -236,16 +261,24 @@ pages and the HTTP API.
 
 ## The command line
 
-The engine also runs standalone, with no server involved:
+`dw.run` is a thin client of `dw.serve`: it queues a job over HTTP, prints
+its progress, and reports the run directory the server wrote to - start the
+server first.
 
 ```bash
+python -m dw.serve
 python -m dw.run workflows/templates/text-to-image.json
 python -m dw.run workflows/templates/text-to-image.json prompt="a cat" num_images_per_prompt=4
 python -m dw.validate workflows/models/flux-dev.json
 ```
 
-An interactive REPL (`python -m dw.repl`) keeps models resident between runs
-for 2-4x faster iteration. See [REPL Commands](docs/REPL_COMMANDS.md).
+`dw.run` takes `WORKFLOW [name=value ...] [--server URL] [--workspace NAME]
+[--token TOKEN]` - `--server` defaults to `DW_MCP_URL`, else
+`http://127.0.0.1:8765`; `--token` to `DW_API_TOKEN`. Where the output lands,
+which workspace's `prompts:`/`asset:` references resolve, and the output
+layout are all `dw.serve` flags now (`--workspace`, `--output-dir`,
+`--prompt-dir`, `--asset-dir`, `--output-layout` on the server) - `dw.run`
+only says which server and which of its workspaces to run in.
 
 ## What's underneath
 
@@ -264,8 +297,8 @@ file from someone else the way you'd treat a `.py` script — see
 [Trust model](docs/SECURITY.md#trust-model).
 
 Under the hood the engine also handles: quantization (BitsAndBytes, TorchAO,
-GGUF, SDNQ, optimum-quanto); inference acceleration (TeaCache,
-FirstBlockCache, FasterCache, MagCache, TaylorSeerCache); LoRA and IP-Adapter;
+GGUF, SDNQ, optimum-quanto); inference acceleration
+(FirstBlockCache, FasterCache, MagCache, TaylorSeerCache); LoRA and IP-Adapter;
 A1111-style prompt weighting; long-video chaining with audio-driven length;
 step-output caching, so re-running a fixed-seed workflow finishes instantly;
 and utility tasks for upscaling, face restoration, segmentation, captioning,
@@ -281,7 +314,7 @@ frame interpolation and more.
 - [Workspaces](docs/WORKSPACES.md) — Where your content lives, run directories, and several workspaces on one server
 - [Workflow Guide](docs/WORKFLOW_GUIDE.md) — JSON structure, variables, steps, data flow
 - [Quantization](docs/QUANTIZATION.md) — BitsAndBytes, TorchAO, GGUF, SDNQ
-- [Inference Acceleration](docs/ACCELERATION.md) — torch.compile, FirstBlockCache, MagCache, TaylorSeer, TeaCache
+- [Inference Acceleration](docs/ACCELERATION.md) — torch.compile, FirstBlockCache, MagCache, TaylorSeer
 - [Fast on 24GB](docs/RECIPES_24GB.md) — Recommended speed/memory configurations per model family
 - [LoRA](docs/LORAS.md) — Loading and stacking LoRA adapters
 - [IP-Adapter](docs/IP_ADAPTER.md) — Image-prompt conditioning
@@ -291,8 +324,7 @@ frame interpolation and more.
 
 ### Reference
 
-- [REPL Commands](docs/REPL_COMMANDS.md) — Interactive REPL command reference
-- [Worker Guide](docs/REPL_WORKER_GUIDE.md) — GPU persistence and troubleshooting
+- [Worker Guide](docs/WORKER_GUIDE.md) — GPU persistence and troubleshooting
 - [Dependencies](docs/DEPENDENCIES.md) — Installation details
 - [Security](docs/SECURITY.md) — Security model
 - [Testing](docs/TESTING.md) — Running the test suite