hermes - 💡(How to fix) Fix fix(vision): _resolve_single_provider kwargs regression — fallback_chain silently fails on Gemini quota errors

Problem

When Gemini returns HTTP 429 (quota/resource exhausted), the vision fallback chain (_try_configured_fallback_chain) attempts to create clients for fallback providers (xiaomi-tp, ollama) via _resolve_single_provider. However, this function does not correctly forward explicit_base_url/explicit_api_key kwargs to resolve_provider_client after certain updates.

Root cause: _resolve_single_provider calls resolve_provider_client(provider=..., model=..., explicit_base_url=base_url, explicit_api_key=api_key). The explicit_base_url/explicit_api_key parameters are ~14 lines after def — any refactoring that shifts the function body can silently break the fallback chain.

Impact

• Users on Gemini free tier get quota exhausted → 429
• Fallback chain silently returns None for all providers
• User sees raw Gemini error, no fallback to MiMo/Ollama
• Verify check (grep -A3) was insufficient; explicit_base_url is on line ~14

Expected

_resolve_single_provider should robustly forward all kwargs to resolve_provider_client. Options: make resolve_provider_client accept base_url/api_key as positional params; add a unit test; document the contract.

Workaround

Re-apply kwargs fix after every hermes update.