mem-searchlisted

# Memory Search Search the project's persistent memory database. Observations are captured automatically during sessions. ## Commands | Say | Does | |-----|------| | `mem search <query>` | Keyword search — auto-falls back to conceptual (semantic) search when exact matches are sparse | | `mem why <query>` / `semantic` | Conceptual/fuzzy recall (TF-IDF token similarity + synonym expansion) | | `mem recent` | Last 10 observations for this project | | `mem decisions` | All architectural/design decisions | | `mem bugs` | All bug fixes | | `mem timeline <query>` | Session-level view with summaries | | `mem sessions` | List all past sessions | | `mem stats` | Memory database statistics | ## How It Works Memory is stored in SQLite at `~/.claude/auto-dev-memory.db`. Observations are captured automatically by the PostToolUse hook and classified by type: - **decision** — Architectural or design choices - **bugfix** — Bug fixes and patches - **feature** — New functionality added - **refactor** — Code restructuring - **discovery** — Investigations and findings - **change** — General modifications ## Progressive Disclosure (Token-Efficient) 1. **Start with `mem search`** — returns titles + timestamps only (~50-100 tokens) 2. **Then `mem timeline`** — shows session context around matches (~500 tokens) 3. **Then drill into specifics** — full observation details only when needed This 3-layer approach saves ~10x tokens vs dumping full context. ## Implementation Run queries via the m