Repository navigation
feat: add match metadata and paginated history - #21
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 public match metadata at
GET /v1/matches/{id}and bounded, cursor-based local history atGET /v1/matches, filtered by game and lifecycle status. Both derive current status from the durable event log and omit private state, RNG seeds, and reasoning.Add a storage listing port and a parameterized, compile-time-checked SQLite query. Limits bound records scanned before filtering; clients follow
nexteven if a filtered page is empty. This also supplies the durable history index needed for opponent scheduling and restart recovery.Tests cover pagination order, SQL parameterization, completion status, filters, malformed query parameters, restart recovery, and generated OpenAPI response schemas. Rust CI, Web CI, and game benchmarks pass. SQLite query metadata has been generated against the migrated schema and committed; runtime and offline query checks agree.