Why: A squad run was one file workspace, and leader delegation depended on a JSON file the model had to emit.
Evidence: GOWORK=off go test -count=1 -timeout 180s ./...
Impact: The goal engine and /v1/runs stay. Orchestration routes mount when the database opens. SSE for a run id skips other runs. External CLIs are not a sandbox.
Refs: feature/orchestration-platform
Why: A squad run was one file workspace, and leader delegation depended on a JSON file the model had to emit.
Evidence: GOWORK=off go test -count=1 -timeout 180s ./...
Impact: The goal engine and /v1/runs stay. Orchestration routes mount when the database opens. SSE for a run id skips other runs. External CLIs are not a sandbox.
Refs: feature/orchestration-platform
Why: Squad runs were one file workspace and one JSON file the leader had to emit, so agents, issues, and retries had no durable queue.
Evidence: GOWORK=off go test -count=1 -timeout 180s ./...
Impact: /v1/runs stays. New routes mount only when the orchestration database opens. SSE for a run id now skips other runs. External CLIs are not a sandbox.
Refs: feature/orchestration-platform S1-S7
Co-authored-by: Cursor <cursoragent@cursor.com>
weichen
merged commit 40f7db9c61 into main2026-10-01 10:31:04 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Why: A squad run was one file workspace, and leader delegation depended on a JSON file the model had to emit.
Evidence: GOWORK=off go test -count=1 -timeout 180s ./...
Impact: The goal engine and /v1/runs stay. Orchestration routes mount when the database opens. SSE for a run id skips other runs. External CLIs are not a sandbox.
Refs: feature/orchestration-platform