setuplisted

# /setup [<vault-path>] [--check] [--sync-templates] Goal: a new user goes from `git clone` to a working system with this one command and one or two answers. Keep it fast and friendly: ask one question message, batch file operations so the user sees as few permission prompts as possible, and don't lecture. **Idempotent:** creates only what is missing. Never overwrites, moves, or deletes an existing vault file (template files under `--sync-templates` are the only exception, and only after confirmation). Never writes into `.obsidian/` (CLAUDE.md hard rule 2). `<repo>` = `git rev-parse --show-toplevel`. Today = `date +%F`. Modes: no flag → steps 1–6. `--check` → step 7 only (read-only). `--sync-templates` → step 8 only. ## 1. Collect the configuration (one message at most) Read `<repo>/config.env.example`. **It defines what to ask:** every variable in it, together with its comment, is one setting, so variables added there later are picked up automatically. If `<repo>/config.env` exists, its values are the defaults. - If `config.env` already has a valid `VAULT_PATH` and no path argument was given, show the current values and ask "keep these?". Then continue with step 3 (the scaffolding still fills in anything missing). - Otherwise ask everything still unknown in **one** message, with a default for each so the user can reply "ok": - `VAULT_PATH` (required). Use the `<vault-path>` argument if one was given. Otherwise ask for the knowledge-base folder: an existing Obsidian v