feat(memory): auto-capture search/write/index events for consolidation feed
The DEFAULT_CAPTURE_TYPES machinery existed but was never wired into the API servers, so the memory event log stayed empty and consolidation always returned 0.
- hub/server.mjs: add fireCaptureEvent() helper; capture 'search' (with query, mode, result_count), 'write' (path, action), and 'index' (note_count) events after successful responses — fire-and-forget, zero latency impact - hub/bridge/server.mjs: add fireBridgeCaptureEvent() helper; capture 'search' via res.on('finish') (handles all return paths cleanly) and 'index' after successful embed+upsert — hosted users now accumulate memory events - 5 new tests verifying shouldCapture gating, search/write/index event shape, and ts field presence so consolidation can summarise real usage
0 comments
muse hub commit comment sha256:f70c2f96f6addc887ae79bfbaf2eb2444c06d60abe63b6f7191b4d312ef5ac2e --body "your comment"
No comments yet. Be the first to start the discussion.