memory-layer

# Pi Memory Layer v6.2 Persistent memory via a single SQLite database (`~/.pi/memory/memory.db`). All operations through `memory-store.js` — zero Python dependency, zero MCP servers. Code parsing uses web-tree-sitter (WASM) in-process. Code analysis (imports, call graph, complexity, dead code, churn) and doc indexing (markdown sections, links, glossary, code examples) built in — no external tools needed. Optional HTTP server for programmatic access to the Aurex domain (missions, milestones, working units) and code analysis endpoints. ## CLI Quick Reference ### Session lifecycle - `session-start --project NAME` → auto-recovers incomplete sessions, returns `{ sessionId, recoveredSession }` - `session-end --id INT --memories INT [--auto]` → trust-recovery + close ### LaPis install/update - Install: `pi install git:github.com/GeneGulanesJr/LaPis` - Update: `pi update --extensions` or `pi update --extension git:github.com/GeneGulanesJr/LaPis` - Restart/reload Pi after updating so the refreshed prompt and extension resources are loaded ### Observations - `save --title TEXT --content TEXT [--type TYPE] [--project NAME] [--scope project|personal] [--topic-key KEY] [--session-id ID] [--force]` - Dedup pipeline: trigram overlap checked against existing observations of the same type+project. - **≥85% overlap** → auto-merges (keeps new, soft-deletes old, records `observation_relations`). - **60-84% overlap** → `potential_duplicate` warning, lists matching IDs. - Use `--fo...