@local/dsh-model-guard

LIMITATIONS

Known limitations

- **The order of `deepseek-account` and `deepseek-official` cannot be changed**: the client's `orderModelProviders()` unconditionally puts those two first, and no Host-side ordering can override it. The settings page states this as well. - **A model already selected in a session does not fall back automatically when disabled**: it disappears from the menu and shows a fallback label; `session/model-unavailable` is only raised when you send a message, so you need to pick another model manually. - **It narrows the human's choices without blocking internal calls**: models explicitly requested by subagents, compaction, and other components still run. - It relies on the `internal/get` waterfall (note the `internal` prefix), which is not a public contract. If a major DSH upgrade leaves the menu unfiltered or the order no longer following the settings, that event's signature has changed. - Ordering is a display-layer rearrangement only and **does not affect the default model** (the default is set by the profile's `agent-default-model` row).