fix(model): accept Discord 'name:provider/model' on every surface; refuse unknown provider

[Kyzcreig]

fix(model): accept Discord 'name:provider/model' on every surface; refuse unknown provider

Pasting Discord's native /model rendering (/model name:claude-bpx-5/claude-fable-5-1)
into Telegram kept the current provider and stored the whole string as the model
id (claude-apr/name:claude-bpx-5/claude-fable-5-1), breaking the session.

• parse_model_flags_detailed (the one parser for CLI/gateway/TUI) strips a leading
  name:/name=/model:/model= option label, so all four forms converge:
  name:P/X, P/X, X --provider P, name:X --provider P.
• switch_model refuses X/model when X is neither a resolvable provider nor a
  vendor namespace, the current provider is not an aggregator, and the id is not
  recognised by the endpoint or declared in config. No state change.
• Gateway /model confirmation appends the resolved provider/model pair.

Verified: 21 parser/switch tests + 2 gateway tests (Telegram literal Discord form
switches provider AND model; unknown prefix refused, no override written).
RED on base: 12 fail without the impl. Neighbor /model + TUI suites: 989 passed,
2 failed. Both failures are in test_user_providers_model_switch.py and fail
identically on clean fork/main.

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.}

[Kyzcreig]

Upstream port: NousResearch#121947. It carries only the name:/model: label strip in parse_model_flags_detailed, plus the parser tests (red/green on upstream main: 7 fail / 4 pass without the fix, 11 pass with it). The provider/model inline split and the unknown-prefix refusal are not ported. Upstream has no _parse_inline_provider_model, uses provider:model as its inline syntax, and treats a slash as an aggregator vendor slug, so the split would be a behaviour change there. The PR body says so.

[Kyzcreig]

🤖 merged-by: apollo · lane: kanban-merge-pass · gate: BYPASS: FleetReview paused by Ace 2026-09-22 (state/fleetreview-pause marker present) · why: t_6b449bc0: /model on Telegram (and every gateway) must parse the Discord-rendered 'name:pro; worker completed in place, CI green

[ang-prism]

FleetReview

Post-merge review (fleetreview:post-merge override): this reviewed the merge commit against its first parent — the bytes that already shipped. It is not a pre-merge gate pass.

Confidence: 3/5

Findings

• P1 hermes_cli/model_switch.py:2494 — Wrong route
• P1 hermes_cli/model_switch.py:782 — Stripping a leading name: in the shared parser breaks the relay's name:<subscription>/<model> routing syntax

---

FleetReview provenance · models: B=gpt-6-sol, C=claude-code-opus-5-5, D=grok-4.6, F=gpt-6-sol · cost: $1.94 · duration: 7m 26s · rounds: 1 · files examined: 4