Release Healer Man 0.1.14

DEPLOYMENT.md

@@ -24,8 +24,9 @@ container, rebuilding `dist`, or pulling source must not replace the database.
 TrueNAS Gitea stores the source repository and APK release attachments; it is
 not the game database.
 
-Large runtime assets are published separately under `/app/content`. Android
-clients download verified content objects from `/content` and retain them in
+Large runtime assets are published separately under `/app/content`. Production
+browser and Android clients download verified content objects from `/content`;
+browsers retain them in an app-managed cache and Android retains them in
 app-private storage for offline play. See `CONTENT_UPDATES.md` for the manifest,
 atomic activation, compatibility, and rollback contract.
 
@@ -55,9 +56,10 @@ Container/host port:
 ```
 
 The Gitea bare repository is not runnable. Clone it with Git; never copy it
-with `cp`. The checkout contains several gigabytes of required GLB assets, so
-the initial clone and first build will take substantially longer than later
-fast-forward updates.
+with `cp`. The checkout contains several gigabytes of content-source GLB assets,
+so the initial clone and first content publication will take substantially
+longer than later fast-forward updates. Production browser and Android bundles
+stage only their compact required-content subset.
 
 Do not turn the GLBs into Git LFS pointers without also changing this deployment
 procedure. Gitea keeps LFS objects outside the bare repository, so a bare-path
@@ -80,7 +82,8 @@ git branch --show-current
 
 If the repository slug differs, change both the remote URL here and every
 `healer-man.git` bare-repository path below. Do not commit `.env` files,
-keystores, API tokens, `content`, `dist`, `dist-android`, or `.android-public`.
+keystores, API tokens, `content`, `dist`, `dist-android`, `.web-public`, or
+`.android-public`.
 
 On TrueNAS, confirm the bare repository path. If the first command fails, use
 the search command:
@@ -154,8 +157,9 @@ account/cloud-save data; `/app/content` owns downloadable manifests and
 immutable content objects. Never mount a volume at `/app/data`, because that
 would hide the checkout's required `/app/data/loot/schema.sql`. The
 startup command installs locked dependencies, initializes the schema, publishes
-new or changed content objects, builds the full browser bundle, and starts the
-combined static/API/content server. Existing content objects are reused.
+new or changed content objects, builds the compact required-content browser
+bundle, and starts the combined static/API/content server. Existing content
+objects are reused.
 
 After startup, test on the LAN:
 
@@ -220,8 +224,8 @@ git rev-parse HEAD
 
 Before `git commit`, read the staged file list printed by `git status --short`.
 Do not commit a `.env` file, password, API token, keystore, APK, database,
-`content/`, `dist/`, `dist-android/`, or `.android-public/` output. The final
-command prints the exact deployed commit ID.
+`content/`, `dist/`, `dist-android/`, `.web-public/`, or `.android-public/`
+output. The final command prints the exact deployed commit ID.
 
 Next, open the TrueNAS Apps UI and **stop** `healer-man`. Open a TrueNAS shell
 and run these exact commands:
@@ -247,11 +251,12 @@ sudo git -C /mnt/usbssds/apps/healer-man/app rev-parse HEAD
 The TrueNAS commit ID must match the one printed on the development PC. Start
 `healer-man` in the TrueNAS Apps UI afterward. Container startup
 publishes immutable content objects and replaces `manifest.json` only after all
-objects exist, then rebuilds the browser client and starts the server. Android
-devices discover the small new manifest and download only missing or changed
-files. Asset-only updates do not require a new APK. A failed fast-forward pull
-deliberately leaves the running checkout unchanged; resolve diverged history on
-the development machine rather than forcing the TrueNAS checkout.
+objects exist, then rebuilds the browser client and starts the server. Browser
+and Android clients discover the small new manifest and download only missing
+or changed files for packs the player installed. Asset-only updates do not
+require a new APK. A failed fast-forward pull deliberately leaves the running
+checkout unchanged; resolve diverged history on the development machine rather
+than forcing the TrueNAS checkout.
 
 After the logs say the server is listening on port `4173`, run on TrueNAS:
 
@@ -286,9 +291,10 @@ copies; it does not replace dataset-level protection.
 ## APK releases and Obtainium
 
 Keep APK binaries out of the Git branch. The Android build uses `dist-android`,
-which contains the game runtime, UI, equipment, and Wailing Caverns starter
-content rather than the full multi-gigabyte browser catalog. Downloaded packs
-survive APK updates.
+which contains the game runtime, UI, starter equipment, basic Human character,
+and Wailing Caverns starter content. Optional character/skin packs, original
+spell media, dungeons, and other large content remain outside the APK.
+Downloaded packs survive APK updates.
 
 Install JDK 21 and Android SDK Platform 36 on the development PC and set
 `JAVA_HOME` plus `ANDROID_SDK_ROOT`. The build wrapper also recognizes the