Add sample scenario data and reporting updates

PRODUCTION_IMPLEMENTATION.md

@@ -30,6 +30,7 @@ This document resolves earlier undecided implementation details with proposed v1
 | `mockups/db/001_initial.sql` through `006_daily_health_reports.sql` | Starting relational model and historical migrations. Extend it deliberately; do not assume the sample schema is sufficient for live ingestion. |
 | `mockups/tests/` | Existing calculation, isolation, retry-adjacent integrity, pagination, and missing-data examples to preserve as production contract tests. |
 | `mockups/realistic_seed.py`, `db/seed*.sql`, `SAMPLE_DATA.md` | Development fixtures only. Never seed synthetic players, inferred sample source labels, or invented pass purchase dates into production. |
+| `mockups/scenario_seed.py`, `mockups/sample_scenarios.py` | Current three-genre scenario generator: stable social game, declining racer, and breakout co-op RPG with distinct latent personalities and catalogs. Playstyle/acquisition tags are fictional fixture metadata; preserve the ability to inspect custom fields without pretending this is a production behavior classifier. |
 | `start_dashboard.py`, `start-dashboard.bat` | Windows development convenience only; not the production process supervisor. |
 
 The temporary Python HTTP server, unprotected local endpoints, sample credentials, prototype API-key controls, SVG chart implementation, in-memory scheduler, and simulated Join button are **not production implementations**.