giq 0.6.1

giq 0.6.1 fixes two gaps found while installing 0.6.0. A vllm recipe that fills most of a card can now load on demand; before, it only ran when kept warm. And giq add no longer accepts a recipe that would fetch a whole repository into a directory named like a model file.

Fixes

• vllm recipes load on demand with a margin that fits how vllm uses memory.
  • giq kept up to 2 GB free on top of a recipe's VRAM figure before loading it. That covers engines that grow into compute buffers as they run. vllm reserves its weights, its KV budget and its buffers at start and never grows past them.
  • With the 2 GB margin, qwen3.8-27b-nvfp4-chat (29.7 GB) needed 31.7 GB, more than a 32 GB RTX 5090 has free. It waited three minutes and failed, unless kept warm. Meanwhile the dashboard and /capabilities called it runnable.
  • vllm now declares a 0.5 GB margin, the same one a keep-warm reload gets. On an RTX 5090 with nothing kept warm, a chat request loaded it on demand and answered in 91 s.
  • The load gate, eviction, /recipes, the Add page and /status all use the same margin, so they agree on what fits. A plugin's engine can declare its own (Engine.vram_margin, docs/plugins.md).
• A source that names a whole repository for a single-file path fails the plan.
  • For a recipe whose weights.path is one file (a .gguf, a .safetensors…) but whose source names the whole repository (hf:org/repo), giq add and the Add page would have downloaded the entire repository into a directory named like the file.
  • The plan now refuses it and says what to write instead: the file in the source, hf:org/repo/<file>. The download process refuses it too.

Upgrading

• From 0.6.0: check out v0.6.1 and run make sync, or install the 0.6.1 wheels from this release. Every package moves to 0.6.1 together.
• If one of your recipe files names a repository as source and a single file as path, change the source to name the file. Nothing breaks until you fetch it; the plan says so then.

Full changelog: v0.6.0...v0.6.1