[codex] Add durable MEMFS snapshotting for SQLite sync#3834
Draft
ashfame wants to merge 3 commits into
Draft
Conversation
18fb906 to
c1d8954
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
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.
🚧 Don't review yet
Branch note
This branch has been rebuilt directly on top of trunk. It intentionally does not include the opfs_sqlite_flush_risk branch stack or the old VACUUM INTO snapshot path.
What changed
Why
This creates a correctness-oriented snapshot substrate for SQLite sync, including journal and WAL mode sidecar files, and gives callers a direct path to publish snapshots to S3-compatible storage without relying on OPFS as an intermediate.
Validation