marvinandClaude Opus 5.5
9ffee8b952
- New docs/09-limits-and-performance.md: principles, all protection layers, what players see, configuration reference, measurements, tuning guide, monitoring and how to test - Server chapter summarises the limits and links to chapter 9; circuit breaker description and AI_MAX_INFLIGHT default corrected - Architecture: new files in the layout, design decisions for load handling; docs index lists chapter 9 - Protocol, AI and operations chapters link to chapter 9; test counts - Root and component READMEs describe the limits and settings Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
wizard_website
React + TypeScript frontend (Vite). All component styles are CSS modules
(*.module.css); the design tokens live on the .app root in
src/App.module.css.
npm install
npm run dev # http://localhost:5173, proxies /api/* (incl. websocket) to localhost:8000 without the /api prefix
npm run build
npm run lint
The app is built with relative asset paths and connects to ../api/ws relative to its own URL
(/wizard/website/ → /wizard/api/ws). Set WIZARD_SERVER_URL to proxy to another server in
development, or VITE_WS_URL at build time to use an absolute websocket URL instead.
Structure
src/api/— protocol types and theuseWizardhook (websocket connection, reconnect with a per-tab session token, game state, server load status; slow retries when the server is full)src/components/— reusable UI (button, playing card, modal, toasts)src/screens/HomeScreen— enter a name, create or join a lobby (Create is disabled with a notice while the server is busy)src/screens/LobbyScreen— lobby code, players, AI players, rule options, start (disabled with a notice while the server is busy)src/screens/GameScreen— the table: seats, trick, hand, bidding, trump choice, scoreboard, round summary, game over