memory-recap

# Memory Recap Turn authorized memories into an actionable retrospective: briefly describe how the user works, then focus on which collaboration problems are worth addressing, what to change next time, and how to evaluate the result. Go beyond profiles or praise, and do not reuse a previously generated profile as the answer to a new analysis. ## Scope and inputs - Preserve the current request's sources, projects, time window, model, and budget. Do not ask again for authorization already given; clarify only when missing information would materially change what is read or sent externally. - For a small recap, prefer summaries and relevant independent task records. When the user requests “all memories,” enumerate and copy all readable original content within the authorized scope before analyzing it in batches. Clearly distinguish sampling, summary analysis, and full-corpus analysis. - A global library may contain project knowledge. Preserve native source identity, project binding, content scope, and material role. Do not merge projects by basename or interpret a global path as evidence of personal preferences. - Reuse existing native Memory interfaces or user-provided exports. Missing sources do not justify automatically expanding into raw sessions, databases, or caches. When using Better Harness or Qoder, read the [execution reference](references/execution.md) as needed. - Before large model runs, report file count, content size, and expected batch count, and respect the exi...