305ecac8b2
The first commit's gate sat inside ``_get_named_custom_provider`` — which only handles user-defined custom blocks. Built-in provider names (``openai`` / ``anthropic`` / ``openrouter`` / ``gemini`` / ...) have their own resolution paths in ``resolve_runtime_provider`` (pool / explicit / generic / ``resolve_provider``) and bypass that gate. So a user who flipped ``providers.openrouter.enabled: false`` would still see OpenRouter resolved when something explicitly requested it (e.g. a fallback chain entry). That defeats the point of the flag. This commit moves the gate one level up: right after ``requested_provider`` is computed, before any custom / built-in / Azure short-circuit. It now raises a typed ``ValueError`` referencing the YAML path, so callers can recognise it and advance to the next fallback instead of silently using a disabled provider. 3 new tests cover: * disabled custom provider raises * disabled built-in provider raises * enabled provider doesn't hit the gate All 20 tests in the providers suite pass.