Release 0.14.0

README.md

@@ -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 62 tools covering the whole surface — the
+Then just ask. The agent has 65 tools covering the whole surface — the
 workflow catalog, the real diffusers pipeline signatures, the job queue, the
 gallery, the model cache:
 

docs/LORAS.md

@@ -165,8 +165,14 @@ exact - an adapter on the wrong base usually loads and is quietly worse.
 (the turbo keyframe files are `["t2va", "fl2va"]`). `proven` and `rejected` entries need `evidence`; a rejected
 entry's first note is why. The schema is `GET /api/lora-schema`.
 
+The server's validate enforces that `workflow` (#870): a step whose workflow
+sits in the other partition is refused when the entry is `proven`, and only
+warned when it is `trial` or `rejected`. Without a covering entry the file
+name decides (`ref2v` / `fl2v`), as in `dw/adapter_compatibility.py`.
+
 Promotion: a trial that worked is saved with `save_lora` (or
-`PUT /api/loras/{name}`) as `proven`, its job id in `evidence`.
+`PUT /api/loras/{name}`) as `proven`, its job id in `evidence`. Promoting
+it is also what makes its `workflow` refuse a mismatched step.
 
 ## Finding LoRAs on the Hub
 

docs/RECIPES_24GB.md

@@ -116,7 +116,7 @@ pipeline-level `offload`. The working 24GB configuration at 960x544:
 | `text_encoder` | `remove_modules: ["lm_head"]` - the encoder path never calls it |
 | `text_encoder.model` | SDNQ int4, `truncate_layers: {"language_model.layers": 51}`, `group_offload` `leaf_level` |
 | `vae`, `audio_vae` | SDNQ int8, `device: "cuda"`, `residency: "on_demand"` |
-| pipeline | `cache: first_block` (`threshold: 0.1`) on the 20-step ref2va workflows only - measured on the 9-step turbo schedule it never skips (consecutive distilled steps differ too much for the threshold), so the turbo examples omit it rather than hold cache state for nothing |
+| pipeline | `cache: first_block` (`threshold: 0.05`) only on a ~30-step base-model run (`lora_model_name: null`): -22% denoise there, identical staging and faces. It skips nothing at 12 steps or on a turbo schedule (consecutive distilled steps differ too much), and every H3 template takes it as a `cache` argument (null by default): `{"type": "first_block", "threshold": 0.05}`. Measured on a 3090 with `sage_hub`; see the `minimax-h3` skill's `references/quality-and-speed.md` |
 
 The VAEs are the piece worth calling out. They hold roughly 3GiB, are used only to
 encode references and decode the result, and group offloading them is worse than useless

docs/RELEASING.md

@@ -7,6 +7,115 @@ notes from commits at tag time (see below). This section is a scratch pad
 for items a branch's author wants the next release note to name; clear it
 when a release ships.
 
