Simplify architecture: remove plugin filewatcher, use basic-memory's native watcher

[bm-clawd]

Problem

The plugin currently has its own filewatcher that duplicates what basic-memory already does natively. This adds complexity and is redundant work.

Additionally, the MCP server is being conflated with direct DB operations — the tools should write directly to the DB without needing an MCP server running.

Proposed Changes

1. Tools write directly to the DB — bm_write, bm_search, etc. should not require an MCP server
2. Remove the plugin's filewatcher — basic-memory already has a filewatcher, no need to duplicate it
3. Extend basic-memory with a watch mode — a mode that runs the filewatcher/indexer without the full MCP server, so markdown files written by the plugin get picked up and indexed automatically
4. Fix all uncaught exceptions — no errors should be thrown/swallowed silently

Target Architecture

Plugin tools write markdown files → basic-memory's watcher detects changes → indexes into the knowledge graph automatically. The plugin becomes a thin layer: write files + query SQLite directly. The MCP server remains a separate optional concern for clients that want MCP stdio access.

Dependencies

• May require changes in basic-memory to support a standalone watch mode (no MCP server)