maintain-contractlisted

# Maintain contract — how to drive the wiki safely This is the procedure any agent (this plugin's or a third party's) follows to operate on a vault without corrupting it. It pairs with `/claude-wiki-pages:engine-api`, which documents the tool surface this contract sequences. ## The three invariants 1. **Ground, then judge, then verify.** Compute facts with the engine (verify, fix, and the planned link-suggest/search) before reasoning. The LLM makes only judgment calls — topic placement, prose, what to synthesize — over engine-computed facts, never from memory. Close every write with `verify`/`heal`. 2. **`raw/` is immutable.** Never write, move, or delete anything under `vault/raw/`. Sources are the provenance anchor. The `protect-raw` hook enforces this; do not fight it. 3. **Git is the safety net, not approval.** Self-heal is automatic. Before structural changes, a checkpoint commit is written; rollback is `git revert <healCommit>`. Do not prompt the user for permission to fix structure. ## Ingest (add knowledge) 1. Read each source in `raw/` completely. 2. Write cited wiki pages (`sources:` as `[[wikilinks]]` to `_sources/` summaries). 3. Run `engine.sh heal` — it checkpoints, then verify→fix→re-verify, then commits. 4. Surface only what needs editorial intent (ambiguous merges, deletions). ## Retrieve (answer questions) 1. Use grounded retrieval (engine `search`, or `grep` over `wiki/` until `search` ships) to fetch candidate pages. 2. Answer **only** from those pa