Repository navigation
Version the durable-wake repair for installed MCP verification - #362
Merged
Merged
Conversation
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.
Give the merged #360 future-wake repair a distinct installed identity,0.22.0.dev1. The existing MCP-catalog refresh gate compares the server-reported version; leaving every build atdev0 cannot prove a resident connection upgraded.
Version metadata and release notes only; wake behavior is already merged in PR361, with1728tests passing on both Python versions. Source compile, policy wiring and whitespace checks pass. No wake schema, resource grant, recurrence default or native binary change. Plan0176 and #360 retain the live repair/connection-verification boundary.
Need help on this PR? Tag
@codesmith-botwith what you need.