3 Commits

Include renames

Author	SHA1	Message	Date
woggioni	723b3b11cf	Upgrade kaya to 0.0.5 ... kaya 0.0.5 surfaces a vanished websocket peer as kaya.core.WebSocketDisconnect instead of leaking granian's RSGIProtocolClosed: receive() reports a close message so iteration ends normally, sends raise the new exception, and KayaApp.handle_websocket swallows it as normal termination. Adopt it: drop the granian-specific workaround from the platform websocket handler, catch WebSocketDisconnect in the send helper, and model the new semantics in the abrupt-disconnect test (with coverage that a send on a vanished peer is ignored). Regenerate the lock: the eight kaya pins move to 0.0.5 (declared metadata is unchanged) and pip-compile also bumps PyJWT to 2.15.1, a security release with no breaking changes for kaya-oidc's jwt.decode usage. tavolo-platform now floors kaya-core>=0.0.5 (it imports WebSocketDisconnect) and tavolo-app floors kaya-otel>=0.0.5.	2026-09-30 06:38:02 +08:00
woggioni	2910fc4600	Refuse websocket upgrades with HTTP statuses, not close codes ... A close() before accept() carries the HTTP status of the refused upgrade, not a WebSocket close code: RSGI (granian) uses the value verbatim as the response status, so 4401 panicked on the invalid status (InvalidStatusCode) and — granian being built with panic = "abort" — aborted the worker and took the whole app down. ASGI servers answer 403 regardless, and browsers report a refused handshake as an abnormal close (1006), so the 4401/4403/4404 codes never reached clients anyway. Reject 401/404/403 to mirror GET /api/games/{id}, and classify a failed first connection in the game page through the REST API so players still see "session expired" / "game no longer available" instead of a retry loop. Add a regression test asserting every pre-accept rejection uses a status in the HTTP range.	2026-09-29 22:31:41 +08:00
woggioni	4b66407fa4	Split backend into tavolo-platform, tavolo-scopone and tavolo-app packages ... Move the game-independent machinery (lobby, live-game store, websocket, deadline scheduler, match history, leaderboards) into a new tavolo-platform distribution behind a GameEngine contract, the scopone scientifico rules plus a platform adapter into tavolo-scopone, and keep only the composition root in tavolo-app. The three distributions share the tavolo namespace (PEP 420, kaya-style monorepo). Match history becomes fully generic: Match carries the engine's result JSON and MatchPlayer points/details instead of scopone-shaped team columns (migration 3 backfills existing rows). Lobby creation takes an opaque per-game options object and websocket actions dispatch to the session's engine. Tests: platform suite runs against a DummyEngine toy game, scopone keeps the rules tests plus new adapter tests, server/tests covers the wired stack end to end (194 tests, was 143).	2026-09-21 13:04:08 +08:00