handoverlisted

# Handover (Write State) Update project files so the next session can pick up exactly where this one left off. ## Step 1: Review the session Before touching any files, reflect: what was created or significantly changed? What decisions were made? What was discovered or learned? Were new key files created (e.g. in `work/`) that a fresh session would need to know about? ## Step 2: Update root files Check every `.md` file in the project root. Follow each file's own update instructions (found at the top of the file); if a file has none, update it whenever this session's work has made it stale. **Common root files and their update logic:** | File | How to update | |------|---------------| | STATUS.md | Rewrite with current state (current position, recent decisions, next steps, open questions) | | LEARNINGS.md | Append only what passes the file's inclusion criteria — a durable insight a future session would act on. Most sessions add nothing. Do NOT use as a session log. | | BACKLOG.md | Move new granular tasks or unresolved issues here. Keep `STATUS.md` "next steps" focused only on immediate session continuity. | | CLAUDE.md | Update pointers — add new key files, remove stale pointers, update descriptions | | README.md | Update if project description, status, or structure changed | | PRD.md | Update if requirements shifted | | ARCHITECTURE.md | Update if architectural decisions changed | | ROADMAP.md | Update if chunks were completed, added, or reordered | | ORCHESTRATION-PLA