fix: use SelectorEventLoop on Windows to avoid cleanup errors

The Windows ProactorEventLoop can raise "IndexError: pop from an empty
deque" during event loop cleanup when there are pending handles. This
was causing the test_bm_tool_help_exits_cleanly test to fail on Windows.

Switch to WindowsSelectorEventLoopPolicy on Windows since we don't need
ProactorEventLoop's features (subprocess pipes, named pipes) for CLI
initialization.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Signed-off-by: phernandez <paul@basicmachines.co>

Author: phernandez

src/basic_memory/services/initialization.py

@@ -6,6 +6,7 @@
 
 import asyncio
 import os
+import sys
 from pathlib import Path
 
 
@@ -193,5 +194,12 @@ async def _init_and_cleanup():
             # Always cleanup database connections to prevent process hang
             await db.shutdown_db()
 
+    # On Windows, use SelectorEventLoop to avoid ProactorEventLoop cleanup issues
+    # The ProactorEventLoop can raise "IndexError: pop from an empty deque" during
+    # event loop cleanup when there are pending handles. SelectorEventLoop is more
+    # stable for our use case (no subprocess pipes or named pipes needed).
+    if sys.platform == "win32":
+        asyncio.set_event_loop_policy(asyncio.WindowsSelectorEventLoopPolicy())
+
     asyncio.run(_init_and_cleanup())
     logger.info("Initialization completed successfully")