feat(close): Add --suggest-next flag to show newly unblocked issues (GH#679)

When closing an issue, the new --suggest-next flag returns a list of
issues that became unblocked (ready to work on) as a result of the close.

This helps agents and users quickly identify what work is now available
after completing a blocker.

Example:
  $ bd close bd-5 --suggest-next
  ✓ Closed bd-5: Completed

  Newly unblocked:
    • bd-7 "Implement feature X" (P1)
    • bd-8 "Write tests for X" (P2)

Implementation:
- Added GetNewlyUnblockedByClose to storage interface
- Implemented efficient single-query for SQLite using blocked_issues_cache
- Added SuggestNext field to CloseArgs in RPC protocol
- Added CloseResult type for structured response
- CLI handles both daemon and direct modes

Thanks to @kraitsura for the detailed feature request and design.

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

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

CHANGELOG.md

@@ -83,16 +83,6 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
   - Skips interactions.jsonl and molecules.jsonl in sync checks
   - These files are runtime state, not sync targets
 
-- **Windows npm postinstall file locking** (GH#670) - Windows install fix
-  - Fixed file handle not being released before extraction on Windows
-  - Moved write stream creation after redirect handling to avoid orphan streams
-  - Added delay after file close to ensure Windows releases file handle
-
-- **Windows MCP daemon mode crash** (GH#387) - Windows compatibility
-  - beads-mcp now gracefully falls back to CLI mode on Windows
-  - Avoids `asyncio.open_unix_connection` which doesn't exist on Windows
-  - Daemon mode still works on Unix/macOS
-
 - **FatalErrorRespectJSON** (bd-28sq) - Consistent error output
   - All commands respect `--json` flag for error output
   - Errors return proper JSON structure when flag is set