setup

# Deus Setup Run setup steps automatically. Only pause when user action is required (channel authentication, configuration choices). Setup uses `bash setup.sh` for bootstrap, then `npx tsx setup/index.ts --step <name>` for all other steps. Steps emit structured status blocks to stdout. Verbose logs go to `logs/setup.log`. **Principle:** When something is broken or missing, fix it. Don't tell the user to go fix it themselves unless it genuinely requires their manual action (e.g. authenticating a channel, pasting a secret token). If a dependency is missing, install it. If a service won't start, diagnose and repair. Ask the user for permission when needed, then do the work. **UX Note:** Use `AskUserQuestion` for all user-facing questions. **CRITICAL:** Do NOT add git remotes (`git remote add`), fetch from external repos, or install npm packages from the public registry outside of step 0. All channel code and packages are local in the repo. If something seems missing, check `packages/` and `src/channels/` before looking externally. **Vault structure default:** The memory step seeds `CLAUDE.md` (identity + critical rules + index + session state). Only `CLAUDE.md` auto-loads every turn — everything else loads on demand via `memory_tree`. ## 0. Git & Fork Setup Check the git remote configuration to ensure the user has a proper setup for receiving updates. Run: - `git remote -v` Determine which case applies based on the origin URL: **Case A — `origin` points to the Deus sou...