update-project-memorylisted

# Sync Project Memory Reconcile what is recorded in memory against the real state of a project's files, surface the differences, and update memory only after the user approves. ## When to use Trigger when the user wants memory checked against reality for an ongoing project: "review memory for this project", "is my memory up to date", "sync memory with the files", "audit what you remember about X", "memory is stale". Do NOT trigger for general memory writes that have nothing to compare against (just saving a new fact), or for editing files unrelated to memory. ## Inputs - The project (named by the user, or the active workspace folder if obvious). - The memory directory and its `MEMORY.md` index (paths are in system context). If the project or its working folder is ambiguous, ask which one before proceeding. Do not guess. ## Procedure 1. **Read memory.** Read `MEMORY.md` and every memory file that relates to the project. Note what each one currently claims. 2. **Read reality.** Enumerate the project's working folder (recursive listing), then read the key content files (outlines, drafts, notes, profiles, anything that states facts about the project). Do not rely on filenames alone; open the files. 3. **Diff.** Compare memory against the files and sort every finding into one of three buckets: - **Wrong**: memory says something the files contradict. - **Missing**: the files establish something memory does not record. - **Still accurate**: memory