[JonasFocus]

Summary

The host can choose Casual (static 10/20) or Turbo (blinds rise every 10 hands) between hands, and the table header shows the current and next blinds.

Changes

• Add a host-only setPace intent, accepted only between hands. Casual keeps 10/20. Turbo steps through 10/20, 20/40, 30/60, 50/100, 100/200 and 200/400, ten hands per level, then holds.
• Carry the next hand's blinds in the lobby state, so a level change applies at the deal and never mid-hand. Levels count hands since the pace was chosen, not wall-clock time.
• Show "Next: 20/40 in 3 hands" under the blinds in the table header, add Casual / Turbo buttons for the host in the lobby panel, and scale the raise chips to the current big blind.

Why

Static 10/20 blinds with 2000 stacks drag once stacks get deep. A hand-count clock keeps pressure on without a slow hand skipping a level.

Testing

• Unit tests for the level table, the hand-boundary timing, host-only and lobby-only checks, the min raise at a raised level, and intent parsing.
• pnpm lint, pnpm typecheck, pnpm test (345 passing) and pnpm build pass.
• Smoke test against node server/index.ts with two ws clients: a guest's setPace is rejected, the host's switches to turbo, the next hand posts 10/20 with "next 20/40 in 10", and setPace mid-hand is rejected.

Notes

SMALL_BLIND and BIG_BLIND now mean the opening blinds; game logic reads the current blinds from state.blinds.

Closes #59

[vercel]

Deployment failed for project game-time with the following error:

Resource is limited - try again in 24 hours (more than 100, code: "api-deployments-free-per-day").

Learn More: https://vercel.com/cloverings1s-projects?upgradeToPro=build-rate-limit