swarm-orchestratelisted

# swarm-orchestrate — optional local autonomy **Gate:** this add-on is disabled by default. Do not enable it, configure write access, or start workers unless the user explicitly asks. Tickets and atomic claims remain the source of truth; signals and controls never override a healthy claim. ## What this is for (read before configuring anything) The goal is **the right model on the right task, at the lowest token cost** — parallelism is only one means to that end, and often not the right one. So orchestration has two separate decisions, and conflating them is the classic mistake: 1. **Fit — always on, at every level.** Which platform, model, and reasoning effort each task deserves, from its kind (design / planning / coding / review / docs), its size, and each platform's remaining usage. A docs ticket never burns a flagship model; a design ticket never gets a cheap one. This is not something the user buys by going slower. 2. **Acceleration — the speed level, and the *only* thing the user chooses.** How eagerly work is handed to *other* agents instead of done in the current session. ## Enable — two design questions, then the numbers only they can see 1. Confirm the project is registered and has dependency-ready tickets. 2. Ask the two **design** questions: - **"Which agentic platforms do you have?"** — the tools installed on their machine: `claude-code`, `codex` (verified), `gemini`, `opencode`, `droid`, `cursor`, `copilot`, `amp` (best-effort), or