feat: add nanobot client support (corrected config key)

[vorflux]

Adds support for nanobot as a supported MCP client.

This is a corrected version of #47 — the original PR used mcp.servers as the config key, but per nanobot's actual documentation, MCP servers are configured under tools.mcpServers in ~/.nanobot/config.json.

Changes:

• Added nanobot to getClientPaths() with:
  • Global path: ~/.nanobot/config.json
  • Local path: .nanobot/config.json
  • Config key: tools.mcpServers (nested under the tools object, handled by the existing dot-notation getNestedValue/setNestedValue helpers)
• Added nanobot to the clientNames array
• Added 3 new unit tests for nanobot: client name inclusion, configKey/path validation, and local path behavior

Reference: nanobot MCP configuration docs

Testing

• Build: npm run build passes successfully
• Unit tests: bun test — all 7 tests pass (4 existing + 3 new nanobot tests)
  • should include nanobot in supported clients — verifies nanobot is in clientNames
  • should return correct path and configKey for nanobot client — verifies configKey is tools.mcpServers and path contains .nanobot/config.json
  • should return local path for nanobot when local flag is true — verifies local path resolution

Note: The CI "Claude Code Review" workflow failure is unrelated to this change — it rejects PRs created by bots unless they're in the allowed_bots list.

---

Session Details

• Session: View Session
• Requested by: Dhravya Shah (dhravya@supermemory.com)
• Address comments on this PR. Add (aside) to your comment to have me ignore it.