setup.sh reads only the first positional (the model) and DOWNLOADS WEIGHTS;
it does not select or boot a serving config. A stray second arg — commonly a
launch slug like `vllm/int8` — was silently dropped.
In issue #250 a user ran `setup.sh gemma-4-31b vllm/int8`; the slug was
ignored, and when the real failure surfaced (a purged-nightly compose pin,
since fixed in the v0.21.0 repin) they mis-attributed it to the setup command.
Silently swallowing the arg reinforced the wrong mental model.
Now any positional beyond the model errors (exit 64) with a pointer to the
launch path (`launch.sh --variant <slug>` / `switch.sh <slug>` / `--list`).
`both` recurses with a single arg, so it's unaffected. switch.sh and launch.sh
already guard this (second positional → "multiple variants supplied"); setup.sh
was the only gap.
Co-authored-by: noonghunna <[email protected]>
Co-authored-by: Claude Opus 4.8 (1M context) <[email protected]>
