[asto18089]

What

A named [providers.<name>] table with wire = "responses" (or "anthropic") minted a Chat Completions candidate: RouteRequest had no wire channel, so candidate.protocol() came from Custom's backward-compatible static policy, and every per-turn client built by CodewhaleClient::from_candidate bound Chat regardless of the table's dialect. The ambient spawn-time client (provider_wire_format_for_config) and the capability reporter did honor the override — so a host that resolves routes per turn silently POSTed {base}/chat/completions while its config said Responses, and a cross-model rebind rebuilt the client around the static protocol, downgrading the transport mid-session.

• RouteRequest gains wire_override, honored only for ProviderKind::Custom (built-ins keep their descriptor policy; a Chat override cannot demote a fixed-Responses builtin either). The resolver binds the Custom gate once so the protocol stamp cannot desync from it.
• The tui route layer populates the override from the resolved identity's scoped config — the same table provider_wire_format_for_config reads — so receipts, preflight, readiness, and the per-turn client all see one protocol. The app-server /v1/chat/completions pass-through threads the same override, so a Responses-bound table fails closed at its Chat-only guard instead of silently receiving a chat body.
• The client-internal model re-resolution pins the transport's own wire for Custom clients, so an engine-internal model switch cannot downgrade it. Same-table per-request switches that bypass rebind still fail closed at the protocol-mismatch guard (unchanged behavior, no silent downgrade).
• The per-config dialect parse moves into the config crate next to the field it reads (wire_dialect_override plus the two alias predicates), replacing the byte-identical private copies in the client and capability readers so one alias list cannot drift. A misspelled dialect keeps degrading to the static Chat policy, now with a warning naming the table.

Tests

• Resolver: the override mints the wire-true candidate (Responses and Anthropic) even on a relay base URL with no first-party catalog facts resurrected; builtins ignore it; absent/chat dialects keep the static policy.
• Route layer: a wire = "responses" custom table mints a Responses runtime route; a typo'd dialect degrades to Chat.
• Shared parse: canonical alias sets, case/separator normalization, explicit-chat arm, unknown degrade.
• cargo test -p codewhale-config --locked 177 passed; app-server suite 15 passed; targeted tui filters green; clippy -D warnings clean (config, app-server, tui lib).

Ported from the Pinvou/CodeWhale fork (#79), rescoped: the fork's encrypted-reasoning capture widening already landed upstream (all Responses routes that send include capture now).

Refs #6997

[claude]

Claude Code Review

This pull request is from a fork — automated review is disabled. A repository maintainer can comment @claude review to run a one-time review.

[Hmbown]

🤖 This reply is from Claude Opus 5.5, an AI agent working on behalf of the Codewhale maintainers. It is posted through @Hmbown's account, but Hunter did not write it.

Merged in 53e4e5a. Thank you @asto18089. Giving RouteRequest a wire channel fixes a bug I had misread on #6997: a named table's wire held only for the startup client, and every turn's re-installed route went back to Chat. I corrected my reply there and credited this PR. Not in a release yet.

— Written by Claude Opus 5.5 (AI agent) on behalf of the maintainers.