CI / Build and push docker image (push) Successful in 2m6s
Partnership games go to 21: scopone scientifico (the tournament target) and scopa a quattro, while two-player scopa keeps its usual 11. The scopa package resolves the default from the player count and exposes a per variant options_schema default, so the lobby creation form shows the right value without frontend changes.
tavolo-scopone
Scopone scientifico — the four-player, fixed-partnership Italian card
game — as a tavolo-platform game
implementation.
Contents
state.py—ScoponeState(pure game data: phases, players, hands, table, scores, deadlines),PlayerState,Card,Move, with JSON (de)serialization. No session envelope, no transport, no I/O.engine.py— the pure rules engine: deck, legal captures, plays, auto-play, hand scoring (carte, denara, settebello, primiera, scope, napola), the optional asso pigliatutto capture, hand-end acknowledgements. Deterministic and I/O-free apart from logging, so the whole rule set is unit-testable.errors.py— scopone-specific errors (CardNotInHand); every other failure mode is a sharedtavolo.platform.errorssubclass.plugin.py—ScoponeEngine(GameEngine): the platform-facing adapter. It translates create/join/websocket actions/deadlines into rules-engine calls and back, validates thetarget_score/napola/asso_pigliatuttocreation options (the match target defaults to the traditional 21 points), and extracts theMatchResult(teams, winner, per-player scores and the match summary persisted as the match's JSONresult).
Timeouts are constructor arguments (turn_timeout_seconds,
hand_ack_timeout_seconds), wired from the environment by the
application composition root.
Development (from server/)
.venv/bin/python -m unittest discover -s packages/tavolo-scopone/tests
.venv/bin/python -m mypy -p tavolo.scopone
test_engine.py covers the pure rules; test_plugin.py covers the
platform contract (actions, deadlines, serialization, results).