docs: add critical task for recording stats update mechanism
This commit is contained in:
13
docs/TODO.md
13
docs/TODO.md
@@ -10,6 +10,19 @@
|
||||
**Tests:** 285/286 passing - 99.7% (73% coverage)
|
||||
**Status:** Awaiting infrastructure setup
|
||||
|
||||
### High Priority Tasks
|
||||
|
||||
**🔴 CRITICAL: Recording Stats Update Mechanism**
|
||||
- **Issue:** Fields `recordingsDone` and `recordingsReceived` exist in database but no mechanism to update them
|
||||
- **Requirements:**
|
||||
- Analyze how to update these fields consistently with tier system and ratings
|
||||
- Determine update trigger: after match completion? after rating? automatic on suggestion acceptance?
|
||||
- Ensure consistency with existing rating system
|
||||
- Consider edge cases: declined suggestions, cancelled matches, incomplete ratings
|
||||
- Design API endpoints or automated triggers for stat updates
|
||||
- **Impact:** Tier system fairness algorithm depends on accurate karma tracking
|
||||
- **Dependencies:** Matches API, Ratings API, Recording Suggestions
|
||||
|
||||
### Recently Completed (2025-11-29)
|
||||
- 3-Tier Account System (BASIC/SUPPORTER/COMFORT) with fairness algorithm
|
||||
- Dual Buffer System (prep before + rest after dancing)
|
||||
|
||||
Reference in New Issue
Block a user