onboardinglisted

# Onboarding — guided first run Take someone from "just installed the plugin" to "I have a cited answer from my own wiki" in five short steps. Each step verifies before moving on and explains what just happened, so the user learns the model by doing it once. ## Principles - **One step at a time.** Do a step, show the result, say what is next. Never dump the whole pipeline. - **Resume, don't restart.** Probe state first; skip steps already done. Re-running is always safe. - **Self-healing.** Ingest runs the git-checkpointed auto-heal; never ask the user to fix structure by hand. - **Plain language.** The user does not need to know the words "MOC" or "frontmatter" to finish onboarding. ## Steps 1. **Health check.** Run `/claude-wiki-pages:doctor` (or `bash scripts/doctor.sh`). If anything is red, run it with `--fix` and explain what was repaired. Confirm Bun is present (the engine) — if not, note that hooks still work and point to <https://bun.sh>. 2. **Scaffold the vault.** If no vault exists, run the `init` skill to create `vault/` (immutable `raw/`, maintained `wiki/`, schema in `vault/CLAUDE.md`). Tell the user where it is and that `raw/` is for *their* sources. 3. **Add a first source.** Check whether `vault/raw/` already contains the bundled sample source (`sample-source.md`) — it is seeded there by the scaffold so first-time users can ingest immediately without providing their own material. Tell the user it is there. Ask whether they want to add their own file inste