Repository navigation
feat: add opponent seats with atomic replies and fork overrides - #35
Merged
Merged
Conversation
nosam1998
marked this pull request as ready for review
September 30, 2026 21:56
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.
Interactive matches can assign self, human, open, or opponent seats. Bot openings complete before creation returns, and a caller's move includes automatic replies plus the resulting caller-scoped state. A single compare-and-append commits the human move, bot actions, and complete idempotency receipt; failed searches or concurrent writes leave the batch unapplied.
Assignments and independent planning seeds are recorded for restart and replay. Forks may replace seats. Hidden-information replies omit private actions and diagnostics. Existing records retain external seats by default; all-opponent matches remain rejected until the background runner is installed.
Validation covers hidden-view isolation, rollback on provider failure, validation before persistence, concurrent duplicate requests, complete human/bot games, restart, bot openings, and fork overrides. No new dependencies.