updating docs

documentation/roadmap.md

@@ -18,7 +18,7 @@ Each phase produces a working increment. Nothing is built speculatively.
 - [x] Configure Drizzle ORM + connection to local PostgreSQL
 - [x] Write first migration (empty — validates the pipeline works)
 - [x] `docker-compose.yml` for local dev: `api`, `web`, `postgres`, `valkey`
-- [x] `.env.example` files for `apps/api` and `apps/web`
+- [x] Root `.env.example` for local dev (`docker-compose.yml` + API)
 
 ---
 

documentation/spec.md

@@ -7,7 +7,7 @@
 
 ## 1. Project Overview
 
-A vocabulary trainer for English–Italian words. The quiz format is Duolingo-style: one word is shown as a prompt, and the user picks the correct translation from four choices (1 correct + 3 distractors of the same part-of-speech). The long-term vision is a multiplayer competitive game, but the MVP is a polished singleplayer experience.
+A vocabulary trainer for English–Italian words. The quiz format is Duolingo-style: one word is shown as a prompt, and the user picks the correct translation from four choices (1 correct + 3 distractors of the same part-of-speech). The app supports both singleplayer and real-time multiplayer game modes.
 
 **The core learning loop:**
 Show word → pick answer → see result → next word → final score
@@ -29,13 +29,13 @@ The vocabulary data comes from WordNet + the Open Multilingual Wordnet (OMW). A
 - Multiplayer mode: create a room, share a code, 2–4 players answer simultaneously in real time, live scores, winner screen
 - 1000+ English–Italian nouns seeded from WordNet
 
-This is the full vision. The MVP deliberately ignores most of it.
+This is the full vision. The current implementation already covers most of it; remaining items are captured in the roadmap and the Post-MVP ladder below.
 
 ---
 
 ## 3. MVP Scope
 
-**Goal:** A working, presentable singleplayer quiz that can be shown to real people.
+**Goal:** A working, presentable vocabulary trainer that can be shown to real people (singleplayer and multiplayer), with a production deployment.
 
 ### What is IN the MVP
 
@@ -45,16 +45,14 @@ This is the full vision. The MVP deliberately ignores most of it.
 - Clean, mobile-friendly UI (Tailwind + shadcn/ui)
 - Global error handler with typed error classes
 - Unit + integration tests for the API
-- Local dev only (no deployment for MVP)
+- Authentication via Better Auth (Google + GitHub)
+- Multiplayer lobby + game over WebSockets
+- Production deployment (Docker Compose + Caddy + Hetzner) and CI/CD (Forgejo Actions)
 
 ### What is CUT from the MVP
 
 | Feature                         | Why cut                                |
 | ------------------------------- | -------------------------------------- |
-| Authentication (Better Auth)    | No user accounts needed for a demo     |
-| Multiplayer (WebSockets, rooms) | Core quiz works without it             |
-| Valkey / Redis cache            | Only needed for multiplayer room state |
-| Deployment to Hetzner           | Ship to people locally first           |
 | User stats / profiles           | Needs auth                             |
 
 These are not deleted from the plan — they are deferred. The architecture is already designed to support them. See Section 11 (Post-MVP Ladder).
@@ -81,14 +79,14 @@ The monorepo structure and tooling are already set up. This is the full stack.
 | Deployment   | Docker Compose, Caddy, Hetzner | ✅          |
 | CI/CD        | Forgejo Actions                | ✅          |
 | Realtime     | WebSockets (`ws` library)      | ✅          |
-| Cache        | Valkey                         | ❌ post-MVP |
+| Cache        | Valkey                         | ⚠️ optional (used locally; production/state hardening) |
 
 ---
 
 ## 5. Repository Structure
 
 ```text
-vocab-trainer/
+lila/
 ├── .forgejo/
 │   └── workflows/
 │       └── deploy.yml              — CI/CD pipeline (build, push, deploy)
@@ -154,7 +152,6 @@ vocab-trainer/
 ├── scripts/                            — Python extraction/comparison/merge scripts
 ├── documentation/                      — project docs
 ├── docker-compose.yml                  — local dev stack
-├── docker-compose.prod.yml             — production config reference
 ├── Caddyfile                           — reverse proxy routing
 └── pnpm-workspace.yaml
 ```
@@ -311,12 +308,20 @@ After completing a task: share the code, ask what to refactor and why. The LLM s
 
 All are new tables referencing existing `terms` rows via FK. No existing schema changes required.
 
-### Multiplayer Architecture (deferred)
+### Multiplayer Architecture (current + deferred)
 
-- WebSocket protocol: `ws` library, Zod discriminated union for message types
+**Implemented now:**
-- Room model: human-readable codes (e.g. `WOLF-42`), not matchmaking queue
+
-- Game mechanic: simultaneous answers, 15-second server timer, all players see same question
+- WebSocket protocol uses the `ws` library with a Zod discriminated union for message types (defined in `packages/shared`)
-- Valkey for ephemeral room state, PostgreSQL for durable records
+- Room model uses human-readable codes (no matchmaking queue)
+- Lobby flow (create/join/leave) is real-time over WS, backed by PostgreSQL for durable membership/state
+- Multiplayer game flow is real-time: host starts, all players see the same question, answers are collected simultaneously, with a server-enforced 15s timer and live scoring
+- WebSocket connections are authenticated (Better Auth session validation on upgrade)
+
+**Deferred / hardening:**
+
+- Valkey-backed ephemeral state (room/game/session store) where in-memory state becomes a bottleneck
+- Graceful reconnect/resume flows and more robust failure handling (tracked in Phase 7)
 
 ### Infrastructure (current)
 
@@ -331,7 +336,7 @@ See `deployment.md` for full infrastructure documentation.
 
 ---
 
-## 12. Definition of Done (MVP)
+## 12. Definition of Done (Current Baseline)
 
 - [x] API returns quiz terms with correct distractors
 - [x] User can complete a quiz without errors
@@ -340,6 +345,9 @@ See `deployment.md` for full infrastructure documentation.
 - [x] No hardcoded data — everything comes from the database
 - [x] Global error handler with typed error classes
 - [x] Unit + integration tests for API
+- [x] Auth works end-to-end (Google + GitHub via Better Auth)
+- [x] Multiplayer works end-to-end (lobby + real-time game over WebSockets)
+- [x] Production deployment is live behind HTTPS (Caddy) with CI/CD deploys via Forgejo Actions
 
 ---