dsh-updater

DeepSeek Harness ships often but has no self-update built in. After installing the npm package you still have to restart it manually, and the restart command must match the original invocation exactly—port, profile, working directory, Node path—any mismatch breaks things. Worse, a single machine often holds more than one DSH install, and a bare npm install -g may update the one last on PATH while the one actually running stays untouched.\n\ndsh-updater chains the whole lifecycle into one pipeline: check version, read the changelog, grade the risk, install, verify, relaunch, and roll back on failure. It tracks the latest / next / alpha npm dist-tags alongside GitHub Releases, renders the bilingual release notes for every version between your current build and the target, and produces a graded risk report covering breaking-change keywords, migration hints, multi-install conflicts, plugin engine compatibility, and a full set of preflight checks (disk space, writable install root, Node version, tarball reachability, and more). High-severity findings block the one-click path until you explicitly acknowledge them. The actual install is handled by a detached helper that atomically renames the current install out of the way, runs npm install with an explicit prefix, verifies the landed tree package by package, relaunches DSH with the exact same arguments and working directory, and renames the backup back if the new build fails to boot.\n\nIt is designed for anyone who keeps a long-running DSH instance on a dev box or server, experiments across multiple release channels, or deals with a machine where several installs coexist and the PATH winner is not obvious. It does not replace DSH; it makes the "click to update" moment predictable, auditable, and reversible.