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

backend/app/api/admin.py

@@ -0,0 +1,56 @@
+"""Instance administration (SPEC §6.1).
+
+The backend seam for the admin panel. Today it carries only the registration
+gate — the first account on a fresh install becomes the administrator and closes
+signup behind itself, and this is how that gets reopened. Further instance-wide
+options land here as the panel grows.
+"""
+
+from __future__ import annotations
+
+import datetime as dt
+from typing import Annotated
+
+from fastapi import APIRouter, Depends
+from sqlalchemy.ext.asyncio import AsyncSession
+
+from app.db import get_session
+from app.identity.deps import CurrentAdmin, require_csrf
+from app.identity.schemas import AdminSettingsIn, AdminSettingsOut
+from app.identity.service import app_settings
+from app.models import AppSettings
+
+router = APIRouter(prefix="/admin", tags=["admin"])
+
+DbSession = Annotated[AsyncSession, Depends(get_session)]
+
+
+def _out(row: AppSettings) -> AdminSettingsOut:
+    return AdminSettingsOut(
+        registration_open=row.registration_open,
+        default_quota_bytes=row.default_quota_bytes,
+    )
+
+
+@router.get("/settings", response_model=AdminSettingsOut)
+async def read_settings(admin: CurrentAdmin, db: DbSession) -> AdminSettingsOut:
+    return _out(await app_settings(db))
+
+
+@router.put("/settings", response_model=AdminSettingsOut, dependencies=[Depends(require_csrf)])
+async def write_settings(
+    body: AdminSettingsIn, admin: CurrentAdmin, db: DbSession
+) -> AdminSettingsOut:
+    """Merge the supplied fields into the settings row.
+
+    Changing ``default_quota_bytes`` affects users created afterwards only —
+    nothing here rewrites an existing ``users.quota_bytes``.
+    """
+    row = await app_settings(db, for_update=True)
+    if body.registration_open is not None:
+        row.registration_open = body.registration_open
+    if body.default_quota_bytes is not None:
+        row.default_quota_bytes = body.default_quota_bytes
+    row.updated_at = dt.datetime.now(dt.UTC)
+    await db.commit()
+    return _out(row)