Third attempt at this, and the first two failed for the same reason: they asked
_config_for_model(requested_id) to find the sibling, but that helper resolves an
alias THROUGH self.model_aliases to the shared weights path — landing right back on
the wrong sibling. So the comparison was always "same object", the swap never
happened, and 0.1.94 still logged

  [vram-est][debug] key='…/gemma-4-26B-A4B-…gguf' -> 51.97 GB | measured_cfg=51.969
  Loading '…gguf': need 52.0 GB VRAM — evicting
  On-request VRAM eviction: unloading active model 'lisa-32k' (measured 22.47 GB)

The estimator now scans self.config for an entry whose `alias` field IS the
requested id. Aliases are unique per entry, so it needs no path comparison and
doesn't depend on how self.config is keyed — which is what the earlier attempts
got wrong. The path-based rule stays as a fallback for entries without an alias.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0182DhR1eFNPQyGmDrpHbedY