Multiple words per turn rule for Russian games #46
Reference in New Issue
Block a user
Delete Branch "feature/single-word-rule"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Adds a per-game rule chosen on New Game for Russian variants (default off = the single-word rule; on = standard Scrabble). Off, only the main word along the play direction is validated and scored; perpendicular cross-words are ignored, including in robot move generation. English games always send standard and show no toggle; the rule rides every create/enqueue request and joins the matchmaking key, so games and auto-match stay one uniform path.
Engine dependency: consumes
scrabble-solverv1.1.0 (PlayOptions{IgnoreCrossWords}, already tagged + pushed).Scope: engine wrapper, game domain + store (new
games.multiple_words_per_turncolumn, baseline migration edited — DB not versioned, jet regenerated), lobby (invitation row + matchmaker queue key), edge FlatBuffers (EnqueueRequest/CreateInvitationRequest, Go + TS regenerated) + gateway, UI New Game toggle (Russian-only). Tests: backend engine/matchmaker, UI unit + Playwright e2e (solver corner-case + GCG fixtures ship in v1.1.0). Docs + PRERELEASE tracker updated.Contour note: schema changed, so the test-contour DB must be wiped (
DROP SCHEMA backend CASCADE+ restart backend) for goose to re-run the baseline with the new column.Add a per-game rule chosen on New Game for Russian variants (default off = the single-word rule; on = standard Scrabble). Off, only the main word along the play direction is validated and scored; perpendicular cross-words are ignored, including in robot move generation. The rule rides every create and enqueue request and joins the matchmaking key, so games and auto-match stay one uniform path; "Russian-only" is a UI affordance (English always sends standard and shows no toggle). - Engine: consume scrabble-solver v1.1.0's PlayOptions{IgnoreCrossWords}, threaded through engine.Options.MultipleWordsPerTurn -> playOpts() into validate, score and generate. - Backend: thread the flag through game CreateParams/Game + store (games column), lobby InvitationSettings + invitation row, and the matchmaker queue key (variant + rule); persisted, so a rebuilt-from-journal game keeps it. Baseline migration gains multiple_words_per_turn (DB not versioned); jet regenerated. - Edge: multiple_words_per_turn added to the EnqueueRequest / CreateInvitationRequest FlatBuffers tables (Go + TS regenerated) and threaded through the gateway. - UI: a "Multiple words per turn" toggle on New Game, shown for Russian variants only (auto-match and friend invite), default off; English silently sends standard. - Tests: backend engine/matchmaker; UI unit (gating) + Playwright e2e (solver corner-case + GCG fixtures ship in v1.1.0). Docs + PRERELEASE tracker updated.