fix: qualify Brain continuity and disclose memory routing uncertainty - #209
Merged
Merged
Conversation
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
1 participant
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.
Memory status inferred an active native writer from file presence, even when Ruflo's CLI selected the other database. Report both stores with routing explicitly unverified and document the snapshot-verified explicit-path retrieval workaround. Preserve all project data and existing shared MCP paths.
Qualify Brain's exact 4.3.17 continuity hook declarations without treating arbitrary future versions or matching event names as validated. Reject extra behavior and keep static configuration separate from runtime execution evidence.
Validation: 3,776 tests, 3,770 passed, six skipped; typecheck, complexity gate, build, and Markdown lint passed. Independent read-only review found no blockers. Runtime and outstanding cross-host limitations are recorded in the follow-up audit.
Deferred dashboard changes are excluded.