Release: weekly deploy

Documentation/deploy-dev-to-prod.md

@@ -34,13 +34,11 @@ For a typical weekly release, use the orchestrator instead of running each step
    - `autoStartDevStack`: `true` starts `dev:server` (or `dev:web`) automatically when `validateBuild` finds API down
    - `git.message`, `git.branch` — used when `gitCommitPush` is enabled
    - `schemaChanged`: `true` enables prod schema migration on `full` profile
-   - `release.imageTag`: image/version tag shared between Gitea push and runtime (`latest`, `2026-07-09`, `v1.3.0`, etc.)
    - `smb.user` / `smb.password` — optional; maps `\\host\share` before image sync
    - `backupFile` — optional fixed path; otherwise uses the newest `gallery_dev_data_*.txt` after backup
 
 3. Prerequisites still apply: **`npm run dev:web` running** (Vite `:5173` + API `:3451`), Docker Desktop running, `docker login gitea.mysuperlab.netcraze.pro`, [`infra/docker/.env.prod`](../infra/docker/.env.prod) present.
    - Before migration/restore steps, verify prod DB target in `.env.prod`: `DB_NAME=gallery_prod`.
-   - Set `IMAGE_TAG=<release.imageTag>` in prod env (TrueNAS app vars or `.env.prod`) to control which pushed Gitea image tag is active.
 
 ### Run
 
@@ -68,7 +66,7 @@ npm run devtoprod:release -- -DryRun
 | `migrateProdSchema` | Step 4 — `dev:migrate` on `gallery_prod` |
 | `restoreProd` | Step 5 — `devtoprod:db:restore` |
 | `syncImages` | Step 6 — `devtoprod:images` |
-| `dockerPublish` | Step 7 — `prod:docker:publish -- -Tag <release.imageTag>` |
+| `dockerPublish` | Step 7 — `prod:docker:publish` (auto tag: `YYYYMMDD-HHMMSS-<gitsha>` + push `latest`) |
 | `truenasRestartPause` | Step 8 — **manual** pause; script waits for Enter after you restart **gallery-web** |
 | `verify` | Step 9 — curl LAN + public `/api/bounds` |