What
The function that resolves default 3rd-party model IDs now throws a descriptive error if a model tier is configured with bedrock: null, instead of silently passing null downstream.
Details
- Previous behavior:
nullwas passed as the Bedrock fallback ID, which could produce cryptic downstream failures - New behavior: immediately throws
"A DEFAULT_3P_*_KEY points at a model config with bedrock: null — Bedrock setup has no fallback id for that tier" - This surfaces misconfiguration at the resolution point rather than at API call time
Evidence
Error message (search for "A DEFAULT_3P_*_KEY points at a model config with bedrock: null")
Strings lifted out of the shipped bundle, so the claim above can be checked against them.