mirror of
https://github.com/nesquena/hermes-webui.git
synced 2026-05-25 11:10:18 +00:00
ec403fa3cf
Opus advisor on stage-303 (#1738 verification Q4) flagged that the catalog-coverage branch produces a redundant repair-write per chat-start when the active Codex default is itself slash-prefixed: the repair sets `provider_context = None`, the next chat-start hits the same branch because `requested_provider is None` again, and the repair fires repeatedly. In practice Codex `default_model` is always a bare `gpt-...` ID from the Codex catalog, so this is theoretical. But once we've decided this session belongs to Codex, we should persist that decision. Drop the conditional catalog-coverage check and unconditionally attach `raw_active_provider` ("openai-codex") on this repair path. The shape is now stable across resolutions. Absorb-in-release per Opus stage-303 verdict — small, defensive, ≤10 LOC.