Release 0.14.0

[dkackman]

Merges develop into master for 0.14.0. This is 284 commits since v0.13.0. The release notes are drafted in docs/RELEASING.md under 0.14.0.

Highlights:

• Gallery files are tagged final or intermediate. A file a later run read now lists as intermediate (All outputs are tagged "final" #928).
• Notes on runs, files, assets and workspaces, plus copy_to_workspace.
• The cost estimate scales with steps, canvas, frames and list length (plan.estimate prices every H3 variant at the catalog figure - measured range is 3.5-44 min #866, validate_workflow: a multi-shot hand-built workflow gets estimate null with no reason; inherited figure withheld past the template's size (#797/#821) #851).
• A host-RAM dispatch gate (bug: two int8 H3 jobs on two cards OOM-kill the host - dispatch is VRAM-aware only, and the earlier job was the one killed #869, #869 stage B: host-RAM dispatch gate, queue_wait event and waiting_for #910).
• Per-step timing and acceleration warnings.
• The H3 quality ramp, with MagCache 0.06 for cinema (H3 quality ramp: follow-up experiments (seed stability, cross-family composition lock, int4 base draft) #861, idea: quality-ramp skill - draft -> preview -> final tiers with measured cost/quality trade-offs (H3 first) #862, H3 cinema-path speed: follow-up experiments after first_block -22% (threshold, 20 steps, close-up, seeds, MagCache) #875, #862 stage 1: H3 quality-ramp section in minimax-h3 quality-and-speed reference #882).
• compare_outputs and the Compare page.
• New check-script findings.

Fixed during the pre-release review:

• Develop CI had been red since 0.14.0-alpha.1 opened. Three causes:
  • Notes traversal test (Linux only): its snapshot caught jobs.sqlite being written whenever the garbage collector closed a leftover connection. JobHistory._connect now closes its connections.
  • UI ratchet: App.svelte is back under the size ceiling and figure() under the complexity limit.
  • Backend ratchet: plan.py, server/jobs.py, api_models.py and pipeline.py were split under the 1,100-line ceiling, and the long function, complex function and prefix literal were fixed in code. Only modules (211 → 219) and test patch targets (326 → 327) were raised, approved, in 318a74b, which names each module.
• Model downloads write refs/main. Since cancel_download has no visible effect: download stays status downloading with frozen byte count, no pending-cancel state #899, a downloaded model read as incomplete and failed to load offline.
• An inline copy of a list-driven template is priced by its list length. It was quoted the template's default-length figure, unscaled and unflagged. v0.13.0 reported that case as unknown.
• The host-RAM gate takes the per-entry fit for a list longer than its history. Before, it gated an 8-shot shots-batch at 30 GB while validate warned about 50 GB.
• Whole-module compile: {fullgraph: true} no longer fails at the first denoise step. The new timing hook ran inside the compiled region.
• The gallery sort is now linear. It used to stall each keystroke on large libraries.
• All outputs are tagged "final" #928, all outputs tagged final.
  • A file a later run in the same workspace consumed, through output: or a kept asset:, lists as intermediate.
  • A step that declares result.role: "final" is never demoted.
  • The script-to-video and series-episodes skills have ingredient workflows declare "role": "intermediate".

Checks:

• Develop CI is green (backend, ui, e2e) at 93ca8db, and CodeQL is green.
• Locally, 14,724 backend tests and 673 vitest tests pass. ruff, lint, svelte-check, both ratchets and the generated API client are clean. The wheel builds and includes every new module.

Review notes, not blocking:

• speech_not_transcribed (check-script: ad-lib flagged in a short file vanishes (no finding) when the same audio opens a longer one #923) uses a fixed -40 dBFS level, so a scripted pause over a score can be flagged.
• level_for_transcription's +40 dB boost may make Whisper hallucinate on silent shots. This needs a lem check.
• quality-and-speed.md still names the older cinema cache setting.
• The delete_workspace check and its delete are two separate steps, so a submit can land in between.
• _synced_clock synchronizes the device on every step. This needs an A/B on lem.
• Skill byte headroom is tight: minimax-h3 has 10 bytes left.
• All outputs are tagged "final" #928 is not field-verified yet: lem and mini-ai are not on 93ca8db.

🤖 Generated with Claude Code