Reflect

This is the cleanup step you run after merging a branch. It writes learnings to MEMORY.md and your Basic Memory vault, verifies that issues mentioned in commits are actually closed, optionally posts learnings as issue comments, and creates new issues from scratchpad TODOs. The MEMORY.md write uses a retry loop with rebase to handle concurrent updates, which is smart if you have multiple agents or teammates running reflect at the same time. It also prunes entries older than 30 days and caps the file at 200 lines. The phase gate blocks completion if you wrote branch context notes but forgot to update MEMORY.md. Probably overkill for solo work, but if you're serious about keeping project memory accurate and not losing context between sessions, this enforces the discipline.