Update HLL Vietnam AI Platform integration with ai-platform.json, extended task lifecycle folders, config-aware runner, lightweight validation, report ignore rules, and platform documentation updates.
87 lines
2.5 KiB
Markdown
87 lines
2.5 KiB
Markdown
---
|
|
id: TASK-XXX
|
|
title: Short task title
|
|
status: pending
|
|
type: platform | frontend | backend | documentation | research
|
|
team: PM | Analista | Backend Senior | Frontend Senior | Arquitecto de Base de Datos | Arquitecto Python | Disenador grafico | Experto en interfaz
|
|
supporting_teams: []
|
|
roadmap_item: foundation
|
|
priority: medium
|
|
---
|
|
|
|
# TASK-XXX - Short task title
|
|
|
|
## Goal
|
|
|
|
Describe the smallest useful objective for this task.
|
|
|
|
## Context
|
|
|
|
Explain where the change happens in HLL Vietnam and why it is needed now.
|
|
|
|
Preserve the current product identity: Spanish-speaking HLL Vietnam community, military/Vietnam/tactical/sober visual direction and controlled repository evolution.
|
|
|
|
## Steps
|
|
|
|
1. Inspect the listed files first.
|
|
2. Apply only the scoped change.
|
|
3. Validate the result and document relevant findings.
|
|
|
|
## Files to Read First
|
|
|
|
List 3 to 6 files that must be reviewed before changing anything.
|
|
|
|
Examples for this repository:
|
|
|
|
- `AGENTS.md`
|
|
- `ai/repo-context.md`
|
|
- `ai/architecture-index.md`
|
|
- `frontend/index.html`
|
|
- `frontend/assets/css/styles.css`
|
|
- `backend/README.md`
|
|
|
|
Rules:
|
|
|
|
- Read these files before implementation.
|
|
- Keep the list small and directly relevant.
|
|
- Prefer existing docs and code that already define the area being changed.
|
|
|
|
## Expected Files to Modify
|
|
|
|
List the files that should change during the task.
|
|
|
|
Rules:
|
|
|
|
- Prefer modifying only these files.
|
|
- If additional files become necessary, explain why in the task outcome or commit message.
|
|
- Do not modify unrelated files.
|
|
|
|
## Constraints
|
|
|
|
- Keep the change minimal.
|
|
- Preserve HLL Vietnam project identity.
|
|
- Do not introduce unnecessary frameworks or dependencies.
|
|
- Do not implement backend functionality unless the task explicitly requires it.
|
|
- Do not expand Elo/MMR, historical workers or RCON server #03 handling unless the task explicitly requires it.
|
|
- Do not overwrite repository-specific context with generic platform template text.
|
|
|
|
## Validation
|
|
|
|
Before completing the task ensure:
|
|
|
|
- scoped checks pass
|
|
- no unrelated files were modified
|
|
- documentation remains consistent with the repository state
|
|
- `git diff --name-only` matches the expected scope
|
|
- integration tests are run when relevant and configured
|
|
|
|
## Outcome
|
|
|
|
Document the validation performed, notable decisions, and any follow-up task that should be created instead of expanding this task.
|
|
|
|
## Change Budget
|
|
|
|
- Prefer fewer than 5 modified files.
|
|
- Prefer changes under 200 lines when feasible.
|
|
- Split the work into follow-up tasks if limits are exceeded.
|