Add expected draws visualization - #202
Open
FL385 wants to merge 1 commit into
Open
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
1 participant
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.
Summary
Adds an expected-draws visualization tile for real-time analysis. The tile prioritizes the latest AI-suggested discard when available, then shows comparable algorithmic candidates, expected incoming tiles, win rate, expected points, EV, and possible yaku names.
Also adds a working report documenting current tile-analysis visualization modules and future module ideas using the same implementation pattern.
Rebase / Conflict Resolution
Rebased onto the latest upstream v3 and resolved the layout conflict in frontend/src/tiles/defaults.ts by keeping the upstream Board tile and placing the Expected Draws tile in non-overlapping positions across 4p/3p breakpoints.
Validation
The remaining failing test is bot::runtime::tests::repoint_venv_rewrites_symlink_and_pyvenv_cfg, unrelated to this PR. On macOS it appears to compare /var and /private/var temp paths after canonicalization.