v0.21.0 — three more engines

Three more coding engines you can install and drive: Kimi Code, Qwen Code, and DeepSeek Code.

moshcode install kimi       # curl -fsSL https://code.kimi.com/kimi-code/install.sh | bash
moshcode install qwen       # npm i -g @qwen-code/qwen-code
moshcode install deepseek   # npm i -g @serjm/deepseek-code

Each one resolves by alias the way every other engine does (qwencode, alibaba, ds, dsc, kimi-code, …), gets its reviewed autonomous-mode flags behind agents, and gets a headless mode behind moshscript's ai():

moshcode agents kimi        # kimi --yolo
moshcode agents qwen        # qwen --approval-mode=yolo
moshcode agents deepseek    # deepseek-code --turbo

Two of those entries route around a bad name:

• kimi installs the kimi-code script directly. The older code.kimi.com/install.sh wrapper now installs the deprecated Python kimi-cli, and it prompts — Enter, or a 30-second timeout, silently redirects to that same script. A vendor installer that blocks on a human for half a minute is not something moshcode install can drive.
• deepseek launches deepseek-code, not the dsc alias its package also installs, because dsc is Microsoft's Desired State Configuration binary. On a machine with both, the short name would silently start the wrong program. DeepSeek publishes no first-party agentic CLI; @serjm/deepseek-code is the live community one, while deepseek-tui is now a stub renamed to codewhale and deepseek-cli has not shipped since January 2025.

template list grew a --json form for automation (#284).

Also fixes a DoH config that dropped its default guards when only one of them was overridden (#285).

Minor, not patch: three new engines and a new output format.

MCP and skills fan-out stay opt-in per engine, so the new engines report "no support" there for now.

Full changelog: #284, #285, #286, #287, #288 — v0.20.0...v0.21.0