brain-backfill-gistslisted

# Brain Backfill Gists — One-time vault migration ## When to use - After implementing gist-layer (Step 4.5 in `brain-save` skill). - After importing many external notes that don't have `gist:` field. - When `brain_lint` reports many `gist_missing` entries. ## Procedure ### Step 1: Find notes that need backfill Call `brain_lint`. From the result, extract `gist_missing` list. If the list is empty — no work needed, exit. ### Step 2: Group by scope Bucket the list by `scope` (each note's scope is in its frontmatter — read with `brain_read` if needed). Typical buckets in our vault: `alpha-seti`, `alpha-details`, `alpha-pdf`, `alpha-local`, `alpha-faq`, `widgetcompare`, `beta`, `symbiosis-brain`, `alpha`, `global`. ### Step 3: Dispatch parallel Explore subagents For each scope bucket — dispatch one `Agent` (subagent_type=Explore) in parallel. Each subagent: 1. Receives the list of paths in its scope. 2. For each path: - Read the note with `brain_read`. - Look at title + body. Determine note type (decision/pattern/mistake/etc.) from frontmatter. - Generate a 1-line gist (≤80 chars) using the type-template from `brain-save` skill Step 4.5: - `project` — what is it, what's distinctive - `decision` — what was decided + reason - `pattern` — when to apply + what it gives - `mistake` — what went wrong + why remember - `research` — what was investigated + main finding - `feedback` — what user noticed + what to change - `user` — princi