Repository navigation
feat(mcp): notify clients when watched match state changes - #58
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.
Add current MCP listen streams and legacy stdio resource subscriptions for match state. Watches use the adapter's authorized viewer and send only resource URIs. Two-second reconciliation catches changes made through REST or another process, including controls that keep the same turn.
Bound shared stream capacity, URI counts, snapshot size, and send duration. Cleanup covers cancellation, unsubscribe, disconnect, and handler drop. Legacy watches use SDK peer identity rather than client-supplied names.
Official-client tests cover initial refresh, quiet unchanged state, external moves, same-turn controls, cancellation, URI filtering, and independent unsubscribe for clients with identical identities.