will.anderson
599073cb92
Every node object on consumer read routes (/api/nodes, /api/search, activation results, neighbors, compiled context) carried the full ~5.7KB emb vector — responses 10-50x oversized, blowing MCP token limits. engram_emit_node_json now takes include_emb; only engram_save passes 1, so persistence and the /api/sync//api/edges replication paths (which serve engram_save output) keep embeddings intact. _eg_act_wm_evicted/_eg_act_breakthroughs were reset at the top of every engram_activate, so act_stats reported only the last call and the 60s heartbeat missed nearly all events (curiosity runs 2 activates per 30s). Both are now monotonic process-lifetime totals; consumers diff readings.