engram-diagnoselisted

# engram-diagnose Inspect the internal state of specific memories and understand what is in the store by category. Useful when a `memory_recall` result seems wrong, when you want to understand the confidence and source evidence behind a memory, or when you need a high-level count of what the store contains. These tools are hidden from the normal tools/list. This skill calls them directly via HTTP. ## When to Use - User says "diagnose this memory", "why does Engram think X", "what's the evidence for memory <id>" - User says "how many memories do I have", "aggregate by tag", "break down memory by type" - User says "summarize memory <id>", "force summarize this entry" - A `memory_recall` result looks wrong or contradicts what you know to be true - Before correcting a memory — understand its evidence first ## How to Use ### 1. Diagnose a single memory — get its evidence map ```bash xh POST "${ENGRAM_BASE_URL:-http://localhost:8788}/mcp" \ "Authorization: Bearer $ENGRAM_API_KEY" \ Content-Type:application/json \ jsonrpc=2.0 id:=1 method=tools/call \ params:='{"name":"memory_diagnose","arguments":{"id":"<memory-id>"}}' ``` Returns: - **conflicts** — other memories that contradict this one - **confidence** — numeric confidence score - **invalidated_sources** — sources that have been marked as no longer reliable - **evidence** — the raw source entries that contributed to this memory Read the response carefully. If `conflicts` is non-empty, report each conflicting mem