Skip to content

test: verify cross-member memory after server restart - #53

Open
outlier27-cell wants to merge 1 commit into
tt-a1i:mainfrom
outlier27-cell:test/issue-6-cross-member-memory
Open

outlier27-cell wants to merge 1 commit into
tt-a1i:mainfrom
outlier27-cell:test/issue-6-cross-member-memory

Conversation

@outlier27-cell

Copy link
Copy Markdown
Contributor

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

  • Memory API, prompt contract, and restart suites: 19 tests passed.
  • After independent review narrowed assertions to the dispatch-specific envelope, the final restart test passed again.
  • Biome on the new test, project check, build, and git diff check passed.
  • Whole-project TypeScript noEmit failed with two TS2352 errors in unchanged tests/unit/workspace-shell-runtime.test.ts (lines 15 and 119); no error was reported in the new test. Production TypeScript compilation in build passed.
  • Four independent reviews identified the same startup-versus-dispatch assertion issue; it was fixed and independently rechecked with no blockers.
  • No full-suite claim.

Impact

No runtime, schema, dependency, or UI changes. References #6 without closing the broader issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant