memory-recall

From README

Steps Use memorysearch with a concrete query and topk: 5. It returns text containing a JSON array of objects with chunkhash, content and source. When calling through execute, return the search result and inspect its text before selecting hashes. Evaluate relevance before expanding results. Use memoryget with the most promising chunkhash values to read full Markdown sections. For claims requiring original dialogue, use memorytranscript with sessionid, turnid and dbpath from the expanded session: / turn: / db: anchor. Set context: 3; for an anchor without a turn, use limit: 10. If OpenCode transcript lookup fails after an upgrade, distinguish an incompatible host/plugin pair, an unavailable database or session/turn, and an incomplete V1-to-V2 database migration. See OpenCode diagnostics, also used by memory-config. Check the referenced conversation only; a lookup failure does not justify scanning unrelated transcripts. Keep existing markdown and session: / turn: / db: anchors unchanged.