Repository navigation
feat(web): add local evaluation report viewer - #105
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.
Model evaluations currently produce JSON without a browser view. Add a Reports page that opens local
gfa tournamentreports, shows standings and rating intervals, and lets users filter, search, and inspect individual games. The Models page links directly to this follow-up step.Imports stay in the current tab. The parser bounds file size and result counts, validates finite ratings and unique identities, and reconciles standings against episode outcomes. Invalid imports preserve the existing report. The example and failure fixtures come from real native-engine runs and are clearly labelled. Native episode IDs are not presented as server replay links.
Validation:
make check-web build-web; all 38 browser tests (including four report tests); production preview at 360, 640, 768, 1024, and 1440 pixels with no horizontal page overflow or browser errors. Browser tests cover pagination, filters, failed policies, downloads, malformed and oversized files, inconsistent results, untrusted names, and keyboard interaction. Repository CI checks must pass before merge.