End of Session Shutdown Protocol (Doomsday Prep)

Role: Paranoid Lead Architect and Project Manager.

Objective: Secure project state, update all documentation, and prepare a comprehensive handoff. Treat this as if the server is about to be wiped and rebuild must happen from these files alone.

Phase 1: Execution & File Integrity

1. Force Save: Ensure every code block, text buffer, or conceptual change discussed is written to its respective file. Leave nothing in "memory" only.
2. File Creation: If new files were discussed but not generated, generate them now.

Phase 2: Documentation Synchronization

Update the following .md files immediately. Create them if they do not exist:

A. Update README.md

• Reflect the current state of the application
• Update installation or usage instructions if dependencies changed
• Add a "Recent Changes" section summarizing this session's work

B. Update/Create PROJECT_STATUS.md

• Current Phase: Where exactly are we? (Dev, Testing, Refactoring)
• Completed: Bullet points of everything achieved this session
• In Progress: What is half-baked? (Mark clearly to avoid deploying broken code)
• Blockers: Any bugs or issues that couldn't be solved today

C. Update User/Dev Docs

• If API endpoints changed, update API documentation
• If UI logic changed, update user guides

Phase 3: The Brain Dump (Context Preservation)

Create SESSION_HANDOFF_[DATE].md (or append to CHANGELOG.md). Include:

1. The "Why": Briefly explain why specific architectural decisions were made today
2. The "Gotchas": Note weird bugs or workarounds that might be forgotten
3. Next Actions: Strictly prioritized list of exactly what to do first next session

Phase 4: Version Control Prep

1. Generate a comprehensive Git Commit Message formatted as:
   • feat/fix/chore: [Summary]
   • [Bulleted list of detailed changes]
2. Do NOT run the commit command unless instructed, but provide exact commands to stage and commit safely.

Final Output Format

✅ FILE SYNC STATUS: [Report on files saved/updated]
📄 DOCS UPDATED: [List of .md files touched]
🚀 NEXT SESSION TRIGGER: [The one command or task to run first next time]

Execute immediately. Go.