release: 2.10.3: backup-reauth - the account password before a backup

Cut without asking, as the owner said on 2026-10-15. The full backup and a
domain's export ask for the signed-in user's account password under the
password change's limit; the import's file field is drawn as designed
(1888dce design, the code commit before this). go vet, go test (26
packages) and make e2e passed on the test server for that tree. No
migration, schema 12.

CHANGELOG [2.10.3]; pins in deploy/docker-compose.yml, README and the guide
(pin, build, the sample restore message); development's "from pin" and
row 35; roadmap row. No tag.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

docs/guide.md

@@ -204,14 +204,14 @@ 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 `2.10.2`. **No 2.x image is
+deliberately never `:latest`. The current pin is `2.10.3`. **No 2.x image is
 published on ghcr.io yet** (the newest there is `1.3.0`); until one is, build
 it from the checkout under the pinned name, and Compose uses the local image
 instead of pulling:
 
 ```sh
-docker build -f build/Dockerfile --build-arg VERSION=2.10.2 \
-  -t ghcr.io/mixeme/selfpost:2.10.2 .
+docker build -f build/Dockerfile --build-arg VERSION=2.10.3 \
+  -t ghcr.io/mixeme/selfpost:2.10.3 .
 ```
 
 `VERSION` must equal the tag: it is the version the backup check compares
@@ -950,7 +950,7 @@ A version mismatch at step 5 refuses to start and leaves `/data` untouched —
 the panel exits with a message naming the tag to use, e.g.:
 
 ```
-backup: this backup was created by SelfPost 2.10.1 but this image is 2.10.2 — restore into the matching image (selfpost:2.10.1)
+backup: this backup was created by SelfPost 2.10.2 but this image is 2.10.3 — restore into the matching image (selfpost:2.10.2)
 ```
 
 Fix the tag in `docker-compose.yml` (build that tag as under [Fixed image