Comment by mjbonanno

Wanted to follow up on this... I dug into the codebase after your comment. You're right that the data is all there (last_access, access_count, raw Ebbinghaus relevance score, provenance source type) but it's siloed behind secondary tool calls rather than inline in the Activate response. That's the gap. I'm going to surface those fields directly in the next release so agents can make trust/refresh/ignore decisions in a single round-trip without needing to call muninn_read or muninn_provenance after the fact. Thanks for the sharp feedback! Exactly the kind of thing that comes from actually building multi-agent systems in production.