ducoterra
f84c6ebaef
Browser co-op kitchen game: FastAPI + native WebSockets, server-authoritative 20 Hz simulation, in-memory anonymous lobbies, data-driven YAML levels, Canvas 2D vanilla ES-module client with locally authored SVG art and no external CDNs. .agents/PLAN.md records the LOCKED decisions; .agents/user_stories/ holds the 12 flow contracts; .agents/phases/todo/ breaks them into 14 sequential, test-gated phases (71 task files), each leaving the app launchable and the suite green. LLM-Generated: true
1.4 KiB
1.4 KiB
US-02 — Join a lobby with a code
As a friend who was told a 5-character code, I want to type it on my own device and be in the kitchen, so that we can play together from anywhere.
Acceptance criteria
- The landing screen has a Join field accepting the code, case-insensitive,
tolerating whitespace and
l/1-style misreads for excluded characters. - Joining with a valid code puts the player in a seat with a generated display name
(
Cook #2) if none was typed, and broadcasts alobbyupdate to everyone. - Joining a full room shows "this kitchen is full (4/4)" and the room code is kept in the field for a retry.
- Joining an unknown code shows "no kitchen with that code" (no leak of which part failed) and never reveals whether a room exists behind a closed door.
- Joining during
PLAYINGputs the player inSPECTATING(visible "watching" banner) until the nextLOBBY. - A display name is sanitized (control chars stripped, 16-char cap) and is not unique-enforced; two players may share a name.
- The second socket from the same token evicts the first cleanly (no ghost).
- Join → seated takes < 1 s on localhost.
E2E suite
tests/e2e/test_us02_join_by_code.py — two browser contexts: create in A, join in B,
assert both see 2 seats; full-room and bad-code paths.
Phases
05_anonymous_lobbies_and_room_lifecycle, 06_realtime_websocket_protocol,
07_canvas_client_and_hud