Repository navigation
feat(chess): add standard rules engine with draw history - #39
Merged
Merged
Conversation
nosam1998
marked this pull request as ready for review
September 30, 2026 22:43
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.
Adds a pure standard-chess engine with validated FEN imports, UCI actions, all promotions, castling, en passant, explicit current/intended-move draw claims, fivefold and 75-move automatic draws, and a distinct move cap. Played-state exports retain public history so repetition and claims survive replay, forks and observation-only planning.
Validation: shared conformance, initial-position perft through depth 4 (197,281), Kiwipete through depth 3 (97,862), edge rules, history tampering, and atomic rejection tests. All Rust, database, browser, web and existing benchmark workflows pass. Chess throughput calibration and Stockfish integration remain separate units.
Dependency: shakmaty 0.30.1 supplies legal move generation and position validation. Its GPL-3.0-or-later license is recorded and accepted for this GPLv3 project; Cargo.lock is pinned. FEN validation checks structural and rule consistency, without claiming full retrograde reachability proof.