chore(release): v0.16.0 (#199)

install.sh resolves releases/latest, so the twelve commits merged since
v0.15.0 have been unreachable to anyone running `moshcode update` —
including the reason `curl <name>` still did not work after enabling DNS.

The headline is that routing stopped being a list. `dns install` wrote
every claimed ending onto one `Domains=` line; systemd-resolved caps how
many search domains it accepts, took 1090 of 4586 alphabetically,
rejected the rest one journal line at a time with "Argument list too
long", and reported success. Names past the cut were configured on disk
and absent from the resolver, so `moshcode dns resolve` answered while
`curl` could not — with nothing in between to say why, and every new
ending making the cut deeper.

`Domains=~.` is one entry that never grows. The bridge now forwards
anything that is not a claimed ending upstream, byte for byte, and fails
open in every direction: an unknown ending set means "not ours", silent
upstreams are SERVFAIL rather than NXDOMAIN, and loopback nameservers are
dropped so it cannot forward to itself.

Also in this release:

  - a name can be served at an IPv6 address end to end — the bridge
    answers AAAA, and an A query for a v6-only name is NODATA rather
    than NXDOMAIN, which was denying the name for the whole page load
  - `moshcode template` scaffolds a Moshpit-hosted service, with
    bun-caddy-sqlite and caddy-static bundled
  - names and endings are letters and digits only; a dash was the
    cheapest way to mint a look-alike of an ending someone else holds
  - an ending has its own page at /n/<ending>, with its pointers and
    relatives rather than a dead end

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

Author: ralyodio

package.json

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