The previous two attempts wired request_model — which only video and image
generation use. Chat completions go through get_model_for_request ->
_load_model_by_name -> ensure_vram_for, and that path collapses the alias the same
way, so on 0.1.93 the second lisa-32k request still logged

  [vram-est] key='…/gemma-4-26B-A4B-…gguf' source=measured(force) -> 51.97 GB
  Loading '…gguf': need 52.0 GB VRAM, have 4.6 GB free — evicting models
  On-request VRAM eviction: unloading active model 'lisa-32k' (measured 22.90 GB)

get_model_for_request now keeps the requested id, passes it to
_load_model_by_name, and from there to both ensure_vram_for and the
expected_vram_gb the backend uses to size its GPU-layer split — so lisa-32k is
sized as itself (22.9 GB) rather than as lisa (51.97 GB).
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0182DhR1eFNPQyGmDrpHbedY