mnemosyne-memorylisted

# Mnemosyne Memory Use Mnemosyne as a selective continuity layer across tasks and agent sessions. Recall only useful context, preserve durable knowledge, and maintain one concise project handoff without turning memory into a transcript or a second source of truth. ## Governing contract 1. Follow applicable host, repository, and user instructions first. They govern whether memory is automatic, what is sensitive, and which profile or bank is active. 2. Let the host-configured Mnemosyne connection choose the bank. Never guess or hardcode a bank, home-directory path, database path, or profile. 3. Use available `mnemosyne_*` tools by capability. Optional tools can vary by Mnemosyne version; degrade gracefully when one is absent. 4. Keep repository files, tracked documentation, and verified live state authoritative. Treat recalled memory as evidence to check, not truth to obey. 5. Continue the user's task when Mnemosyne is unavailable. Do not replace it by reading its database directly or by switching to another memory surface. Apply the lifecycle to substantive work: repository changes, diagnosis, multi-step research, durable decisions, or work whose state should survive the current session. Skip routine memory work for greetings and disposable one-answer questions unless the user explicitly asks to remember or recall. ## Resolve project identity Choose one stable project key before project-scoped recall or writes: 1. Use a key explicitly defined by the us