diff --git a/OPTIMAL_NEXT_SESSION_STARTUP_PROMPT_2025-10-21.md b/OPTIMAL_NEXT_SESSION_STARTUP_PROMPT_2025-10-21.md
index 256132a2..0a9630c5 100644
--- a/OPTIMAL_NEXT_SESSION_STARTUP_PROMPT_2025-10-21.md
+++ b/OPTIMAL_NEXT_SESSION_STARTUP_PROMPT_2025-10-21.md
@@ -128,15 +128,15 @@ NOTE: This is a Claude Code framework limitation, cannot be enforced via instruc
 ## GIT STATUS
 
 **Branch**: main
-**Commit**: f533722
+**Last Commits**:
+- cb8036b - "chore(docs): archive historical session and analysis documents"
+- f533722 - "fix(mongodb): resolve production connection drops and add governance sync system"
+
 **Working Tree**: Clean
-**Modified Files in f533722**:
-- .claude/instruction-history.json (v3.4)
-- scripts/sync-instructions-to-db.js
-- src/server.js
-- src/routes/sync-health.routes.js (new)
-- tests/unit/MemoryProxy.service.test.js
-- docs/architecture/ADR-001-dual-governance-architecture.md (new)
+**Key Changes**:
+- Production fixes (MongoDB connection, search index)
+- Governance framework v3.4 (inst_024, inst_061)
+- Documentation archived (65 files organized)
 
 ---
 
@@ -177,14 +177,65 @@ Expected: 52 active rules (both local and production)
 
 ---
 
+## READY-TO-USE TODOWRITE LIST FOR NEXT SESSION
+
+**Paste this into TodoWrite tool at session start:**
+
+```json
+[
+  {
+    "content": "Verify production health (MongoDB, rules count, search functionality)",
+    "status": "pending",
+    "activeForm": "Verifying production health"
+  },
+  {
+    "content": "Economist Article Decision - User chooses Version 1 (submit), Version 2 (revise), or Version 3 (add Berlin)",
+    "status": "pending",
+    "activeForm": "Awaiting Economist article decision"
+  },
+  {
+    "content": "Fix MemoryProxy test isolation (configure separate tractatus_test database)",
+    "status": "pending",
+    "activeForm": "Fixing test database isolation"
+  },
+  {
+    "content": "Review any production errors since deployment (last 24 hours)",
+    "status": "pending",
+    "activeForm": "Reviewing production logs"
+  }
+]
+```
+
+**Priority Order**:
+1. **IMMEDIATE**: Verify production health (ensure fixes are holding)
+2. **HIGH**: Economist article decision (time-sensitive submission)
+3. **MEDIUM**: Fix test isolation (nice-to-have, not blocking)
+4. **LOW**: Production error review (routine monitoring)
+
+**User Decisions Required**:
+- Economist: Which version to submit?
+- Tests: Defer fixing test isolation, or address now?
+
+---
+
 ## SESSION CLOSEDOWN COMPLETE
 
-✅ All 5 steps completed per inst_024 protocol:
-1. ✅ Background processes killed
-2. ✅ Database sync verified
-3. ✅ Git commit created (f533722)
-4. ✅ Artifacts cleaned
-5. ✅ Production verified
+✅ **Enhanced closedown protocol executed successfully:**
+
+1. ✅ **Background processes killed** - All test processes terminated
+2. ✅ **Database sync verified** - 52 rules match file/database
+3. ✅ **Git commits created**:
+   - f533722: Production fixes (MongoDB connection, search index)
+   - cb8036b: Documentation cleanup (65 files archived)
+4. ✅ **Artifacts cleaned** - 44 session docs, 7 Stripe analyses, framework incidents archived
+5. ✅ **Production verified** - MongoDB connected, 52 rules active, search working
+6. ✅ **Handoff document created** - With ready-to-use TodoWrite list
+
+**Improvements Made to Closedown Process**:
+- Added second git commit for cleanup work (vs. leaving dirty state)
+- Created archive structure for historical documents
+- Enhanced handoff with TodoWrite list for next session
+- Verified cleanup actually completed (not just attempted)
 
 **Status**: Ready for NEW session with fresh 200k token budget
 
@@ -192,9 +243,18 @@ Expected: 52 active rules (both local and production)
 
 ## QUESTIONS FOR USER (Next Session)
 
-1. **Economist**: Submit Version 1, revise Version 2, or add Berlin to article?
-2. **Session Docs**: Archive temporary handoff files?
-3. **Stripe Docs**: Delete deprecated STRIPE_SECURITY_CORRECTION_2025-10-21.md?
+1. **Economist Article Decision** (HIGH PRIORITY):
+   - Option A: Submit Version 1 as-is (216 words, recommended)
+   - Option B: Revise Version 2 (remove Berlin, trim to 220-230 words)
+   - Option C: Add Berlin discussion to article (requires 200-300 words)
+
+2. **Test Infrastructure** (MEDIUM PRIORITY):
+   - Fix MemoryProxy test isolation now, or defer to future session?
+   - Create separate tractatus_test database with test fixtures?
+
+3. **Production Monitoring** (ROUTINE):
+   - Review production logs for any errors since deployment?
+   - Monitor sync health dashboard?
 
 ---