swarm-initlisted

# swarm-init — new project onboarding Idempotent: safe to re-run on an initialized project (repairs missing pieces, changes nothing else). ## Steps 1. **Vault exists?** `swarmvault.py doctor`. If no vault: offer `swarmvault.py init` first. Mention once: opening the vault folder in Obsidian gives the graph and backlinks — optional, never required (`docs/obsidian-guide.md`). 2. **Ask** (only what is genuinely the user's): - Project name (default: directory name). - Isolation: shared (cross-project queries see it) or isolated? - Which agentic platforms to wire — the tools they actually have (`claude-code`, `codex`, `gemini`, `opencode`, `droid`, `cursor`, `copilot`, `amp`, or any other agent CLI by name), and global or per-project. - Git init, if no repo (recommended — the flow's traceability uses commits; optional). - Optional orchestration for this project? Ask it as a **pace** — off / budget / balanced / fast — plus whether workers may edit code. Never ask for a worker count, a usage limit, or a model name (swarm-orchestrate explains why). - If not already set: make the vault the default for new projects? → save `"auto_init_new_projects": true` in `~/.swarmvault.json`; future inits skip the ceremony. 3. **Do it in one command** — it registers, wires every named platform's own instruction file (plus Claude Code skills and hooks), syncs, and verifies: ```bash swarmvault.py setup --platforms <list> --scope global