Release Healer Man 0.1.56

docs/BALANCE_LAB.md

@@ -56,15 +56,18 @@ use the live companion AI. The healer is the default active member. Use
 
 A server-authorized GM sees **Balance Lab** directly underneath **GM Tools** on
 the main menu. That screen exposes the automatic sweep controls: party source,
-level, class/spec selection strategy, a searchable spec picker, simulations per
-party/boss, duration, random seed, boss category, and a searchable multi-boss
-picker. Random mode exposes the requested parties per source; coverage modes
-show the derived minimum party count before submission.
+a single level or an all-brackets schedule, class/spec selection strategy, a
+searchable spec picker, simulations per party/boss, duration, random seed, boss
+category, and a searchable multi-boss picker. The bracket schedules cover level
+1 plus every 10 levels, level 1 plus every 5 levels, or every level from 1
+through 80. Random mode exposes the requested parties per source; coverage
+modes show the derived minimum party count before submission.
 
-**Run on server** sends only that allow-listed configuration to the authenticated
-GM API. The server places it in a one-at-a-time queue, launches the same Python
-controller and live TypeScript runtime used by the command line, and writes
-artifacts under:
+**Run on server** sends one allow-listed configuration to the authenticated GM
+API. **Run all level brackets** submits the complete schedule atomically and
+creates one independently persisted job and report per level. The bounded worker
+pool runs several jobs at the same time, launches the same Python controller and
+live TypeScript runtime used by the command line, and writes artifacts under:
 
 ```text
 DATA_DIR/balance-lab/jobs/<job-id>/
@@ -139,10 +142,12 @@ command installs `python3`, prints `python3 --version` during startup, and sets
 `BALANCE_LAB_PYTHON=python3`; use the exact YAML in `DEPLOYMENT.md` rather than
 the older Node-only command.
 
-`BALANCE_LAB_MAX_CONCURRENT` defaults to `1` and is capped at four.
-`BALANCE_LAB_MAX_QUEUED` defaults to eight and is capped at 50. Raising
-concurrency permits parallel server processes but can make both the game server
-and simulations less responsive. Requests are capped before launch, subprocess
+`BALANCE_LAB_MAX_CONCURRENT` defaults to four and is capped at 16.
+`BALANCE_LAB_MAX_QUEUED` defaults to 100 and is capped at 200, which leaves room
+for an 80-job every-level sweep. Raising concurrency permits more parallel
+server processes but can make both the game server and simulations less
+responsive. A batch contains at most 80 jobs and is validated against the
+remaining queue capacity before any of its jobs are created. Subprocess
 arguments are passed as an array without a shell, artifact names are
 allow-listed, and every job and artifact endpoint authenticates the account's
 server-issued GM role.
@@ -372,9 +377,10 @@ combat tick while retaining their own attack cadence.
   cards, and complete boss/class-spec/party tables. Add new dashboard metrics
   here only after they exist in `suite-report.json`.
 - `src/app/balanceLabClient.ts`: typed GM Balance Lab API client.
-- `server/balance-lab-jobs.mjs`: validated job specifications, bounded
-  one-at-a-time process queue, progress parsing, `job.json` persistence/startup
-  restoration, report-summary extraction, and artifact allow-list.
+- `server/balance-lab-jobs.mjs`: validated single and batch job specifications,
+  bounded parallel process queue, progress parsing, `job.json`
+  persistence/startup restoration, report-summary extraction, and artifact
+  allow-list.
 - `server/server.mjs`: GM-authenticated runtime-preflight, job, status, and
   artifact HTTP routes.
 - `src/game/benchmark/benchmarkBuilds.ts`: selectable spec builds and legal