feat(memory): add branchable provider improvement system#71
Merged
Conversation
tangletools
approved these changes
Jul 18, 2026
tangletools
left a comment
Contributor
There was a problem hiding this comment.
✅ Auto-approved drewstone PR — c3cc7b4e
This PR was opened by the trusted drewstone account.
The full PR reviewer audit still runs separately and will publish findings if it detects issues.
tangletools · auto-approval · reason: drewstone_author · 2026-07-18T06:46:38Z
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary\n\n- add official-client Mem0 hosted/OSS and Neo4j Agent Memory adapters plus Graphiti MCP support\n- add isolated branches, snapshots, forks, resume, private/team/shared policies, and ordered per-agent writes\n- add parallel multi-track configuration improvement with fresh-history comparison and atomic activation\n- add durable controller ownership, bounded recovery retries, retired-candidate cleanup, shared dollar limits, and complete cost attribution\n- harden provider scope rejection, exact deletion, delayed-write cleanup, timeout behavior, and late adapter release\n- document the 4.0.0 API and pre-4.0 run-directory migration boundary\n\n## Checks\n\n- 424/424 runnable tests passed across 104 files; 10 intentional skips; 0 failures\n- lint, TypeScript, build, and production dependency audit passed\n- clean tarball install imported all 5 public entry points, ran CLI version 4.0.0, and repacked\n- real SIGKILL and disk resume passed for both the multi-step experiment and direct benchmark paths\n- resumed runs cleared abandoned provider scopes before retry, left 0 active attempts, and left 0 provider records\n- independent read-only review confirmed the named isolation, timeout, cost, and recovery fixes; its late adapter leak finding is fixed with regression coverage\n\n## Limits\n\n- Mem0 and Neo4j compatibility is checked against official current SDK types and deterministic provider behavior tests\n- no live Mem0, Graphiti, or Neo4j credentials were available for a network run\n- deterministic benchmark scores prove execution and recovery behavior; they do not rank third-party memory systems