Update Healer Man server

PLAYTEST_NOTES.md

@@ -3639,3 +3639,47 @@ Vite's existing large-chunk advisory remains informational.
   `playtest-artifacts/balance-lab/02-level-batch-config.png`,
   `playtest-artifacts/balance-lab/04-server-job-complete.png`, and
   `playtest-artifacts/balance-lab/06-mobile-analytics.png`.
+
+## Balance Lab parallel watcher isolation (2026-09-19)
+
+- A production all-WoW, every-10-level Stockades batch completed only the level
+  1 and level 80 jobs. Levels 10 through 70 failed during startup before a
+  party ran. Every failed job recorded `ENOSPC: System limit for number of file
+  watchers reached` beneath Vite's watcher stack, while the Balance Lab runtime
+  reported zero active jobs and normal queue capacity after the failures.
+- Each parallel Python worker had launched its own `vite-node` process. The
+  inherited Vite development configuration watched the large shipped public
+  asset tree, so ten simultaneous jobs exhausted the container's Linux watcher
+  allowance. Which two levels completed was a startup resource race, not a
+  class, level, boss, or combat-model failure.
+- The headless bridge now launches with `--mode balance-lab`. That Vite mode
+  sets `publicDir: false` and ignores every watch path, eliminating hot-reload
+  watchers that one-shot simulations do not use. Server job failures also
+  translate the known watcher-limit signature into a specific GM-facing error.
+- The Python controller tests, all 14 Balance Lab service tests, the complete
+  84-test server suite, and the 62-test benchmark/party suite passed. A resolved
+  Vite configuration check returned an empty public directory and
+  `watch.ignored: ["**/*"]`; a real level-10 WoW catalog invocation completed
+  through the new mode and wrote its 72,723-byte catalog. The production build
+  passed, and the authenticated GM smoke flow completed a real server job,
+  loaded its analytics and ability breakdown, and passed desktop/mobile checks.
+
+## Default Git and TrueNAS release path (2026-09-19)
+
+- The visual release manager now starts with **Git + TrueNAS only** enabled.
+  This mode retains the candidate check, content/server/application tests,
+  content publication, production build, staged-file review, commit,
+  remote-main verification, and pinned TrueNAS deployment commands.
+- The default path does not bump package or Android versions, request signing
+  credentials, run Android sync, build an APK, or publish a Gitea release.
+  Clearing the toggle restores the existing full APK workflow; **Publish
+  Current APK Only** remains available for retrying publication from an already
+  versioned and pushed commit.
+- **Run test suites** is independently enabled by default. Clearing it skips
+  only the content, server, normal-application, and shelved-application test
+  commands. The candidate check, content publication, production build,
+  staged review, Git verification, and selected deployment/APK stages remain.
+  Both the log and final staged review identify the skipped suites.
+- All 12 release-manager unit tests and Python compilation passed. The real
+  Windows Tk smoke launch also initialized the default-on mode and closed
+  cleanly.