woggioni/tavolo

Fork 0

Files

T

History

woggioni 353f012906

CI / Build and push docker image (push) Successful in 5m35s

Details

Add briscola chiamata

Five-player briscola with a descending calling auction and a secret
partner. Starting with the player after the dealer, each player bids a
lower rank (A > 3 > K > H > J > 7 > 6 > 5 > 4 > 2) or passes; once the
standing bid is the two the auction continues on points (62, 64, ...).
The last player standing must bid, and the winner names any card of the
won rank: its holder is the secret partner, or the caller plays alone
when it is one of their own cards, and its suit becomes the trump. The
calling side must reach 61 (or the raised target); a 60-60 deal with the
plain target is a patta and is replayed. A match is a single deal, so
the caller and partner (or the lone caller) against the other players
map onto the platform's two-team result, Elo and match history.

The rules live in tavolo.briscola.chiamata with the
BriscolaChiamataEngine adapter registered alongside the other briscola
variants; the partner's role and the side totals stay hidden until the
called card is played. The web client gets a five-seat table, the
auction panel with legal bids and point raises, the call picker, the
reveal bands and a chiamata-aware final summary.

2026-10-08 21:50:56 +08:00

src/tavolo

Add briscola chiamata

2026-10-08 21:50:56 +08:00

pyproject.toml

Add briscola: classic two-player and briscola a quattro

2026-10-06 14:08:25 +08:00

README.md

Add briscola: classic two-player and briscola a quattro

2026-10-06 14:08:25 +08:00

README.md

tavolo-app

The deployable tavolo application: the composition root wiring tavolo-platform to the tavolo-scopone and tavolo-briscola games.

app.py — assembles the KayaApp (session/OIDC/Tortoise/OpenAPI mixins plus PlatformMixin and the deadline scheduler), registers the ScoponeEngine, BriscolaEngine and BriscolaQuattroEngine with their configured timeouts, and exposes tavolo.app:app for granian.
config.py — environment-driven frozen Settings.
telemetry.py — the optional OpenTelemetry wiring beyond kaya-otel: meter/tracer/logger providers, the tavolo.active_users/tavolo.ongoing_games gauges (polled from the stores), process/CPython metrics via opentelemetry-instrumentation-system-metrics, Postgres/Redis query spans via the asyncpg/redis instrumentations, and OTLP log export.
aerich_config.py — Tortoise ORM configuration consumed by the aerich CLI (migrations live in server/migrations/; aerich itself is configured via the [tool.aerich] section of server/pyproject.toml).
logging_config.py — logging setup.
static.py — SPA shell hosting for the compiled frontend.

Development (from `packages/tavolo-app/`)

.venv/bin/python -m mypy --namespace-packages --explicit-package-bases \
  src/tavolo/app.py \
  src/tavolo/config.py \
  src/tavolo/telemetry.py \
  src/tavolo/static.py \
  src/tavolo/aerich_config.py \
  src/tavolo/logging_config.py

End-to-end coverage of the wired stack lives in server/tests/.

README.md

tavolo-app

Contents

Development (from packages/tavolo-app/)

Development (from `packages/tavolo-app/`)