Repository navigation
feat(mcp): add paginated match history and replay - #54
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.
Expose get_match_history and get_replay as compact paginated MCP tools. Replay output comes from the service's projected event stream, preserving action and reasoning visibility while omitting raw initial state and RNG seeds. History reflects the existing trusted local user's database.
Tests cover filtered page traversal, stable event cursors, hidden reasoning during active games, disclosure after a perfect-information match ends, spectator and seat-override behavior, invalid bounds, output schemas, and replay after reopening storage.