fix(mcp): gate cloud sync marker on live status - #3198
Draft
reachjalil wants to merge 1 commit into
Draft
Conversation
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
Contributor
|
@reachjalil is attempting to deploy a commit to the Different AI Team on Vercel. A member of the Team first needs to authorize it. |
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
openwork.den.mcp.synconly as token/config freshness metadataopenwork-cloudengine statusconnectedwith the desired revision applied before writing or retaining the markerRoot cause
Cloud MCP reconciliation could retain or write a fresh sync marker from configuration/token state even when OpenCode had not successfully registered
openwork-cloud. Later mounts could interpret that marker as a successful sync and skip repair while the live MCP was failed or absent.Checks
bun test --isolate tests/cloud-mcp-health.test.ts— 15 passedbun test --isolate tests/cloud-mcp-maintenance-gate.test.ts— 4 passedScope and risk
The change is limited to Cloud MCP reconciliation and its focused tests. It does not change Den APIs, protocol routes, TLS, token formats, general MCP behavior, or endpoint fallback behavior. No end-to-end app run or manual UI verification was performed.