fix: coordinate concurrent edge writes - #71
Merged
Conversation
creatornader
force-pushed
the
fix/edge-write-coordinator
branch
from
July 26, 2026 21:09
52dd85b to
d8be268
Compare
creatornader
force-pushed
the
fix/edge-write-coordinator
branch
from
July 26, 2026 21:18
d8be268 to
163c48d
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.
Replace the unsafe file-lock attempt with a token-checked write lease stored in the shared SQLite edge database. The lease serializes local edge mutations across concurrent MCP processes, recovers expired crashed-writer ownership safely, and keeps gateway calls outside the write boundary.\n\nTests cover concurrent schema upgrades, 21-process post/get/ack traffic, live and crashed writer leases, WAL checkpointing, restart, and clean-home full verification.