Update Healer Man server

RELEASE_RUNBOOK.md

@@ -11,20 +11,34 @@ On the development PC, double-click `scripts\release-manager.cmd` or run:
 npm run release:gui
 ```
 
-The release manager suggests the next semantic patch version and a strictly
-increasing Android `versionCode`, runs the complete validation suite, and
-stages the release. It then shows the exact staged paths and diff summary for
-approval before it commits, pushes `main`, builds the signed APK, and publishes
-the Gitea release. Signing passwords and the Gitea token are passed to the
-child process in memory rather than on its command line.
+The release manager opens with **Git + TrueNAS only** enabled. In this default
+mode it runs the server validation and production build, shows the exact staged
+paths and diff summary for approval, commits, pushes `main`, and pins the
+TrueNAS **Deploy** tab to the new commit. It does not change `package.json` or
+`release-version.json`, run Android sync, read signing credentials, build an
+APK, or create a Gitea APK release.
+
+Clear **Git + TrueNAS only** when the update also needs a new Android release.
+APK mode suggests the next semantic version and a strictly increasing Android
+`versionCode`, then performs Android sync and publishes the signed APK after the
+Git push. Signing passwords and the Gitea token are passed to the child process
+in memory rather than on its command line.
+
+**Run test suites** is also enabled by default. Clear it for a narrowly scoped
+update that does not need the content, server, normal-application, or
+shelved-application test suites. The manager records the skip in its log and
+staged-review dialog. This toggle does not skip the isolated release-candidate
+check, content publication, production build, staged whitespace/secret review,
+Git push verification, or any Android stages selected by APK mode.
 
 If a content, server, normal-application, or shelved-application test command
 fails, the visual manager pauses with the failed command, exit code, and recent
 test output. **Stop Release** remains the safe default, but **Continue Anyway**
 allows an intentional override and records that decision in the release log.
 Build, content-publication, Git, signing, and APK-publication failures are not
-overridable and still stop the workflow. The manual procedure below remains
-fail-closed.
+overridable and still stop the workflow. Android sync, signing, and APK
+publication are omitted entirely in Git + TrueNAS mode. The manual procedure
+below remains fail-closed.
 
 Before changing versions or running the longer test/build sequence, the manager
 runs an isolated release-candidate check. It validates tracked and untracked