Add native Windows support (#91)

- Native Windows daemon using TCP loopback endpoints
- Direct-mode fallback for CLI/daemon compatibility
- Comment operations over RPC
- PowerShell installer script
- Go 1.24 requirement
- Cross-OS testing documented

Co-authored-by: danshapiro <danshapiro@users.noreply.github.com>
Amp-Thread-ID: https://ampcode.com/threads/T-c6230265-055f-4af1-9712-4481061886db
Co-authored-by: Amp <amp@ampcode.com>

integrations/beads-mcp/README.md

@@ -80,7 +80,7 @@ bd daemon --global
 The MCP server automatically detects the global daemon and routes requests based on your working directory. No configuration changes needed!
 
 **How it works:**
-1. MCP server checks for local daemon socket (`.beads/bd.sock`)
+1. MCP server checks for local daemon socket (`.beads/bd.sock`) — on Windows this file contains the TCP endpoint metadata
 2. Falls back to global daemon socket (`~/.beads/bd.sock`)
 3. Routes requests to correct database based on working directory
 4. Each project keeps its own database at `.beads/*.db`

integrations/beads-mcp/SETUP_DAEMON.md

@@ -32,7 +32,7 @@ bd daemon start
 ```
 
 The daemon will:
-- Listen on `.beads/bd.sock`
+- Listen on `.beads/bd.sock` (Windows: file stores loopback TCP metadata)
 - Route operations to correct database based on request cwd
 - Handle multiple repos simultaneously