@brainbase-labs/cli 0.24.0 → 0.25.0-eng1209.10

package/README.md

@@ -72,21 +72,28 @@ synchronously. Schema v1 supports:
 - `workspace_assertion`: file existence, absence, SHA-256, or content checks.
 - `sandbox_command`: a bounded argv command rooted in the workspace or hidden
   tests directory. Exit zero passes; any other exit code is a valid failed
-  verdict. Schema v1 allows one command evaluator and runs it after all
-  read-only assertions so evaluator mutations cannot change candidate verdicts.
+  verdict. Schema v1 allows up to 20 command evaluators and runs them after all
+  read-only assertions. Each command receives either the verified live workspace
+  for legacy read-only evaluation or its own isolated frozen workspace copy.
 
 Valid failed verdicts still produce a successful evaluation phase. Invalid
-specs, digest/path violations, missing environment, launch failures, timeouts,
-and output-budget violations fail the phase. Results are written atomically
+specs, digest/path violations, missing environment, phase-budget exhaustion,
+and output-budget violations fail the phase. Individual command launch failures,
+timeouts, and forced terminations are recorded as errored evaluator results so
+the remaining evaluators can still run. Results are written atomically
 with mode `0600`, include the raw spec digest and checksummed evidence/log
 input/output references with explicit `staging`, `workspace`, `tests`, or
 `logs` roots, redact declared secret values from command logs, require the
 result path to be `<logs_root>/result.json`, and treat a matching successful
 phase result as authoritative on replay.
 
-On any phase-level execution failure, MAS must tear down the task sandbox. The
-CLI kills the command process group and descendants it can observe, but the
-runtime lifecycle remains the final cleanup boundary for daemonized processes.
+On any phase-level execution failure, MAS must tear down the task sandbox.
+Failed and timed-out commands clean up the process group and descendants the
+CLI can observe. Successful evaluator commands receive the same cleanup so one
+check cannot contaminate the next. Successful hydration setup commands may
+intentionally leave services running for the agent turn; the runtime lifecycle
+remains their final cleanup boundary. Isolated evaluator workspace copies omit
+`.git` and unsafe absolute or escaping symlinks.
 
 ## Development