Memory dialogs and control responses now include a full list of saved memories

What

• The terminal's status dialog schema now includes an optional memories field, listing saved auto-memory entries drawn from the MEMORY.md index and each file's modification time, capped at 200 entries.
• The status call that reports auto-memory/auto-dream status now also returns a memories array whenever memory folders are present.
• A new schema describes a single memory entry: its name (a relative path, or "MEMORY.md" for the index file), its absolute path, an optional description and type (user, feedback, project, or reference) from its frontmatter, and its last-modified time.
• The get_memory_dialog control-protocol response, used by hosts that build their own /memory UI, now includes this same memories array alongside the existing folder list.

Why Tools and custom UIs built on top of Claude Code can now show users exactly which memories are saved, with descriptions and types, instead of only folder-level summaries.