F001 — Hand Count Rules

​

Business Rule

• Default: 3 hands
• Minimum: 2 hands
• Reference client UI maximum: 4 hands (configurable via settings — see F030)
• Theoretical backend maximum: 23 hands — floor((52 − 5) ÷ 2) — 52 cards in a standard deck, 5 reserved for community cards, 2 hole cards per hand

​

Technical Design

​

UMA client (platform.js)

var NUM_HANDS = 3; // default, hardcoded in platform.js

maxHandCount: NUM_HANDS,     // tells the GDK how many hand panels to render
numberOfHands: NUM_HANDS,    // sent in each /api/tables/:id/deal request

window._holeCards = holeState.hands; // string[] — one 4-char entry per hand, e.g. ['AcKd','7h2s','QsJd']

​

Deck constraint derivation

52 cards in deck
−  5 community cards
= 47 available for hole cards
÷  2 cards per hand
= 23.5 → floor = 23 maximum hands

​

Hand indexing

​

Acceptance Criteria

• AC1 — After page load and initialisation, window._holeCards.length equals the configured hand count (default: 3)
• AC2 — Each entry in _holeCards is exactly 4 characters (two 2-char card tokens, e.g. AcKd)
• AC3 — Hand count is within the valid range: ≥ 2 and ≤ 23
• AC4 — No card appears more than once across all hands (deck integrity — no duplicates)

​

Version Parity

​

Known Discrepancies

​

Test Coverage

VERSION=uma npx playwright test tests/features/F001-hand-count.spec.ts --project=features --workers=1