v0.8.0

The release that lets you notice a delegate has gone down. Delegating a namespace hands
the life of the identifiers beneath it to someone else — and arkhe does not know how they
are doing: it answers with a redirect and never fetches the target.

The list to watch was missing the worst failure. /.well-known/ark published delegated
minting but not delegated resolution. When a minter dies, minting stops; when a
redirect dies, every ARK beneath it stops resolving.

arkhe is still not made to probe. Making no outbound calls is what keeps failures easy
to attribute, and that is too expensive to trade away for monitoring — noticing lives
outside, stopping lives inside.

Added

• /.well-known/ark now carries where resolution was delegated (redirect) and each
  shoulder's status.

  It used to list only minter (delegated minting) and about. The failure that hurts
  most was the one missing: when a minter dies, minting for that namespace stops; when
  a redirect dies, every ARK beneath it stops resolving. The first thing to watch
  from outside cannot be watched if it is not published.

  The list no longer filters on status=delegated alone. A redirect can be set
  independently of status, so a shoulder that mints locally but delegates resolution
  was dropping out of the list — and nobody would notice when it failed.

• How to watch a delegate from outside, in
  Deployment.

  arkhe is not made to do the probing. This ledger makes no outbound calls at all
  (even an unknown NAAN just gets a 302; nothing is fetched) — a property that makes
  failures easy to attribute, and too expensive to trade away for monitoring. It
  publishes the list instead.

  Noticing lives outside; stopping — a hold — lives inside.

---

日本語の変更履歴
· Full Changelog: v0.7.0...v0.8.0