Start with less YAML.Name the installed catalog route and its credential reference. Add endpoint or model fields only when evidence requires them.
One manual route creates three misleading symptoms.
The hand-declared model carries no reasoning-effort metadata.
developer 400Generic endpoint detection assumes a role this gateway rejects.
A refused profile edit can leave an older route active.
A non-empty models list replaces the catalog.
The safe fix changes by release.
supportsDeveloperRole is outside the configurable compat schema.
Custom routes can explicitly disable developer-role dispatch.
Adjust one installed model without hiding the rest.
A 400 naming a message role is not an API-key verdict.
Capture the first provider response and prove which configuration generation is active before rotating credentials.
Primary evidence.
Preserve the catalog before customizing it.
The complete runbook includes the minimal profile, failure classification, version boundary, replacement semantics, override rules, custom-model workflow, and fifteen acceptance gates.
Read the complete runbook