fix: serialize shared edge writes - #70
Closed
creatornader wants to merge 1 commit into
Closed
Conversation
Owner
Author
|
Closing: review found a stale-lock ownership race in the initial write-file coordinator. The replacement requires a properly versioned edge schema migration and contract update. This PR must not merge. |
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.
Summary
Serialize local gateway-edge mutations across concurrent MCP processes with a short-lived crash-recoverable lock. The gate never covers remote gateway calls.
Verification
npm run checkreaches the pre-existing server-factory failure on both this branch andmainbecause the active environment supplies a gateway backend config to an incomplete-config fixture.