v0.2.0

Breaking

• forget_all_memory now requires confirm=true to actually delete anything. A bare call reports the entity/relation counts a real call would remove and deletes nothing. destructive_hint=true on this tool is only an advisory hint the MCP spec doesn't require a host to enforce, so a host that treats it as cosmetic (or an agent auto-approving destructive tools) could previously wipe a whole memory graph on the first call with zero human confirmation. This closes that gap at the protocol level instead of relying solely on the host.

Added

• Provenance.client_name, captured automatically from the calling MCP client's initialize handshake (not a tool argument). When two clients write contradicting facts (same subject+predicate, different object) and both declare a different client, the write no longer silently overwrites the older fact — both are kept and add_memory's response says so, since nothing in a memory graph makes the newer write the correct one. Same-client corrections and unrecognized clients keep the existing update-in-place behavior.

Both changes came directly from real technical review on a public post about this project, not internal speculation.

Full diff: v0.1.3...v0.2.0