Update game 1.0.27

DEPLOYMENT.md

@@ -138,9 +138,12 @@ services:
 
 The app listens inside Docker on port `4173`. The database lives at
 `/mnt/usbssds/apps/iwanttoheal/data/game.db` because that host directory is
-mounted into the container as `/app/data`. The startup command installs
-dependencies, applies schema migrations, builds the web app, and starts the
-production server.
+mounted into the container as `/app/data`. This is persistent runtime data, not
+code. Do not commit it and do not copy the Mac `data/game.db` over it during
+deploys.
+
+The startup command installs dependencies, applies schema/static-content
+updates, builds the web app, and starts the production server.
 
 Test the local TrueNAS service:
 
@@ -220,11 +223,22 @@ cd /mnt/usbssds/apps/iwanttoheal/app
 git pull
 ```
 
+Before restarting, back up the persistent database:
+
+```sh
+cp /mnt/usbssds/apps/iwanttoheal/data/game.db \
+  "/mnt/usbssds/apps/iwanttoheal/data/game-before-update-$(date +%Y%m%d-%H%M%S).db"
+```
+
 Restart the `iwanttoheal` app in the TrueNAS Apps UI after pulling. The app
 command runs `npm ci`, `npm run db:init`, `npm run build`, and `npm start` on
 startup, so dependency, schema, and browser bundle changes are applied each time
 the container restarts.
 
+`npm run db:init` updates schema and seeded static game content. It should not
+erase accounts, characters, inventory, or save progress. Character resets are
+separate manual operations and should only be run intentionally.
+
 Normal update workflow:
 
 ```sh
@@ -236,10 +250,14 @@ git push origin main
 # TrueNAS shell
 cd /mnt/usbssds/apps/iwanttoheal/app
 git pull
+cp /mnt/usbssds/apps/iwanttoheal/data/game.db \
+  "/mnt/usbssds/apps/iwanttoheal/data/game-before-update-$(date +%Y%m%d-%H%M%S).db"
 ```
 
 Then restart the TrueNAS app.
 
+For the shorter checklist, see [docs/push-updates.md](docs/push-updates.md).
+
 ### Existing auth-only app
 
 If `iwanttoheal-auth` was already created during earlier testing, the simplest