[Bug] Kiro saved unpublished model IDs remain routable after catalog removal #6215

Problem

#6214 removes unpublished model IDs from Kiro’s static picker, but a configuration saved before that correction can still name one of those IDs. The adapter intentionally keeps manual wire handling, so the request reaches Kiro and receives the provider rejection instead of an actionable local explanation.

Affected currently unpublished IDs:

• gpt-6-sol
• gpt-6-luna
• claude-opus-5.5
• claude-sonnet-5.5

Kiro’s current official model catalog lists GPT-5.6, Claude Opus 5, and Claude Sonnet 5, but not the IDs above: https://kiro.dev/docs/models/

Impact

Users who selected a preemptive row before #6214 can keep a hidden, failing route after upgrading. The picker no longer offers the route, so the source of the failure is harder to discover.

Design question

Preserve manual/future-model escape hatches without silently destroying configuration, while making known-unpublished saved IDs explicit. Options include a route-time local diagnostic, a config warning with a visible disabled state, or a narrowly owned migration that preserves recovery information.

Acceptance criteria

• existing saved unpublished Kiro IDs do not fail as an unexplained upstream provider error
• no silent destructive rewrite of user configuration
• manually configured future IDs remain possible through an explicit/diagnosable path
• direct-provider catalogs and accounting-only price fallbacks remain unaffected
• regression coverage includes an existing saved route across the catalog correction

Follow-up to #6214; intentionally not bundled into the picker hotfix.