frank-zealot: sweep the live path — serve defaults, unit text, picker docs
- serve script: header + every fallback default re-keyed to the Bonsai-2 trio (vendor LLAMA_BIN, PQ2_0 MODEL_FILE, Q8_0 MMPROJ) and CACHE_TYPE_*:=q8_0 — a defaulted run must land on the shipped shape, never on the retired 9B/f16 pair (the trial window proved a silent default is how a swap goes wrong) - unit Description now names the payload + KV dtype that `systemctl status` will show during the next incident - OpenWebUI decoration-row description re-keyed, with the law that the row is live DB state a swap must follow into the database
This commit is contained in:
@@ -43,8 +43,10 @@ As of 2026-10-07 the picker exposes **exactly one model: `frank-zealot`**.
|
||||
| 2 | `http://host.containers.internal:7771/v1` | yes | `frank-zealot` | llama.cpp CUDA (RTX 3090, 2×200,704) | Dankclaw |
|
||||
|
||||
The `model` table carries exactly one decoration row, `frank-zealot`
|
||||
(context length 200,704 = the per-slot window; description: Qwen3.5-9B
|
||||
Q6_K + BF16 vision mmproj).
|
||||
(context length 200,704 = the per-slot window; description since 2026-10-17:
|
||||
Ternary-Bonsai-2-27B PQ2_0 + Q8_0 vision mmproj — the row's `description` is
|
||||
live DB state, so a payload swap must re-key it in the database too, not only
|
||||
in the repo).
|
||||
|
||||
A third gate sits *after* the table, and it is the one that bites family
|
||||
accounts (2026-10-07): a model row is only visible to a non-admin user when
|
||||
|
||||
Reference in New Issue
Block a user