Root causes:
- index.js tried to start its own UI bridge server on port 9711, but
ws-bridge.js (spawned by Tauri) already owns it → broadcastUiAction
was a no-op. Fixed by connecting index.js as a WebSocket CLIENT that
sends messages through the existing bridge.
- ws-bridge.js UI bridge had no relay — client messages weren't forwarded.
Added relay so messages from the MCP server reach the React frontend.
- useAiActivity hook existed but was never imported in App.tsx.
- useAiActivity only handled highlight, not open_note/open_tab/set_filter.
- No vault_changed events after write operations.
- set_filter payload used `type` key which overwrote `type: 'ui_action'`.
Changes:
- mcp-server/index.js: connect as WS client instead of starting server;
broadcast vault_changed after all write operations
- mcp-server/ws-bridge.js: add message relay in UI bridge; broadcast
vault_changed after write operations; fix set_filter payload key
- useAiActivity: handle all UI actions (highlight, open_note, open_tab,
set_filter, vault_changed); accept callbacks; auto-reconnect on close
- App.tsx: wire useAiActivity into vault/notes/selection actions; apply
ai-highlight CSS class to editor and note list panels
- App.css: add ai-highlight-glow keyframe animation
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
93d598d04c