v0.103.0 — MiMo Code joins the engines

A new engine, and one name that finally works everywhere.

MiMo Code. Xiaomi's agentic coding CLI joins the engine table. moshcode install mimocode runs the vendor's installer from mimo.xiaomi.com, which drops a binary called mimo in ~/.mimocode/bin; moshcode looks there itself, so the engine shows as installed in the very session that installed it, before your shell rc has been re-read. moshcode agents mimocode starts it autonomous, moshcode start mimocode starts it plain, moshcode upgrade mimocode hands off to its own updater, and ai() in moshscript can drive it headless through mimo run. It resumes with --continue after a reboot like opencode does, because it is an opencode derivative underneath.

Two dialogs are worth knowing about, both verified on 0.1.14. A fresh directory opens on a workspace trust check, which agent mode skips with --trust. The permissions bypass then puts up a warning of its own on every launch, defaulting to "No, exit", and no flag turns it off. A swarm answers it for you; the herd reads it as blocked rather than idle; at a keyboard you answer it once. Cost reporting does not cover it yet, because it keeps its sessions in a sqlite database rather than the JSON layout the opencode reader knows, so its rows show no cost rather than zero.

Aliases install too. /agents mimo, /start cc and moshcode upgrade cc have always taken an engine's alias, but /install mimo and moshcode install cc looked the word up as a raw key and answered "unknown engine". One resolver now backs the pit's /install and the CLI's install and uninstall, so the name that starts an engine is also the name that installs it. mimo, mimo-code and xiaomi all reach mimocode.