refactor: rimuove terminal controller CLI

CLAUDE.md

@@ -4,15 +4,13 @@ This file provides guidance to Claude Code (claude.ai/code) when working with co
 
 ## Project Purpose
 
-**Segnapunti Anto** is a real-time volleyball scoreboard PWA. An Express/WebSocket server hosts the game state; two separate web interfaces — a **display** (public scoreboard) and a **controller** (operator panel) — stay in sync via WebSocket. A terminal CLI (`cli.js`) provides an alternative controller interface.
+**Segnapunti Anto** is a real-time volleyball scoreboard PWA. An Express/WebSocket server hosts the game state; two separate web interfaces — a **display** (public scoreboard) and a **controller** (operator panel) — stay in sync via WebSocket.
 
 ## Commands
 
 ```bash
-npm run dev          # Vite dev server — display: :5173, controller: :5173/controller.html (proxied on :3001)
-npm run serve        # Build + run production — display: :3000, controller: :3001
-npm run cli          # Terminal controller (connects to production :3000)
-npm run cli:dev      # Terminal controller (connects to dev :5173)
+npm run dev          # Vite dev server — display: :5173/display, controller: :5173/controller
+npm run serve        # Build + run production — display: :3000/display, controller: :3000/controller
 
 npm run test         # Vitest watch mode
 npm run test:all     # All Vitest suites once (unit, integration, component, stress)
@@ -28,19 +26,20 @@ npm run test:e2e:ui  # Playwright with interactive UI
 ```
 Controller (Vue)  ──WebSocket──┐
 Display (Vue)     ──WebSocket──┤── websocket-handler.js ── gameState.js
-CLI (Node)        ──WebSocket──┘
+                               │         │
+                               │         └── persist.js ── .segnapunti/state.json
 ```
 
 All game logic lives in `src/gameState.js` as three pure functions:
 - `createInitialState()` — returns the initial state
-- `applyAction(state, action)` — immutable reducer (deep-clones via `JSON.parse/stringify`)
+- `applyAction(state, action)` — immutable reducer (deep-clones via `structuredClone`)
 - `checkVittoria(state)` — volleyball win conditions (25-point sets with 2-point margin, 15-point final set)
 
-`src/websocket-handler.js` receives actions, validates that the sender is a registered controller (not just a display), calls `applyAction`, then broadcasts the new state to all clients.
+`src/websocket-handler.js` receives actions, validates that the sender is a registered controller (not just a display), calls `applyAction`, broadcasts the new state to all clients, then calls `onStateChange` to persist state to disk.
 
-Two production HTTP servers are started by `server.js` (Express): port 3000 serves `dist/index.html` (display), port 3001 serves `dist/controller.html` (controller). Both share a single WebSocket endpoint at `/ws`.
+`server.js` (Express) serves both interfaces on port 3000: `/display` → `dist/index.html`, `/controller` → `dist/controller.html`. Single WebSocket endpoint at `/ws`.
 
-In development, `vite-plugin-websocket.js` is a custom Vite plugin that embeds the WebSocket server inside the Vite dev server and proxies port 3001 traffic back to Vite.
+In development, `vite-plugin-websocket.js` embeds the WebSocket server inside the Vite dev server with URL rewrite middleware for `/display` and `/controller`.
 
 ## Key Design Constraints
 
@@ -48,6 +47,7 @@ In development, `vite-plugin-websocket.js` is a custom Vite plugin that embeds t
 - **Role-based WebSocket** — clients register as `display` or `controller`; only controllers may send actions.
 - **Immutable state** — `applyAction` never mutates; always returns a new state object.
 - **Single-controller intent** — the design targets one active controller and one display; no conflict resolution exists for simultaneous controllers.
+- **Persistent state** — `src/persist.js` saves state to `.segnapunti/state.json` after every action and loads it on server startup.
 
 ## Test Layout
 
@@ -60,7 +60,3 @@ In development, `vite-plugin-websocket.js` is a custom Vite plugin that embeds t
 | E2E | `tests/e2e/` | Playwright (Chromium, Firefox, Mobile Chrome) |
 
 E2E tests run serially (`workers: 1`) to avoid WebSocket state races. Run `npm run serve` before `npm run test:e2e`.
-
-## Simplification Goals (Current Work)
-
-The intended architecture is: **one host acts as both WebSocket server and display; one connected device acts as controller**. Complexity reduction should be evaluated against this constraint — anything that supports multi-controller scenarios, complex client topologies, or unneeded abstractions is a candidate for removal.