diffusers-workflow 0.4.0b1__tar.gz → 0.4.0b5__tar.gz

{diffusers_workflow-0.4.0b1 → diffusers_workflow-0.4.0b5}/MANIFEST.in

@@ -1,3 +1,4 @@
 include dw/*.json
 recursive-include dw/workflows *.json
 recursive-include dw/server/ui *
+recursive-include dw/docs *.md

diffusers_workflow-0.4.0b5/PKG-INFO

@@ -0,0 +1,298 @@
+Metadata-Version: 2.4
+Name: diffusers-workflow
+Version: 0.4.0b5
+Summary: Declarative workflow engine and web UI for Hugging Face Diffusers
+Author: dkackman
+License: Apache-2.0
+Project-URL: Homepage, https://github.com/dkackman/diffusers-workflow
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: torch>=2.13.0
+Requires-Dist: torchvision>=0.28.0
+Requires-Dist: diffusers>=0.40.0
+Requires-Dist: transformers>=5.16.1
+Requires-Dist: accelerate>=1.14.0
+Requires-Dist: peft>=0.20.0
+Requires-Dist: safetensors>=0.8.0
+Requires-Dist: huggingface-hub>=1.29.0
+Requires-Dist: sentencepiece>=0.2.2
+Requires-Dist: protobuf>=7.36.0
+Requires-Dist: ftfy>=6.3.1
+Requires-Dist: torchsde>=0.2.6
+Requires-Dist: torchao>=0.18.0
+Requires-Dist: optimum-quanto>=0.2.7
+Requires-Dist: sdnq>=0.2.5
+Requires-Dist: gguf>=0.19.0
+Requires-Dist: bitsandbytes>=0.50.2; sys_platform == "linux"
+Requires-Dist: controlnet-aux>=0.0.10
+Requires-Dist: opencv-python-headless>=5.0.0.93
+Requires-Dist: kornia>=0.8.3
+Requires-Dist: spandrel>=0.4.2
+Requires-Dist: facexlib>=0.3.0
+Requires-Dist: numpy>=2.5.2
+Requires-Dist: Pillow>=12.3.0
+Requires-Dist: piexif>=1.1.3
+Requires-Dist: imageio>=2.37.4
+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: qrcode>=8.2
+Requires-Dist: requests>=2.34.2
+Requires-Dist: aiohttp>=3.14.3
+Requires-Dist: beautifulsoup4>=4.15.0
+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
+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"
+Requires-Dist: pytest-xdist>=3.8.0; extra == "dev"
+Requires-Dist: pytest-timeout>=2.4.0; extra == "dev"
+Requires-Dist: pytest-mock>=3.15.1; extra == "dev"
+Requires-Dist: pytest-asyncio>=1.4.0; extra == "dev"
+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"
+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)
+
+# diffusers-workflow
+
+Your GPU, as something an agent can drive.
+
+diffusers-workflow wraps the [Hugging Face Diffusers library](https://github.com/huggingface/diffusers)
+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.
+
+**Python 3.10-3.14 | CUDA (NVIDIA) | MPS (Apple Silicon) | CPU**
+
+<picture>
+  <source media="(prefers-color-scheme: dark)" srcset="docs/img/ui-workflows-dark.png">
+  <img alt="The workflow browser: every workflow as a card with its description, output kinds, and variables" src="docs/img/ui-workflows.png">
+</picture>
+
+## Getting started
+
+**1. Install.** The script picks the right torch build for your platform,
+creates a virtual environment and installs everything, MCP server included.
+
+```bash
+# Linux / macOS
+bash ./install.sh
+source ./activate
+
+# Windows
+.\install.ps1
+.\venv\scripts\activate
+```
+
+`python -m dw.test` confirms torch and diffusers import and shows which
+accelerator was found.
+
+**2. Start the engine.** Leave it running; everything else talks to it.
+
+```bash
+dw-serve
+# diffusers-workflow server on http://127.0.0.1:8765
+```
+
+That address is the web UI. Open it and run `templates/text-to-image` — a
+small, ungated model, so the first generation needs no Hugging Face login and
+downloads only a few GB.
+
+**3. Connect Claude Code.** Register the MCP server with the absolute path to
+`dw-mcp` in the venv you just made (the relative path is the one setup detail
+that reliably goes wrong):
+
+```bash
+claude mcp add dw -- "$(pwd)/venv/bin/dw-mcp"
+```
+
+Then, optionally, the [dw plugin](plugins/dw/README.md) — one skill per model
+family that knows which workflow fits a request and the rules that bite:
+
+```
+/plugin marketplace add dkackman/diffusers-workflow
+/plugin install dw@diffusers-workflow
+```
+
+Most of the shipped workflows (Flux, LTX-2, MiniMax...) use **gated** models.
+Request access on the model's Hugging Face page, then `huggingface-cli login`
+once; without it the run fails partway through with a 401/403 from the Hub.
+
+> **GPU on another machine?** Start the engine there with `--mcp` and connect
+> over HTTP — nothing to install on the laptop:
+>
+> ```bash
+> # on the GPU box
+> dw-serve --host 0.0.0.0 --token "$DW_API_TOKEN" --mcp --workspace ~/studio
+>
+> # on your laptop
+> claude mcp add --transport http dw http://gpu-box:8765/mcp \
+>   --header "Authorization: Bearer $DW_API_TOKEN"
+> ```
+>
+> The server's own **Server** page composes that line for the address you
+> pick. End to end: [Remote GPU server](docs/REMOTE.md).
+
+## Drive it from an agent
+
+Then just ask. The agent has 55 tools covering the whole surface — the
+workflow catalog, the real diffusers pipeline signatures, the job queue, the
+gallery, the model cache:
+
+![Claude Code driving the dw MCP server: creating a workspace, authoring a script, and generating from it](docs/img/claude-authoring.png)
+
+Generation is the long pass, and the agent stays with it — queuing each shot,
+waiting it out, and reporting what came back:
+
+![The same session hours later: shots rendering one at a time, roughly 30 minutes each, with the agent reporting progress between them](docs/img/claude-generating.png)
+
+What a session looks like:
+
+- **"What can this box run, and what do I already have?"** — `get_server_info`
+  for the accelerator and workspace, `list_workflows` for the catalog with each
+  entry's shape, cost and variables, `list_models` for what is already in the
+  hub cache. The agent knows the device before it proposes anything CUDA-only.
+- **"Take my Flux workflow, swap in the portrait LoRA, render four at 1024."**
+  — `get_workflow`, `get_pipeline_signature` to check the arguments exist,
+  `validate_workflow` (free: schema *and* signature checking, no model loads),
+  `save_workflow`, `run_workflow`. That last one refuses until the agent passes
+  `acknowledged_cost=true`, so it has to tell you what it is about to spend.
+- **"How's it going?"** — `wait_for_job` blocks for a bounded interval instead
+  of polling; `get_output_image` brings the result back into the conversation
+  so the agent can look at what it made.
+- **"That third frame is the one — keep it and seed the video pass from it."**
+  — `keep_output` promotes the file into the asset library under a name you
+  pick, and the next workflow references `asset:hero-frame.png`.
+
+Everything that costs real GPU time or real disk (`run_workflow`, `rerun_job`,
+`enhance_prompt`, `download_model`, `delete_model`, `update_diffusers`,
+`delete_workspace`) refuses until it is explicitly acknowledged, so an agent
+cannot quietly burn an hour of GPU or delete 40GB of weights.
+
+One server holds several **workspaces** — each with its own workflows, assets
+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.
+
+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).
+
+## The web UI
+
+Everything the engine does, in a browser, backed by the same persistent GPU
+worker — models stay loaded between runs.
+
+**An editor built from the real pipeline signatures.** Forms and argument
+autocomplete are generated by introspecting diffusers itself, so every knob a
+pipeline exposes is there with its documentation. Validation catches schema
+errors *and* argument typos before any model loads.
+
+![The editor: introspection-driven forms beside live JSON in Monaco](docs/img/ui-editor.png)
+
+**A gallery where every image is a recipe.** Outputs carry their full workflow
+and seed; *open as workflow* drops any image back into the editor, ready to
+reproduce or riff on. *Keep as asset* promotes a generated file into the asset
+library for later workflows to build on.
+
+![The gallery with generated images and videos](docs/img/ui-gallery.jpg)
+
+**A prompt library** stores a prompt once and lets any workflow reference it,
+with an *Enhance with AI* panel that expands an idea into a full prompt using
+a local language model. **A model manager** inventories the Hugging Face hub
+cache — sizes, last use, free space — and downloads or deletes models with
+live progress.
+
+![The model manager listing cached models with sizes](docs/img/ui-models.png)
+
+Jobs queue, stream progress live per denoising step, cancel cooperatively and
+persist to a searchable history. See [Server & Web UI](docs/SERVER.md) for the
+pages and the HTTP API.
+
+## The command line
+
+The engine also runs standalone, with no server involved:
+
+```bash
+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).
+
+## What's underneath
+
+Every front end reads and writes the same thing: a JSON document of named
+steps, each a diffusers pipeline or a utility task, whose arguments reference
+variables, earlier steps' outputs, stored prompts and assets rather than
+hard-coded values. That is what makes text-to-image chain into image-to-video,
+and what makes a generated image reopen as the exact recipe that produced it.
+[workflows/](workflows/) is a corpus of runnable examples across model
+families; the [Workflow Guide](docs/WORKFLOW_GUIDE.md) is the reference when
+you do want to write one.
+
+Because a workflow reaches any diffusers pipeline or quantization backend by
+dynamic import, loading one can execute arbitrary Python. Treat a workflow
+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;
+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,
+frame interpolation and more.
+
+## Documentation
+
+### Guides
+
+- [MCP Server](docs/MCP.md) — The agent tool surface (Claude Code, Claude Desktop)
+- [Server & Web UI](docs/SERVER.md) — The web UI, jobs API, and introspection service
+- [Remote GPU server](docs/REMOTE.md) — Using the server, UI and MCP from another machine
+- [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
+- [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
+- [Prompt Weighting](docs/PROMPT_WEIGHTING.md) — A1111-style syntax
+- [Prompt References](docs/WORKFLOW_GUIDE.md#prompt-references) — The stored prompt library and `prompt:` references
+- [Tasks](docs/TASKS.md) — Image processing, ControlNet preprocessors, utilities
+
+### Reference
+
+- [REPL Commands](docs/REPL_COMMANDS.md) — Interactive REPL command reference
+- [Worker Guide](docs/REPL_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
+- [Releasing](docs/RELEASING.md) — Cutting a release from a version tag
+- [Agent Loop](docs/AGENT_LOOP.md) — What the automated implementer/tester ticket labels mean, for anyone joining an Issue

diffusers_workflow-0.4.0b5/README.md

@@ -0,0 +1,223 @@
+[![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)
+
+# diffusers-workflow
+
+Your GPU, as something an agent can drive.
+
+diffusers-workflow wraps the [Hugging Face Diffusers library](https://github.com/huggingface/diffusers)
+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.
+
+**Python 3.10-3.14 | CUDA (NVIDIA) | MPS (Apple Silicon) | CPU**
+
+<picture>
+  <source media="(prefers-color-scheme: dark)" srcset="docs/img/ui-workflows-dark.png">
+  <img alt="The workflow browser: every workflow as a card with its description, output kinds, and variables" src="docs/img/ui-workflows.png">
+</picture>
+
+## Getting started
+
+**1. Install.** The script picks the right torch build for your platform,
+creates a virtual environment and installs everything, MCP server included.
+
+```bash
+# Linux / macOS
+bash ./install.sh
+source ./activate
+
+# Windows
+.\install.ps1
+.\venv\scripts\activate
+```
+
+`python -m dw.test` confirms torch and diffusers import and shows which
+accelerator was found.
+
+**2. Start the engine.** Leave it running; everything else talks to it.
+
+```bash
+dw-serve
+# diffusers-workflow server on http://127.0.0.1:8765
+```
+
+That address is the web UI. Open it and run `templates/text-to-image` — a
+small, ungated model, so the first generation needs no Hugging Face login and
+downloads only a few GB.
+
+**3. Connect Claude Code.** Register the MCP server with the absolute path to
+`dw-mcp` in the venv you just made (the relative path is the one setup detail
+that reliably goes wrong):
+
+```bash
+claude mcp add dw -- "$(pwd)/venv/bin/dw-mcp"
+```
+
+Then, optionally, the [dw plugin](plugins/dw/README.md) — one skill per model
+family that knows which workflow fits a request and the rules that bite:
+
+```
+/plugin marketplace add dkackman/diffusers-workflow
+/plugin install dw@diffusers-workflow
+```
+
+Most of the shipped workflows (Flux, LTX-2, MiniMax...) use **gated** models.
+Request access on the model's Hugging Face page, then `huggingface-cli login`
+once; without it the run fails partway through with a 401/403 from the Hub.
+
+> **GPU on another machine?** Start the engine there with `--mcp` and connect
+> over HTTP — nothing to install on the laptop:
+>
+> ```bash
+> # on the GPU box
+> dw-serve --host 0.0.0.0 --token "$DW_API_TOKEN" --mcp --workspace ~/studio
+>
+> # on your laptop
+> claude mcp add --transport http dw http://gpu-box:8765/mcp \
+>   --header "Authorization: Bearer $DW_API_TOKEN"
+> ```
+>
+> The server's own **Server** page composes that line for the address you
+> pick. End to end: [Remote GPU server](docs/REMOTE.md).
+
+## Drive it from an agent
+
+Then just ask. The agent has 55 tools covering the whole surface — the
+workflow catalog, the real diffusers pipeline signatures, the job queue, the
+gallery, the model cache:
+
+![Claude Code driving the dw MCP server: creating a workspace, authoring a script, and generating from it](docs/img/claude-authoring.png)
+
+Generation is the long pass, and the agent stays with it — queuing each shot,
+waiting it out, and reporting what came back:
+
+![The same session hours later: shots rendering one at a time, roughly 30 minutes each, with the agent reporting progress between them](docs/img/claude-generating.png)
+
+What a session looks like:
+
+- **"What can this box run, and what do I already have?"** — `get_server_info`
+  for the accelerator and workspace, `list_workflows` for the catalog with each
+  entry's shape, cost and variables, `list_models` for what is already in the
+  hub cache. The agent knows the device before it proposes anything CUDA-only.
+- **"Take my Flux workflow, swap in the portrait LoRA, render four at 1024."**
+  — `get_workflow`, `get_pipeline_signature` to check the arguments exist,
+  `validate_workflow` (free: schema *and* signature checking, no model loads),
+  `save_workflow`, `run_workflow`. That last one refuses until the agent passes
+  `acknowledged_cost=true`, so it has to tell you what it is about to spend.
+- **"How's it going?"** — `wait_for_job` blocks for a bounded interval instead
+  of polling; `get_output_image` brings the result back into the conversation
+  so the agent can look at what it made.
+- **"That third frame is the one — keep it and seed the video pass from it."**
+  — `keep_output` promotes the file into the asset library under a name you
+  pick, and the next workflow references `asset:hero-frame.png`.
+
+Everything that costs real GPU time or real disk (`run_workflow`, `rerun_job`,
+`enhance_prompt`, `download_model`, `delete_model`, `update_diffusers`,
+`delete_workspace`) refuses until it is explicitly acknowledged, so an agent
+cannot quietly burn an hour of GPU or delete 40GB of weights.
+
+One server holds several **workspaces** — each with its own workflows, assets
+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.
+
+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).
+
+## The web UI
+
+Everything the engine does, in a browser, backed by the same persistent GPU
+worker — models stay loaded between runs.
+
+**An editor built from the real pipeline signatures.** Forms and argument
+autocomplete are generated by introspecting diffusers itself, so every knob a
+pipeline exposes is there with its documentation. Validation catches schema
+errors *and* argument typos before any model loads.
+
+![The editor: introspection-driven forms beside live JSON in Monaco](docs/img/ui-editor.png)
+
+**A gallery where every image is a recipe.** Outputs carry their full workflow
+and seed; *open as workflow* drops any image back into the editor, ready to
+reproduce or riff on. *Keep as asset* promotes a generated file into the asset
+library for later workflows to build on.
+
+![The gallery with generated images and videos](docs/img/ui-gallery.jpg)
+
+**A prompt library** stores a prompt once and lets any workflow reference it,
+with an *Enhance with AI* panel that expands an idea into a full prompt using
+a local language model. **A model manager** inventories the Hugging Face hub
+cache — sizes, last use, free space — and downloads or deletes models with
+live progress.
+
+![The model manager listing cached models with sizes](docs/img/ui-models.png)
+
+Jobs queue, stream progress live per denoising step, cancel cooperatively and
+persist to a searchable history. See [Server & Web UI](docs/SERVER.md) for the
+pages and the HTTP API.
+
+## The command line
+
+The engine also runs standalone, with no server involved:
+
+```bash
+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).
+
+## What's underneath
+
+Every front end reads and writes the same thing: a JSON document of named
+steps, each a diffusers pipeline or a utility task, whose arguments reference
+variables, earlier steps' outputs, stored prompts and assets rather than
+hard-coded values. That is what makes text-to-image chain into image-to-video,
+and what makes a generated image reopen as the exact recipe that produced it.
+[workflows/](workflows/) is a corpus of runnable examples across model
+families; the [Workflow Guide](docs/WORKFLOW_GUIDE.md) is the reference when
+you do want to write one.
+
+Because a workflow reaches any diffusers pipeline or quantization backend by
+dynamic import, loading one can execute arbitrary Python. Treat a workflow
+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;
+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,
+frame interpolation and more.
+
+## Documentation
+
+### Guides
+
+- [MCP Server](docs/MCP.md) — The agent tool surface (Claude Code, Claude Desktop)
+- [Server & Web UI](docs/SERVER.md) — The web UI, jobs API, and introspection service
+- [Remote GPU server](docs/REMOTE.md) — Using the server, UI and MCP from another machine
+- [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
+- [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
+- [Prompt Weighting](docs/PROMPT_WEIGHTING.md) — A1111-style syntax
+- [Prompt References](docs/WORKFLOW_GUIDE.md#prompt-references) — The stored prompt library and `prompt:` references
+- [Tasks](docs/TASKS.md) — Image processing, ControlNet preprocessors, utilities
+
+### Reference
+
+- [REPL Commands](docs/REPL_COMMANDS.md) — Interactive REPL command reference
+- [Worker Guide](docs/REPL_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
+- [Releasing](docs/RELEASING.md) — Cutting a release from a version tag
+- [Agent Loop](docs/AGENT_LOOP.md) — What the automated implementer/tester ticket labels mean, for anyone joining an Issue