dsh-plugin-model-capability

DSH stores its LLM provider routes in the llm-pi-ai section of settings.yaml, and hand-editing that block is both error-prone and repetitive. Two pain points dominate: gateway compatibility and thinking-level wiring. Vendors like DashScope compatible-mode, Moonshot, Zhipu, MiniMax, Volcengine Ark, SiliconFlow, and Baidu Qianfan each handle OpenAI-dialect fields such as developer role and reasoning_effort differently, and the seven thinking levels require a vendor-specific wire value that is tedious to map by hand. This plugin adds a dedicated Model Capability page to the DSH Web settings sidebar, replacing YAML surgery with a purpose-built GUI. The per-model editor covers name, context window (with K/M suffix support), max output tokens, input modalities, and the full seven-level reasoning matrix where every level accepts its own wire value or can be batch-filled with one click. The per-route editor handles API dialect selection, default parameters, cache retention, timeouts, and request headers. Seven built-in one-click presets - Safe gateway, OpenAI native, DeepSeek dialect, Qwen dialect, Max thinking, Text only, and Image ready - encode dialect-safe compatibility combinations for the major gateway families, and your current configuration can be saved as a custom preset for later reuse. Persistent advisory checks at the top of the page flag common misconfigurations such as legacy gateways with supportsDeveloperRole left on or reasoning levels missing a wire mapping. Credential-shaped header names are hard-blocked in the editor and stripped before a custom preset is stored, so API keys never leak into settings.yaml. All writes go through the DSH settings service with revision fencing and automatic retry on concurrent edits, the same safety pattern the built-in Models page uses. This plugin installs as a single npm bundle into any DSH profile, registering a host-side settings schema and a Web client Bundle via the DSH module loader so no manual patch editing is required. The UI follows the DSH global language or can be manually pinned to English or Chinese, and the choice persists into settings.yaml rather than only to the browser session. Ideal for teams managing multiple provider routes in DSH who need fine-grained control over thinking depth or must accommodate several gateway dialects without maintaining fragile YAML by hand.