grounder-setuplisted

# Grounder setup Drive the native Grounder CLI to preview, install, verify, and repair Grounder. Adding this skill only loads these instructions. Running it is what installs the CLI (if missing), skills, and hooks. ## Boundary - Delegate writes to the CLI. Do not copy skill files, edit `~/.grounder/config.json` by hand, or invent repair steps. - Do not pass `--agent` unless the user asks to **limit** the install. Auto-detect should install every detected host (Cursor and Claude Code). - Never `--force` on first setup. Never `--force` a vault-root change (home config pointing at a different vault is a conflict to surface, not overwrite). - Always preview writes in chat and get approval. For `setup` / `link` / `migrate`, say the `Step N of 4` line (section 4), run `--dry-run`, and show that stdout as-is — do not reconstruct the write list. Then apply (`--yes` on setup/link; `migrate` has no confirm). Never rely on the interactive `confirm()` prompt — it treats empty stdin as yes, so a non-TTY agent shell would apply unaudited. No extra confirmation gates. - Do not write a test note or handoff unless asked. - Skill present ≠ Grounder ready. The vault and `~/.grounder` live outside the project directory. If the host prompts for a permission scope, grant access to those two specific paths — the CLI needs to read and write there. ## 1. Environment and Grounder CLI Steps 1–2 of the board. Prefer a real global CLI so `grounder setup` can symlink `~/.grounder/runtime` (tracks u