Version cut 1.9.3: close the panel-redesign docs prep, bump the pin

CHANGELOG.md audited against the full commit history from the repo's
first commit (8ad56ed) through HEAD: version/date headings, entry
completeness, and technical claims against their diffs all check out,
no discrepancies found.

The Unreleased section (panel-redesign mockups, contract, and
decisions; preflight plan) is docs-only prep — development.md's own
rule would hold the cut until a product stage ships — but the owner
asked for a version cut now, so it becomes 1.9.3 (PATCH) and a fresh
Unreleased opens. Pin bumped in deploy/docker-compose.yml, README's
quickstart, guide.md, and development.md's planned-cuts table, which
also gains the new row (renumbering inbound-antispam-panel to 11).

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

CHANGELOG.md

@@ -5,6 +5,14 @@ Format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/); version
 
 ## [Unreleased]
 
+## [1.9.3] - 2026-09-22
+
+Panel-redesign prep, docs only: stage 1-2 mockups on all 33 screens, the
+accepted header/type-scale/contrast corrections, the account e-mail and
+inbound-delegation decisions, and the routes/quarantine/preflight roadmap
+screens. Nothing in `internal/web` changes; the design stays `candidate`
+(3/21) until the redesign itself ships as `2.0.0`.
+
 ### Added
 
 - Panel redesign, account e-mail and notifications: a user's e-mail is its own

README.md

@@ -112,7 +112,7 @@ docker run --rm -d --name selfpost-try \
   -e SELFPOST_HOSTNAME=mail.local.test \
   -e PANEL_COOKIE_SECURE=false \
   -v selfpost-try-data:/data \
-  ghcr.io/mixeme/selfpost:1.9.2
+  ghcr.io/mixeme/selfpost:1.9.3
 ```
 
 **Get the setup URL** (pick one):

deploy/docker-compose.yml

@@ -21,7 +21,7 @@
 
 services:
   selfpost:
-    image: ghcr.io/mixeme/selfpost:1.9.2
+    image: ghcr.io/mixeme/selfpost:1.9.3
     restart: unless-stopped
     environment:
       SELFPOST_HOSTNAME: "${SELFPOST_HOSTNAME:?set the mail/panel hostname, e.g. mail.example.com}"

docs/development.md

@@ -107,7 +107,7 @@ than the default «meaningful step» rule in [§ Commits and release build](#com
 2. Git tag `vX.Y.Z` and publish the GitHub Release only on explicit request (see
    [§ Release image](#release-image)).
 
-**Planned version cuts** (from pin `1.9.2`; adjust if semver changes mid-track):
+**Planned version cuts** (from pin `1.9.3`; adjust if semver changes mid-track):
 
 | Stage | ID | Cut |
 |---|---|---|
@@ -120,7 +120,8 @@ than the default «meaningful step» rule in [§ Commits and release build](#com
 | 7 | application auth IPs | `1.9.0` |
 | 8 | port-25 Postfix startup fix | `1.9.1` (PATCH) |
 | 9 | 2026-08-19 code review pass | `1.9.2` (PATCH) |
-| 10 | inbound-antispam-panel | `1.10.0` (planned) |
+| 10 | panel-redesign prep (docs only, owner-requested cut) | `1.9.3` (PATCH) |
+| 11 | inbound-antispam-panel | `1.10.0` (planned) |
 
 Docs-only prep (checklists in plans, no product code) uses the same per-step
 commit rule but **no** version cut until the next product stage ships.

docs/guide.md

@@ -173,7 +173,7 @@ cat ./data/setup-token
 #### Fixed image tag
 
 `deploy/docker-compose.yml` pins an explicit version (`ghcr.io/mixeme/selfpost:X.Y.Z`),
-deliberately never `:latest`. The current pin is `1.9.2`. Intermediate
+deliberately never `:latest`. The current pin is `1.9.3`. Intermediate
 CHANGELOG sections (`0.2.0`…`0.6.0`) record development cuts from before that
 image was published. Pinning matters because of the backup version check (see
 [Full backup and restore](#full-backup-and-restore)): the panel binary's