v2.47.3

Corrects a defect in 2.47.2's own migration — the mechanism that carries 2.47.2's
fix to servers that are already running.

Fixed

• The /assets/ migration could skip the vhost it was meant to repair. After
  rewriting the block it verified its work by searching the whole file for the
  expires directive, on the reasoning that the directive should be gone. But
  expires can legitimately appear in another location block — a hand-added
  /media/, for instance — and the check cannot tell which block it came from.
  On such a server the verification fails, the rewrite is discarded, and the
  updater reports failed to rewrite the /assets/ block — skipped.

  The check now reads only the block it just wrote. The failure was already in
  the safe direction — nothing is changed and the skip is logged, so no server
  was left with a broken configuration — and a vhost generated by the installer
  has no other expires, so reaching it took a hand-edited file. It is corrected
  because a fix that silently does not arrive is the failure this release series
  exists to address.

Added

• Eight further assertions in tests/nginx-headers-pin-e2e.sh covering the two
  server populations the suite had not: one already running 2.47.1, where the
  document block exists and must be neither skipped nor duplicated, and one with
  expires in an unrelated location. Both had been checked by hand, which is
  precisely the state this project keeps finding does not hold.

---

Install: curl -sL dockpanel.dev/install.sh | bash

Every release is installed on a throwaway VPS and driven as a user before
it ships. What that means, and what it has found, is written up at
https://docs.dockpanel.dev/testing.html.

Binaries are static musl builds signed with Sigstore; checksums.txt
and the .sig/.pem pairs are attached below.

Full changelog: v2.47.2...v2.47.3