Repository navigation
fix: correct league UX, showcase state, and engine safety - #73
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.
The league dashboard could show truncated lifetime records, change the champion when a column was sorted, silently reject playback controls, and hide finished games. Engine input and adjudication paths could panic on malformed SFEN or replace checkmate with impasse. This fixes the reviewed issues and related failures at their data and state boundaries.
Tracks Filigree task
keisei-79ca3edc56and the linked review/related correctness issues. No schema migration or data reset is required.Validation:
1bb58a0, including Python 3.12/3.13, Rust, frontend, and normal package imports.Screenshots (synthetic fixtures):