Admin panel on its own port, and a registration gate

Three strands that only make sense together, so they land together.

Registration gate (migration 0016). POST /auth/register was open to anyone
who could reach the port. Now the first account on an empty instance is
always allowed, becomes the administrator, and closes registration behind
itself; after that it takes an admin reopening it. The decision is made
under a row lock on app_settings so two simultaneous first signups cannot
both see an empty table and both claim administrator. Existing installs
keep their oldest account as admin and start closed.

Instance default quota (migration 0017). users.quota_bytes is snapshotted
at creation from app_settings.default_quota_bytes, so changing the default
affects later accounts only and never resizes a mailbox that exists.

The panel is a separate app, not a page in the mail client. admin.html is
its own Vite entry (5.8 KB next to the client's 1.7 MB; they share only the
vendor chunk), with its own administrator sign-in. One nginx now serves two
listeners: :80 is the mail client and 404s both /admin.html and
/api/admin/*, :81 is the panel. docker-compose publishes them as WEB_PORT
and ADMIN_PORT. The boundary is nginx refusing paths on one listener, not
process isolation — CurrentAdmin still guards every admin route — so
ADMIN_PORT must be restricted to the LAN, which the runbook now covers for
both DSM and QNAP.

Also QNAP: deploy/webmail.sh finds Container Station's docker under
/share/*/.qpkg/container-station/bin, which is off an SSH session's PATH,
before anything shells out to it. docs/nas-install.md gains a QuTS hero
runbook (§2.6), splits the DSM firewall section into container-to-container
(§8.1) and the egress case that makes account-add time out while
autodiscovery appears to work (§8.2), and scopes both to Synology.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_018SqJYt7jD7oUEkoY68sBZo

docker/.env.prod.example

@@ -31,10 +31,19 @@ POSTGRES_PASSWORD=
 APP_DOMAIN=mail.home.lan
 
 # --- Network ----------------------------------------------------------------
-# The single published port. Avoid 5000/5001 (Synology DSM) and 8080 (QNAP QTS).
+# Two published ports, same container. Avoid 5000/5001 (Synology DSM) and
+# 8080 (QNAP QTS).
+#
+# WEB_PORT is the mail app. The admin API is refused on it, so this is the one
+# you may expose beyond the LAN.
 WEB_PORT=8088
+# ADMIN_PORT is the same app with the admin API reachable. Restrict it to your
+# LAN in the NAS firewall — see docs/nas-install.md §5.1. Publishing it is not
+# what protects it.
+ADMIN_PORT=8089
 # Bind to one NAS interface instead of every network, e.g. WEB_BIND=192.168.1.185
 WEB_BIND=0.0.0.0
+ADMIN_BIND=0.0.0.0
 
 TZ=Europe/Warsaw