locus-memorylisted

# Locus -- Persistent Project Memory You have access to Locus memory tools via MCP. Use them to maintain project context across sessions. ## Core Tools 1. **memory_recall** -- Summary-first recall for past-work questions 2. **memory_calendar** -- Discover day/week/month activity buckets by project and time range 3. **memory_project_state** -- Verify current project identity, package/git state, freshness, and active next steps 4. **memory_search** -- FTS5 search across all memory layers 5. **memory_remember** -- Save architecture decisions with auto-redaction 6. **memory_explore** -- Navigate the project file tree 7. **memory_timeline** -- View recent conversation history 8. **memory_status** -- Memory health and storage info 9. **memory_scan** -- Re-index project structure after file changes 10. **memory_review** -- Inspect durable memories, states, confidence, and evidence ## Key Behaviors - Always check Locus before saying you do not remember prior work or prior decisions - Use `memory_recall` first for questions about past work, prior decisions, or recent progress such as: - "what did we do yesterday?" - "what did we decide about auth?" - "what did we just fix?" - Use `memory_calendar` for broad period discovery such as "what did we work on this month?" or "show May work" before drilling into specific days, weeks, or topics - For user period questions, pass `this_month`, `last_month`, or an explicit range instead of relying on the default `last_30d` - For date-s