chore(release): v0.16.5 (#218)

`moshcode update` now checks before it installs.

  moshcode update --check              is there a newer release?
  moshcode update --if-newer           install only if there is
  moshcode update --timer [--install]  check on a schedule, 15min default

Until now every run re-fetched Node, bun and the release tarball whether
or not anything had changed — fine as a thing you type, wrong as a thing
a timer runs every fifteen minutes.

Versions compare in order rather than by string inequality, so a rolled
back release does not read as an upgrade and 0.9.0 does not read as newer
than 0.10.0. An unreachable feed means do nothing, because a timer that
reinstalls on every failed check hammers a machine that is merely offline.
The timer sets Persistent=true so a sleeping laptop checks on waking, and
runs the checking form rather than a bare update.

Automatic updates hand a bad release to every machine on the timer within
the interval, with nobody in the loop — which is worth knowing before
enabling the installing form rather than the checking one.

Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>

Author: ralyodio

package.json

@@ -1,6 +1,6 @@
 {
   "name": "moshcode",
-  "version": "0.16.4",
+  "version": "0.16.5",
   "type": "module",
   "description": "moshcode — a metal wrapper for coding engines and native UGig/CoinPay workflow CLIs, with OpenPRD and moshscript",
   "bin": {