Assignment - Bharathi Krishnan#15
Open
bharathi-everest wants to merge 26 commits into
Open
Conversation
Initial principles for brownfield enhancement, HTTP polling sync, Spec Kit traceability, and deterministic game rules. Co-authored-by: Cursor <cursoragent@cursor.com>
Define host creation, join validation, lobby polling, and host-only start-game requirements with acceptance criteria and quality checklist. Co-authored-by: Cursor <cursoragent@cursor.com>
Include research, data model, REST contracts, quickstart validation, and agent context for Scenario 1 host, polling, and start-game gating. Co-authored-by: Cursor <cursoragent@cursor.com>
Ordered implementation tasks by user story with foundational prerequisites, polling, and host-only start-game gating. Co-authored-by: Cursor <cursoragent@cursor.com>
Add host tracking, join validation, lobby polling, and host-only start game with backend start endpoint and frontend navigation gating. Co-authored-by: Cursor <cursoragent@cursor.com>
001 room setup lobby
Capture name validation, game-start transition, host-as-drawer assignment, and drawer-only secret word visibility before planning. Co-authored-by: Cursor <cursoragent@cursor.com>
docs: discovery of project
Scribble lab v2
…o 2) Capture research decisions, data model, API contract deltas, quickstart validation steps, and viewer-aware snapshot design for drawer-only word visibility. Co-authored-by: Cursor <cursoragent@cursor.com>
Break down name validation, game polling, drawer roles, and drawer-only secret word visibility into 28 ordered, story-mapped implementation tasks. Co-authored-by: Cursor <cursoragent@cursor.com>
Validate and trim player names, assign host as drawer with deterministic secret word, expose word only to drawer via viewer-aware snapshots, and sync roles on the game screen with polling. Co-authored-by: Cursor <cursoragent@cursor.com>
feat: game start and drawer flow (Scenario 2)
Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
feat: implement gameplay interaction (Scenario 3)
Define round end, shared result display, lobby restart, and end-to-end validation requirements for the final game loop phase. Co-authored-by: Cursor <cursoragent@cursor.com>
Define result/restart state model, API contracts, and two-browser validation steps for the final game loop phase. Co-authored-by: Cursor <cursoragent@cursor.com>
Break down result/restart work into phased, story-organized tasks for end-round, shared result UI, lobby restart, and E2E validation. Co-authored-by: Cursor <cursoragent@cursor.com>
Add result room status with host end-round and restart endpoints, in-place result UI on the game screen, and backend tests for the full round lifecycle. Co-authored-by: Cursor <cursoragent@cursor.com>
…tion Scenario 4: Result, restart, and final validation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This branch turns the scaffold-only repo into a playable, HTTP-polling multiplayer drawing game. Work was delivered in four incremental scenarios (merged via PRs), backed by Spec Kit specs, plans, and tasks.
Scenario 1 — Room setup & lobby: Host creates rooms with shareable codes; guests join; lobby shows participants with host indicator; automatic ~2s polling keeps the lobby in sync.
Scenario 2 — Game start & drawer flow: Host-only start with 2-player minimum; room transitions to playing state; deterministic drawer assignment and secret word from starter list; viewer-scoped snapshots hide the word from guessers.
Scenario 3 — Gameplay interaction: Interactive DrawingCanvas for the drawer; stroke sync and clear-canvas via polling; guess submission with scoring; live scoreboard and guess history.
Scenario 4 — Result, restart & validation: Host ends round → in-place result mode (word revealed, canvas hidden); shared final scores/history; host restart returns all players to lobby with round state cleared.
Also includes project discovery notes, Scribble constitution v1.0.0, and Spec Kit tooling (skills, templates, workflows).
Contributor