v0.62.0 — same code, fresh release

No code changes. v0.62.0 is identical to v0.61.0 — the only difference is the
version in package.json. It was cut so there is a fresh release and a fresh npm
publish to update from.

If you are upgrading to chase a DNS problem, this is worth knowing up front: it
does not contain a fix for one. moshcode dns enable, the bridge, and the
resolver logic are all unchanged from v0.61.0.

Two things worth recording from the session that produced this release, neither of
which required a code change:

• The bridge parks unpointed names correctly. A name that is claimed but has
  no target — scrambled.eggs is the one the docs use — resolves to the parking
  address (69.46.46.103), not NXDOMAIN. So curl http://scrambled.eggs failing
  with "Could not resolve host" is not the bridge; it means the system resolver
  never asked the bridge, which points at the routing step, not the daemon.
• dns start takes a few seconds to bind. It fetches the full ending list
  (17,848 of them) before it opens the socket, so a query fired immediately after
  launch gets connection-refused from a process that is working fine. dns enable
  already accounts for this by probing until the bridge answers.