chore(docs): drop session logs, add ADR home and a doc policy

AGENTS.md

@@ -20,7 +20,7 @@ Billard-system/
 ├─ frontend/        # Angular 22 application (src/app: core, features, shared)
 ├─ camera-bridge/    # Local LAN camera bridge (Node): discovery + CORS proxy for go2rtc
 ├─ deploy/          # Nginx config, deployment guide
-├─ docs/            # Guides, screenshots, specs (docs/specs/)
+├─ docs/            # Guides, specs, ADRs (docs/specs/, docs/adr/)
 ├─ .opencode/       # AI home: agent/, command/, skills/ (tracked; local plugin scaffold ignored)
 ├─ .github/         # CI/CD workflows
 ├─ Dockerfile       # Multi-stage single-image build
@@ -59,6 +59,17 @@ Angular 22 SPA in `frontend/src/app` (`core/` auth/API/SignalR/models, `features
 - `opencode.json` holds instructions, MCP servers and permissions. Skills, agents and commands need no config — opencode auto-discovers `.opencode/`.
 - `AGENTS.md` is the single source of truth; `docs/specs/` holds details.
 
+## Documentation Policy
+
+Docs capture decisions and current state, never session narration.
+
+- **Allowed:** `README` (how to run), `docs/adr/NNN-*.md` (one decision: context, options, decision,
+  consequences), `docs/specs/*.md` (current design and business rules), runbooks (`DEPLOY.md`, …)
+  and any current audit/security doc.
+- **Forbidden:** phase reports, progress logs, "what I did" narration and per-session summaries.
+  When a change needs a durable record, update the relevant spec or add an ADR — do not create a
+  report file. This applies to AI output too.
+
 ## Working Rules For This Repo
 - Language: all code, comments, XML docs, tests, commit messages, PR titles/descriptions, docs (`README`, `docs/`, `AGENTS.md`), and AI output must be in English. Only user-facing UI strings may be in Spanish (via i18n files), never hardcoded Spanish in code/comments.
 - Prefer small, focused changes.

docs/adr/README.md

@@ -0,0 +1,12 @@
+# Architecture Decision Records
+
+One file per irreversible or costly decision: `NNN-title.md` with **Context**, **Options**,
+**Decision** and **Consequences**. Written by the human, in a few paragraphs — not generated as a
+report.
+
+Use an ADR when a choice is hard to reverse or future-you needs the *why* (token strategy, schema,
+real-time transport, deployment). For everyday changes, update the relevant [spec](../specs/) and
+the code instead.
+
+To backfill: the opaque 30-day sliding token sessions (vs JWT) and the SQLite domain model / EF
+outbox shape are good first candidates.

docs/specs/folder-structure.md

@@ -6,8 +6,7 @@ c:\Dev\Billard-system\
 │   ├── 00-project-overview.md
 │   ├── 01-architecture.md
 │   ├── 02-tech-stack.md
-│   ├── ...
-│   └── progress.md
+│   └── ...
 ├── backend/                            # Solución C# / .NET 9
 │   ├── BilliardSystem.sln
 │   ├── src/

docs/specs/roadmap.md

@@ -7,7 +7,14 @@
    - Promedio de carambolas por partida y tacada máxima.
    - Gráficas de rendimiento histórico por jugador y por mesa.
    - Tiempos de ocupación pico por día, semana y mes.
-2. **Integración con Cámaras IP y Múltiples Ángulos**:
+
+2. **Hardening pendiente** (ver [known-issues.md](known-issues.md)):
+   - Autenticación JWT real (hoy token opaco).
+   - Paginación/filtros de historial y auditoría.
+   - Pruebas de integración frontend.
+   - Pasar `EnsureCreatedAsync` a migraciones EF.
+
+3. **Integración con Cámaras IP y Múltiples Ángulos**:
    - Soporte para transmisión RSTP / WebRTC desde cámaras de red IP.
    - Selección de múltiples cámaras por mesa (ej. cámara superior + cámara lateral).
    - _Estado 2026-09-30_: primera versión en LAN (descubrimiento + WebRTC + auto-H.264) en [ip-cameras.md](ip-cameras.md). Pendiente: bridge por HTTPS para usarlo desde otros dispositivos y selección por mesa.