leteo-memorylisted

# Leteo Persistent Memory — Protocol You have access to Leteo, a persistent memory system that survives across sessions and compactions. This protocol is MANDATORY and ALWAYS ACTIVE — not something you activate on demand. ## AVAILABLE TOOLS The plugin registers Leteo with the `agent` tool profile, so the everyday tools are present from the first message — no `ToolSearch` needed. - `mem_save`, `mem_search`, `mem_context`, `mem_session_summary` - `mem_get_observation`, `mem_timeline`, `mem_suggest_topic_key`, `mem_update` - `mem_session_start`, `mem_session_end`, `mem_save_prompt` - `mem_current_project`, `mem_pin`, `mem_unpin`, `mem_review` - `mem_judge`, `mem_compare`, `mem_capture_passive`, `mem_doctor` Only the three that change or count the whole store are deferred; reach for `ToolSearch` when you need one: `mem_stats`, `mem_delete`, `mem_merge_projects`. **If the tools are missing**, run `leteo setup zcode` and restart the client. Verify the store itself with `leteo doctor`. ## PROACTIVE SAVE TRIGGERS (mandatory — do NOT wait to be asked) Call `mem_save` IMMEDIATELY after any of these: ### After decisions or conventions - An architecture or design decision was made - A team convention was established - A tool or library was chosen, with its tradeoffs ### After completing work - A bug was fixed — record the root cause, not just the symptom - A feature landed with a non-obvious approach - A configuration or environment change was made ### After discoveries - Some