The LTX-2.5 key reconciliation shipped, the retry failed identically, and the
repair had never run. It needs the component's config.json to know which names
the class expects, and _component_dir looked only in the local snapshot --
which, for a component whose weights come from a GGUF, is precisely the
subfolder nobody downloads. 20 GB of weights the file replaces are not worth
fetching; a few hundred bytes of config are.

Cache first, then one hf_hub_download of that component's config.json. Same
lesson as a cache-only existence check on a rented pod: an answer of "not
here" from a cache is not an answer about the repo.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014T3rZnLhydX9QqUcfBbqLu