Both of these were found by running the previous commit rather than trusting
it, which is the only reason they are not still in.

The audio backend was read from the manager's per-model config map. That map
holds RUNTIME kwargs, and a whisper-server model has no row in it at all --
it lives in `whisper_servers` -- so the lookup answered "no backend" for
exactly the models whose backend decides the question, and the pick that was
supposed to avoid them chose `whisper2`. The entry is now read from
models.json, where `backend` is actually written, matched on id, alias, path
or basename because an audio model is referred to by any of them and the same
alias appears twice in a real catalogue. Verified against this install's
sixteen audio models: every one resolves, and the pick is now the model
measured to return fourteen word timings rather than the one measured to
return none.

The new warning is what caught it: the render reported "'whisper2' returned no
word timings" instead of quietly estimating. That is the whole point of it.

And `enabled: false` was hidden behind `all_engines`, which is the wrong seam.
The node-wide list the system worker serves -- the one the front hands clients
-- MUST pass all_engines=True, because that worker has no engine of its own
and would otherwise list nothing. So the filter was off on the only path that
mattered, and /v1/models offered LTX-2.5, Krea-2-Turbo and Krea-2-Edit: three
models configured ahead of a diffusers version that does not exist yet, each
of which answers 500. `include_disabled` is now a separate question, asked
only by the admin config view, because that is where a parked model gets
re-enabled.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01S8LAP3ueNzQJtwzhgVbq66