ref(memory): remove viewer collection facade - #1649
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
dcramer
force-pushed
the
feat/web-memory-linked-identities
branch
2 times, most recently
from
August 22, 2026 22:57
20e8bdb to
b9db2a6
Compare
dcramer
force-pushed
the
codex/1600-memory-viewer
branch
from
August 23, 2026 02:42
5ab8ec9 to
8c8345f
Compare
dcramer
marked this pull request as ready for review
August 23, 2026 02:46
dcramer
force-pushed
the
codex/1600-memory-viewer
branch
from
August 23, 2026 03:02
8c8345f to
8d124e1
Compare
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.
Replaces the memory viewer object facade with named archive, get, list, stats, and timeline operations used directly by the REST API and User page. Authenticated User authority, public and private visibility, archive rules, cursor behavior, ordering, filters, and response shapes stay unchanged.
This is a hard cutover with no compatibility wrapper. The refactor is a small net deletion and keeps the existing real-SQL integration coverage.
Refs #1600