loom-maintainlisted

# Loom Maintain Vault governance: validate → migrate → connect → evolve → index. ## Read First - `references/schemas.md` - `<vault-root>/.loom/config.yaml` if it exists (vault configuration) ## Validate Run read-only vault health check. ```bash python3 scripts/scan_vault.py <vault-root> python3 scripts/validate_vault.py <vault-root> ``` Output: validation report with blocking errors and migration warnings. Rules: - Never write files. - Separate blocking errors from legacy-compatibility warnings. - Treat legacy warnings as migration candidates, not failures. ## Migrate Scan and migrate a legacy Markdown vault into the Loom schema. ### Migration workflow 1. Scan vault to inventory: directory presence, note counts by year/status, missing frontmatter, status values, link-only topics, broken links, index existence. 2. Propose staged plan: - Initialize indexes without modifying notes. - Add missing frontmatter to high-confidence files. - Normalize status values only if requested. - Convert selected link-only Topic Notes into synthesis notes. - Validate links and index consistency. 3. Apply only when user explicitly requests writes. ```bash python3 scripts/scan_vault.py <vault-root> python3 scripts/validate_vault.py <vault-root> python3 scripts/build_indexes.py <vault-root> ``` ### Migration rules - Default is read-only. Generate report before changing anything. - Preserve all content and unknown frontmatter. - Prefer additive changes. - Do not move ass