Keep prod users local and fix post-restore id sequences.

Prod restore skips users/session/audit, syncs serial sequences after load, and user create re-aligns users_id_seq so new accounts are not misreported as duplicates.

Co-authored-by: Cursor <cursoragent@cursor.com>

Documentation/deploy-dev-to-prod.md

@@ -244,10 +244,11 @@ The restore loads rows in two ways automatically:
 
 Multi-line values (e.g. artist bios with embedded newlines) are parsed as whole statements, so long text restores correctly.
 
-**Caveats — prod tables are replaced by dev's contents:**
+**Caveats — prod catalog tables are replaced by dev's contents:**
 
-- `users` is overwritten. The **dev curator account and password become the prod login**. `curator_audit_log` is **not** synced — prod keeps its existing audit history.
-- The `session` table is truncated, so any active prod curator sessions are logged out.
+- **`users`**, **`session`**, and **`curator_audit_log`** are **not** truncated or loaded from the backup. Prod staff accounts, passwords, active sessions, and audit history stay as they are on `gallery_prod`.
+- Catalog / content tables (`artists`, `paintings`, tours, translations, etc.) are fully replaced by the dev dump.
+- After load, serial sequences are reset to `MAX(id)` so new rows (including staff users) do not collide with restored ids.
 - The target is guarded: the restore refuses to run unless the database name ends with `_prod` and only reads `infra/docker/.env.prod`.
 
 > **Optional** — to use the faster single-pass load, have the postgres superuser run this once in pgAdmin (role-global, covers dev and prod): `GRANT SET ON PARAMETER session_replication_role TO gallery;`