Repository navigation
test: verify cross-member memory after server restart - #53
Open
outlier27-cell wants to merge 1 commit into
Open
outlier27-cell wants to merge 1 commit into
outlier27-cell wants to merge 1 commit into
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
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.
Problem
The memory tests cover search, dispatch injection, and persistence separately, but lack a combined regression proving an approved member-originated memory reaches a different member after closing and reopening the server.
Value
This protects cross-member recall after restart and ensures inactive or foreign workspace guidance cannot enter that task's memory envelope. Without this coverage, a persistence/injection integration regression could escape the individual tests.
Approach
Add one real HTTP/SQLite/PTY regression. Fixture Alice contributes a candidate and it is approved through the existing store API. Reopen the same database, preserve source snapshots, authenticate Bob's HTTP search and the orchestrator's HTTP dispatch, and inspect the dispatch-specific memory envelope received by Bob's Node echo subprocess. Disabled, archived, unapproved, and foreign workspace records share the same search tag as exclusion controls.
This is test-only: the scenario passed against current main; no production defect was reproduced or fixed. Fixture writes do not test write authorization. It does not prove model comprehension, actual provider acceptance, or completion of the broader EverOS proposal.
Validation
Impact
No runtime, schema, dependency, or UI changes. References #6 without closing the broader issue.