Correggo documentazione: sync CSI e risultato scout non persistiti server-side

Il CLAUDE.md e la memory affermavano una sincronizzazione CSI e una
persistenza server-side dei risultati partita che non esistono nel
codice: la classifica è un array hardcoded (demo) e il risultato
scoutato vive solo nel localStorage di chi segna.

CLAUDE.md

@@ -92,8 +92,13 @@ load-bearing, not style preferences:
 - Stats/badges/standings are "write once, read many": computed and persisted once (e.g. at match
   end), never recomputed on every page open.
 - Live match scouting: only the scoring user writes; everyone else reads already-saved data.
-- CSI league data is synced periodically server-side into a local table; the app only ever reads
-  from the internal DB, never the CSI site directly.
+- CSI league data is currently a **hardcoded placeholder** array in `src/lib/crapp-data.ts`
+  (`classifica`, `storicoMatch`), explicitly marked "(demo)" in the UI — no real sync exists yet,
+  this is planned/open work, not an existing pattern to copy.
+- A scouted match result (`ScoutMatch`, from `scout.tsx` / `scout-store.ts`) is saved **only to
+  the scoring device's `localStorage`** (key `crapp-scout-v1`), never to Supabase — only the
+  in-progress resume state goes to the `scout_live` table. So today a match result is not shared
+  across devices/users at all.
 - Push notifications only for high-value events (convocations, training/match reminders, ball-duty
   turn, final result) — no chat/photo/video features.