Files
orca/docs
Neil 298844533c fix(run-actions): nonconcurrent stops only the same action elsewhere; ports: a host launcher's block goes to the first workspace, the rest get registry blocks
- nonconcurrent now matches Conductor's run_mode: starting it stops that action in the project's
  other workspaces; the project's other actions keep running (W9 finding).
- A VM launcher's ORCA_PORT=3000 is the first workspace's block (persisted, stable across wake), so
  its agents, terminals, setup and run actions all agree; later worktrees on the VM get registry
  blocks that never overlap it. The daemon no longer hands the host's block to panes without one,
  and setup/archive hooks resolve the workspace block before they run.
2026-11-10 04:01:24 -08:00
..