The previous attempt at this didn't fire. request_model overwrites the requested
name with the alias target on its first resolution step:

    if requested_model in self.model_aliases:
        requested_model = self.model_aliases[requested_model]

so by the time anything looks a config up, 'lisa-32k' no longer exists — model_key
and resolved_name are both the weights path, they compare equal, and the
same-path-sibling check had nothing to compare. Confirmed live on 0.1.92: the
second lisa-32k request still logged "need 52.0 GB VRAM, have 4.6 GB free" and
evicted the model that was serving it.

Keep the original id in _requested_id before that overwrite, hand it to
ensure_vram_for at all three reservation sites, and let _get_model_used_vram_gb try
it ahead of resolved_name. Against the live config: lisa-32k now sizes at 22.44 GB
instead of lisa's 51.97 GB, and qwen38-128k at 19.50 instead of qwen38's 18.00.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0182DhR1eFNPQyGmDrpHbedY