baalda-setuplisted

# Baalda OS — Setup + Onboarding USE WHEN the user runs `/baalda-setup` or asks to set up their Baalda vault, bootstrap the second brain, initialize the system, or turn a folder of notes into an AI-operated OS. Baalda notes are plain `.md` files on disk, so everything this skill builds is just files and folders — no plugins to install, no import step. The moment you write them, the app indexes them, and if the vault is synced they appear for every teammate live. ## Baalda ground rules (read once, obey throughout) These are app invariants, not preferences. Breaking them corrupts note identity or the sync state. 1. **Run from the vault root.** The vault root is the folder the user opened in Baalda. Everything below writes relative to it. If the current directory isn't that folder, stop and ask. 2. **`.context/` is off-limits.** Baalda keeps its SQLite index, CRDT store and `config.json` in `<vault>/.context/`. Never read, write, walk, move, index, or `git add` it. Same for `.git`. 3. **Write files, don't shell out to move them.** Creating and editing `.md` files with normal tools is fully supported — the watcher picks the change up in ~150ms and merges it as a CRDT operation, so an AI edit and a human keystroke coexist instead of clobbering. 4. **Never `mv` or `rm` a note that is already synced.** A note's identity is a `doc_id`, not its path. An external move looks like *delete + create* to the app: the note gets a **new** `doc_id`, and its history, back