fix: harden raw storage and split storage modules - #57
Merged
Conversation
This reverts commit 5a4f040.
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.
Summary
Why
The review found cases where concurrent writers and failed lock publication could strand or lose access to durable raw events. This change keeps
events.jsonlauthoritative, makes lock recovery explicit, and separates derived storage work from the raw append path.Impact
Capture and recovery are safer under concurrent or failed writes. The public storage surface stays intact, while the smaller modules make each storage responsibility easier to test and review.
Validation
npm run typechecknpm testnpm run smokenpm pack --dry-run --cache /tmp/codex-lcm-npm-cache