v0.57.0

Worktrees now execute a project-specific dependency install command before builds, ensuring coders have the correct dependencies and preventing filesystem-wide searches.

Worktree Configuration

• A new setup_cmd setting installs a project's own dependencies into every fresh worktree (e.g., npm ci --prefer-offline), instead of the tree borrowing the repo checkout's node_modules, which may be stale or missing.
• The command runs in the card tree, Max-Mode candidates, ladder candidates, test-rung candidates, and the merged-state verify tree before the gate runs.
• Existing node_modules symlinks are unlinked before installation so writes stay within the tree and never modify the shared checkout.
• Installation is off by default and configured via YAML per project or board-wide.

Reliability and Isolation

• The install process runs in its own process group with no stdin and an allowlisted environment, matching the gate child contract.
• The entire process tree is killed and reaped if the install exceeds setup_timeout_s (default 600 seconds).
• Failed or hung installs are logged and the build proceeds, ensuring best-effort behavior even for unanticipated spawn errors.