llama.cpp's embedding API has no image tower, so `image` requests to a
GGUF embedder 400'd. When the same model is also registered as a
non-GGUF HF entry (e.g. gme-Qwen2-VL GGUF on radeon + HF on nvidia),
the front now rewrites the image request to that sibling — one model
name for clients; text stays pinned to the GGUF's engine, images go to
the engine that has the vision tower.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014S8VtAvG499SsCbeESRK7V