Files
zeekay 44fa4501f2 every router preference led with a model that no longer exists
All eight lists — code, reasoning, math, creative, vision, long_context,
cheap_chat, default — named a zen4* or zen3* champion first. Those families were
collapsed into the zen5 lineup long ago, so not one of the eight preferred model
could ever serve.

It reported nothing, and the reason is the routing rule itself: FIRST SERVABLE
WINS. The router walks past a dead champion, a fallback answers, the request
succeeds. A preference that does nothing looks exactly like a preference that
worked.

`vision` was the worst of it. Its top THREE were dead (zen5-omni, zen3-omni,
zen3-vl) and the live house vision SKU was not in the list at all — so the one
task where our own model matters most routed to another vendor every time.

Every id is now checked against GET /v1/models, and each list leads with a house
model that serves: zen5-coder, zen5-pro, zen5, zen-vl, zen5-mini.

Three tests hold it. They assert what is provable OFFLINE — no preference names
a retired family, no list leads with one, and every list leads with a house
model — and deliberately DO NOT assert that each id is declared in
conf/models.yaml, because that is not true and should not be: prod's surface is
the deployed ConfigMap plus what the zen, enso and openrouter families discover
at runtime. Asserting it fails on gpt-5.3-codex, which is servable today. That
class belongs to cmd/catalog, against the vendor. Mutation-checked: restoring a
zen4 champion fails two of the three.
2026-08-19 22:45:04 -07:00
..