Provider and model catalog should be consistent across onboarding, config, and runtime #108
Description
Summary
Supported providers and models are not yet exposed consistently across setup, config, and runtime behavior in public Core.
Current dev-cycle goal:
- show supported providers/models where they are actually usable
- avoid listing stale, partial, or misleading inventory
- keep onboarding, config panels, and runtime selection surfaces aligned
- surface exact blockers when a provider/model cannot be supported cleanly
Why this matters
A provider catalog that differs between setup, config, and runtime creates mistrust and makes support much harder.
Acceptance criteria
- supported providers/models are consistent across onboarding, config, and runtime surfaces
- stale inventory is removed or explicitly marked unavailable
- newly supported inventory appears end to end, not in just one UI surface
- runtime selection does not drift from visible catalog state
Internal tracking
WEB-113