rgonsal/comunidadhll
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Document RCON-first historical architecture

Browse Source
This commit is contained in:
devRaGonSa
2026-05-19 15:37:50 +02:00
parent 064ea016fd
commit a2ec70220d
6 changed files with 72 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
ai/architecture-index.md
View File

@@ -80,3 +80,6 @@ Community website repository with a static landing in the current phase and a pl
- Comunidad Hispana #03 is disabled from default RCON targets, while existing historical/Elo code and persisted data remain available for explicit future reintroduction. Elo/MMR remains paused and decoupled from backend startup.
- Frontend data consumption should remain progressive, endpoint by endpoint, with static fallbacks preserved during migration.
- The frontend integration strategy is documented in `docs/frontend-data-consumption-plan.md`.
- Historical RCON architecture is RCON-first end to end: session capture, AdminLog ingestion, parsed event storage, materialized matches/player stats and optional profile-snapshot enrichment.
- Public-scoreboard data remains optional enrichment/link source or fallback only; it must not become the normal primary historical path while RCON coverage is available.
- Manual RCON validation commands include `docker compose exec backend python -m app.rcon_admin_log_ingestion --minutes 1440` and `docker compose exec backend python -m app.rcon_historical_worker capture`.

2
ai/repo-context.md
View File

@@ -22,6 +22,8 @@ This repository is in foundation stage. The objective is to grow in a controlled
- Default deployment: `backend` + `frontend`; historical workers are advanced/manual only.
- Live and historical defaults are RCON-first, with public-scoreboard kept only as historical fallback.
- Comunidad Hispana #03 is not part of default RCON targets. Historical/Elo code and persisted data are preserved, while Elo/MMR remains paused and decoupled from backend startup.
- RCON historical data flow is session capture plus AdminLog ingestion, parsed event storage, materialized matches/player stats and optional player profile snapshot enrichment.
- Public scoreboard may enrich links or fill unsupported historical gaps, but it is not the primary historical source when RCON coverage exists.
## Repository Areas

9
ai/tasks/pending/TASK-132-document-rcon-first-historical-architecture.md → ai/tasks/done/TASK-132-document-rcon-first-historical-architecture.md
View File

@@ -1,7 +1,7 @@
---
id: TASK-132
title: Document RCON-first historical architecture
status: pending
status: done
type: documentation
team: PM
supporting_teams:
@@ -84,3 +84,10 @@ HLL Vietnam is building a historical/live data platform for Comunidad Hispana se
- Stage only intended files.
- Commit the completed implementation.
- Push the branch to origin.
## Outcome
- Documented the RCON-first historical architecture in README, backend README, decisions and AI context.
- Covered RCON session capture, AdminLog ingestion/parser/storage, materialized matches/player stats, profile snapshot enrichment, public-scoreboard fallback boundaries, Elo/MMR paused state and Comunidad Hispana #03 disabled defaults.
- Added the requested manual Docker commands for AdminLog ingestion and historical capture.
- Validation: `powershell -ExecutionPolicy Bypass -File scripts/run-integration-tests.ps1` returned exit code 0, but its nested historical UI regression check emitted an existing frontend assertion about the missing recent-match external action label. No frontend/backend behavior files were changed in this documentation-only task.