+### 0.14.0
+
+<!-- Drafted from v0.13.0..develop (7b72a7de). Paste into the GitHub release body once the tag has published: gh release edit v0.14.0 --notes-file ... -->
+
+A release about what a run is and what it will cost. Gallery files say
+whether they are a final or an intermediate, anything can carry a note, and
+runs copy between workspaces. The cost estimate scales with steps, canvas
+and frames instead of quoting a flat figure that was up to 12x off, and a
+queued job waits for host RAM rather than being OOM-killed.
+
+**Roles and notes** (#855-#858)
+
+- Gallery files are tagged final or intermediate (inferred when a workflow
+  doesn't say), and the gallery opens on finals. A run lists what it was
+  Made from.
+- A file a later run in the workspace read, through `output:` or an asset
+  kept from it, lists as intermediate, so a project's shots, narration and
+  score step aside once the cut that uses them exists. A step that sets
+  `result.role: "final"` stays final. The `script-to-video` and
+  `series-episodes` skills have ingredient workflows declare
+  `"role": "intermediate"` (#928).
+- Runs, files, assets and workspaces take an optional note: `note` on
+  `run_workflow`, `upload_asset` and `keep_output`, and MCP `set_note`.
+  Every listing carries notes; the web UI edits them in place as Markdown.
+- Starring a file keeps it. A rerun records the job it reran (`rerun_of`).
+- `copy_to_workspace` copies whole runs, with manifests, and asset-library
+  entries into another workspace (#853, #859, #860).
+
+**Cost and host RAM** (#866, #869, #881)
+
+- The estimate scales as steps x canvas x frames against the template's
+  defaults (`basis: "derived"`, `scaled` names the axes). Any other driver
+  that moves keeps the figure and sets `low_confidence`; H3 adds weights,
+  LoRA, attention and cache as drivers. On the H3 matrix it lands within
+  30% (B3->L5: 32.3 min quoted, 29.5 run), and an inline copy prices
+  within 2% of its template (#906-#908, #915, #916, #921).
+- A queued job is held at dispatch while its projected host-RAM peak won't
+  fit, and stays `queued` with `waiting_for` and a `queue_wait` event. It
+  is never held with nothing else running. On a 125 GB, 2x 3090 host a
+  second int8 H3 job waited ("needs ~87 GB, ~57 GB free") while two int4
+  jobs ran at once (#909, #910).
+- An OOM kill now takes the newest dispatch, not the earlier job (#881).
+
+**Timing and caches** (#867, #868, #905)
+
+- Manifest entries carry per-step timing (`first_pass_s`, `pass_s`) and
+  step-cache skip counts (`cache_stats`). A `first_pass_slow` warning names
+  a warm pipeline's slow first pass (#924: 202 s against 37 s/pass).
+- Validate warns on acceleration that can't pay off or won't run: a cache
+  on a short schedule or with no transformer to attach to, `fullgraph`
+  with a cache, a CUDA-only attention backend, and an unbraced type name
+  under a `*_dtype` key (#887, #904, #926).
+- The plan fingerprint and step cache key only on what changes the output,
+  so metadata edits and `12.0` vs `12` no longer miss the cache (#905,
+  #911).
+- Every H3 template exposes `attention_backend` and `cache` (#883, #884).
+  MagCache calibration now reports its ratios on H3 (#927); with them,
+  MagCache 0.06 ran the cinema final in 18.1 min, 39% under L5 (#875).
+
+**H3 quality ramp** (#861, #862, #882)
+
+- The `minimax-h3` skill has measured draft -> final rungs. TV: L1 (~5.4
+  min) -> L7 (~7.2 min), changing only `weights_dtype`. Cinema: B3 (~12.9
+  min) -> L5 (~29.5 min), changing only steps. Staging carries at the same
+  seed; the skill says what to approve at each tier.
+- A proven LoRA catalog entry decides which H3 step an adapter fits,
+  ahead of its filename (#870, #888).
+
+**Compare, sweeps and check-script** (#871, #872, #919-#925)
+
+- `compare_outputs` puts 2-4 outputs side by side with PSNR/SSIM; the web
+  UI's Compare page plays them in sync and lists the differing arguments.
+  The workspaces guide has a Running a sweep section.
+- check-script refuses a wrong shot name at validate, adds
+  `unscripted_speech` and `speech_not_transcribed`, and levels its input
+  so the verdict no longer depends on loudness.
+
+**Web UI**
+
+- A running-jobs chip, a tab title that tracks the running job, measured
+  run times on cards, drag-and-drop upload, and keyboard culling in the
+  gallery.
+
+**Fixes**
+
+- `cancel_download` stops queued files and shows `cancel_requested`
+  (#899); a model download records `refs/main`, so it reads complete.
+  `cancel_job` takes effect during a load (#892).
+- A kept asset keeps its lineage and its job survives the workspace's
+  deletion (#902, #913, #917, #918).
+- `get_gallery_metadata` measures an image, and `include_workflow=false`
+  omits the embedded workflow (#922).
+- An inline copy of a list-driven template is no longer quoted the
+  template's default-length price unscaled.
+- The host-RAM gate no longer under-projects a list-driven run whose peak
+  grows with the list.
+- Whole-module `compile: {fullgraph: true}` no longer fails at the first
+  denoise step after the timing hook.
+- FasterCache runs on FLUX.1-dev (#897); denoise time on mps is no longer
+  billed to decode (#896).
+- The gallery's sort no longer stalls each keystroke on a large library.
+
+**Dependencies and deploy**
+
+- No dependency floors changed.
+- `scripts/dw-serve.service` sets `OOMPolicy=continue`, so one worker's
+  OOM kill no longer stops the server. Reinstall the unit to pick it up.
+- The jobs history gains a `memory_key` column, migrated on start.
+
 ### 0.13.0
 
 <!-- Drafted from v0.12.0..develop. Paste into the GitHub release body once the tag has published: gh release edit v0.13.0 --notes-file ... -->
@@ -140,9 +249,10 @@ hallucinations as lyrics.
 
 **Fixes**
 
-- The inherited cost estimate is withheld when an inline workflow runs
-  more steps or frames than the template it came from, instead of
-  quoting the template's number (#821: a 7x under-quote).
+- The inherited cost estimate is re-priced linearly when an inline
+  workflow runs more steps or frames than the template it came from,
+  instead of quoting the template's number (#821: a 7x under-quote); the
+  estimate carries `scaled` (why) and `low_confidence` (#851).
 - `assess_output` shot findings carry `index` and `start_frame`, so a
   repeated shot name is unambiguous (#835).
 - `dialogue-short` and `music-video` expose `match_levels_dbfs` (#836).