memory-and-contextlisted

# Memory and Context **IMPORTANT: Start your response with a context preamble.** Call `help_lookup(topic="memory", mode="preamble")` and display the returned `preamble` text as a blockquote. Then tell the user they can say "tell me more" for a step-by-step guide, or answer the scoping questions below to proceed. If the MCP call fails, fall back to: > **Memory and Context** — Stores and retrieves persistent context across sessions — notes, preferences, project state. ## Scoping Before running, ask: 1. **Operation**: "What do you need? Store, retrieve, search, or forget?" 2. **Key/query**: "What key or search term?" 3. **Classification** (store only): "PUBLIC, INTERNAL, or SENSITIVE?" ## Execution ### Shared command workspace (preferred) Open adapter `memory-and-context` with the selected operation and scoped arguments. Present its widget or returned Markdown and collect its bound action before calling the existing memory tool. Store and forget are external writes and require explicit confirmation; retrieve and search remain read-only. Publish the exact tool response as `operation_result`. After a successful store or forget, follow the workspace's returned `memory_retrieve` verification request and publish it as `verification_result`. Store succeeds only when the same value and classification are retrieved; forget succeeds only when the post-delete read misses. Never render stored values—especially SENSITIVE values—in the workspace. A failed backend call must s