archie-synclisted

# Archie Sync — keep the snapshot current The blueprint and per-folder CLAUDE.md are **living snapshots of the codebase**. Capture the work just done and **reconcile** it back so those snapshots stay accurate. No git writes — record + edit files only; the user decides what to commit. **Prerequisites:** Archie must already be installed (`.archie/sync.py` exists). If it doesn't, tell the user to run `npx @bitraptors/archie "$PWD"` and try again. ## Phase 1 — record the change ledger ### Step 1 — Get context: PROVIDE or BUILD Produce *statements about what the code now is* (not a changelog of your edits): - **PROVIDE** — you hold the reasoning: emit statements from what you know. Real `confidence`, `reconstructed: false`. - **BUILD** — context cleared/compacted or fresh session: read `git diff` and derive statements from the change itself. Structural facts are fine; mark inferred intent `confidence: "low"`, `reconstructed: true`. Don't invent beyond the diff. ### Step 2 — Record Pipe a JSON array of statements. **Descriptive kinds are the default** — what the code now is. Advisory kinds (decision/pitfall/rule) only when a change genuinely establishes one; they are NOT the point. ```json { "statement": "MainViewModel now filters background subscription-refresh errors so they no longer surface the purchase dialog", "kind": "behavior", "evidence_files": ["path/touched/by/this/change.ext"], "confidence": "low | medium | high", "reconstructed": false } ``` Descr