Release v0.1.1 2026-07-10

README.md

@@ -38,14 +38,23 @@ state rather than two independent WebViews.
 
 ## TrueNAS deployment
 
+Complete first-install, local-Gitea clone, YAML, update, and verification steps:
+[DEPLOYMENT.md](DEPLOYMENT.md).
+
 The production preview server uses the existing deployment address and port:
 
 - Public URL: `https://iwanttoheal.phenomrom.com`
 - Host/container port: `4173`
-- App directory: `/mnt/usbssds/apps/iwanttoheal/app`
+- App directory: `/mnt/usbssds/apps/iwanttoheal-mmo/app`
 
-Clone the repository into the app directory, then deploy `compose.yaml`. Compared
-with the old game configuration:
+Clone from the TrueNAS-local Gitea bare repository into the app directory, then
+deploy `compose.yaml`. The expected source path is:
+
+```text
+/mnt/.ix-apps/app_mounts/gitea/data/git/repositories/phenom/i-want-to-heal-mmo.git
+```
+
+Compared with the old game configuration:
 
 - use `corepack pnpm install --frozen-lockfile`, not `npm ci`;
 - remove `npm run db:init` because this game has no server database;
@@ -66,11 +75,10 @@ The repository target is:
 https://git.whoagland.com/phenom/i-want-to-heal-mmo.git
 ```
 
-Create a Gitea access token with repository write permission, expose it only for
-the publishing process, then publish from `main`:
+The Mac publisher is configured with the Gitea release token. `GITEA_TOKEN` can
+optionally override it for one run. Publish from `main`:
 
 ```bash
-export GITEA_TOKEN="..."
 pnpm publish:gitea -- --message "Describe the update"
 ```
 
@@ -80,11 +88,11 @@ version tag and Gitea prerelease, and uploads the APK plus its SHA-256 file. It
 uses `package.json` version unless that version is already tagged, then advances
 the patch number. Pass `--version 0.2.0` to choose an explicit version.
 
-If the TrueNAS app directory is mounted locally, publishing also performs a
-fast-forward-only pull. Otherwise it prints the clone/pull command to run on
-TrueNAS before restarting the app. The pull refuses to run when the TrueNAS
-checkout still points at the old game's repository; move or archive that checkout
-and clone the new repository first.
+If the publisher runs where TrueNAS paths are visible, it prefers a
+fast-forward-only pull directly from TrueNAS-local Gitea storage. Otherwise it
+prints the exact local clone/pull commands to run in the TrueNAS shell. The pull
+refuses to run when the checkout still points at the old game's repository;
+archive that checkout and clone the new repository first.
 
 Preview checks without changing Git or TrueNAS:
 
@@ -92,9 +100,9 @@ Preview checks without changing Git or TrueNAS:
 pnpm publish:gitea -- --dry-run
 ```
 
-Git push credentials still come from Git's credential manager. Gitea release API
-credentials come from `GITEA_TOKEN`. Never store access tokens or Android signing
-keys in this repository.
+Git push credentials still come from Git's credential manager. The configured
+Gitea token handles release creation and APK uploads. Android signing keys remain
+outside the repository.
 
 ## Controls