v3.59.5 — distill both memory stores

Fixes

• Memory distillation now covers both project stores (#4338, fixes #3446). memory distill run
  and the daemon's consolidate worker previously resolved only memory.db, which in an
  MCP-only project often lacks the AgentDB target tables, so every tick skipped while the actual
  corpus accumulated un-distilled in the sibling agentdb-memory.db. Both stores are now
  resolved and distilled; a per-store failure can't block the other, and an explicit --db still
  pins a single store.

Published

• @claude-flow/cli@3.59.5, claude-flow@3.59.5, ruflo@3.59.5 — latest/alpha/v3alpha
  dist-tags all verified matching on the live registry.