The serve-cockpit Download action runs `WEIGHT_KEY=<model>:<variant> bash
scripts/setup.sh <model>` to fetch an exact catalog entry. But the friendly
model-name dispatch (`case "${MODEL_NAME}"`) hard-`exit 1`s on any model outside
the five flagship families — BEFORE the WEIGHT_KEY override a few lines down.
So a download of any other catalog model (e.g. llamacpp/vibethinker-3b-single)
died instantly with "unsupported model", never fetched a byte, and the cockpit
then reported "download incomplete (partial) — check disk / HF_TOKEN".
WEIGHT_KEY is documented as the authoritative "exact catalog entry" fetch-now
flow: the recipe fully specifies <model>:<variant> and load_weight_recipe()
already validates that the key's model matches MODEL_NAME. So when WEIGHT_KEY
is set, the unknown-model `*)` branch is now a no-op (the override below sets
PRIMARY_WEIGHT_KEY); the friendly guard still fails fast for a typo'd / truly
unsupported positional when WEIGHT_KEY is absent.
Validated: `WEIGHT_KEY=vibethinker-3b:prithivmlmods-q8 SKIP_MODEL=1 setup.sh
vibethinker-3b` now resolves the recipe (prithivMLmods/VibeThinker-3B-GGUF →
vibethinker-3b-gguf/prithivmlmods-q8) and reaches the download; an unknown
model with no WEIGHT_KEY still errors. +regression guard in test-setup-picker.
Co-Authored-By: Claude Opus 4.8 <[email protected]>
