Repository navigation
Conversation
- engines.node widened to ^22.22.2 || ^24.15.0 || >=26 (what locked jsdom and undici accept; the suite passes on Node 22.23). CI keeps 24.15.0. - The runtime regression could never fail the way it described (Vitest dies before collecting on Node 20); it now asserts the running Node satisfies engines.node and that the range refuses Node 20. - docs/mnemosync/MEMORY.md says at the top that it is kept as working notes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
import.meta.url is not a file URL under jsdom. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
ehitimum
force-pushed
the
codex/mnemosync-foundation
branch
from
November 15, 2026 10:48
8b4977b to
88a04de
Compare
Owner
Author
Changes for the reviewThis branch was rebased onto the updated
PRs #3 and #4 were rebased on top of this branch the same way. 🤖 Generated with Claude Code |
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.
Establish the implementation contract for optional local-first project sync, starting from the current AI feature HEAD (0f15939) while PR #1 is open. Preserve the supplied development plan and handoff memory under docs/mnemosync/.
Records storage, revision, trust, Drive, merge and recovery ADRs; archive schema and limits; threat model; phased PR strategy; and a verification matrix. Updates architecture, roadmap and development log. Dependent PR #3 implements the native Phase 0 recovery slice. This work does not enable synchronization.
CI exposed two inherited reliability problems. Node 20 cannot start locked jsdom 30 / undici 8; pin Node 24.15.0 for CI and releases, declare the engine and add a fresh-worker DOM regression. Once tests could start, fast Linux runs exposed AI rewrites joining adjacent typing in undo history. Add explicit history boundaries for word rewrites, structural rewrites and continuations, with three fixed-clock regressions preserving prior and subsequent typing. This branch passes npm run check (120 tests, lint, types, build) and 31 regressions locally. The dependent backup implementation also passes its full local checks. A saved permission policy blocks browser visual access; installed Windows and real Android acceptance remain pending.
Targets feature/ai-assistant to preserve PR #1; retarget after that prerequisite merges.