Repository navigation
fix(memory): safely migrate legacy bookmarks and refresh README - #151
Merged
Merged
Conversation
Preserve legacy bookmark data through atomic conflict-aware migration, and document the measured architecture and first-run experience.
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.
Change summary
What: Safely reconcile legacy bookmarks during database initialization and refresh the bilingual onboarding documentation.
Why: Existing databases can contain both legacy and current tables, or partially migrated references. These cases need to preserve all records and remain recoverable. New users also need a concrete first experience and an agent-assisted setup path.
Changes:
Not verified
Not verified: No migration was run against a real user memory database. Crash/power-loss and concurrent-process scenarios, installation in actual agent hosts, and cloud integration were not tested. Local verification ran on Windows.
Completion checklist
Local quality checks
agent:verify, including the checks covered byverify:static.test:productpassed throughagent:verify: 2,091 passed, 2 skipped.## Not verifiedis filled in.mutation:teethpassed for all 23 targets and restored the target files.The documentation check reported one existing bilingual-link warning in an unrelated decision; lint reported one existing warning in an unrelated integration test.
RCP (Repository Control Plane)
agent:verifyreconciled the changed paths and passed.CI completion confirmation
All checks passed.