The silent one. self.models is keyed by model_key, and model_key was the
weights path -- so two entries naming the same path shared ONE resident
pipeline. LTX-2.3-PinkCherry requested while LTX-2.3-10Eros was resident never
loaded its own transformer: no load, no eviction, straight to generation, and
HTTP 200 with 10Eros weights. Every other instance of this family failed
loudly; this one answered successfully with the wrong model.

It also meant both wrote measured_vram_gb to the same key, so a Q4_K_M and a
Q5_K_M of different sizes were overwriting each other sizing.

A key is split only when the caller named something, two or more DISTINCT
aliases point at that same path, and the named one is among them. A lone
aliased model, or a request that names the path, keeps the key it has always
had.

That narrowness is the point, not caution for its own sake: collapsing every
name form onto one key is deliberate a few lines above -- without it two
concurrent first-requests under different spellings each load an instance and
exceed max_model_instances=1. This is not a licence to key by whatever the
caller typed.

Verified live: the estimator now reports key=video:LTX-2.3-10Eros where both
models previously shared key=video:diffusers/LTX-2.3-Diffusers.

Suite: 15 failed, 5268 passed -- the same 15 as the baseline.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014T3rZnmWyKjWZerwsb27jZ