mitai-jinkendo/backend/calculations
Lars cc76ae677b
All checks were successful
Deploy Development / deploy (push) Successful in 50s
Build Test / lint-backend (push) Successful in 0s
Build Test / build-frontend (push) Successful in 14s
fix: Phase 0b - score functions use English focus area keys
Root cause: All 3 score functions returned None because they queried
German focus area keys that don't exist in database (migration 031
uses English keys).

Changes:
- body_progress_score: körpergewicht/körperfett/muskelmasse
  → weight_loss/muscle_gain/body_recomposition
- nutrition_score: ernährung_basis/proteinzufuhr/kalorienbilanz
  → protein_intake/calorie_balance/macro_consistency/meal_timing/hydration
- activity_score: kraftaufbau/cardio/bewegungsumfang/trainingsqualität
  → strength/aerobic_endurance/flexibility/rhythm/coordination (grouped)

Result: Scores now calculate correctly with existing focus area weights.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-03-28 10:59:37 +01:00
..
__init__.py feat: Phase 0b - Calculation Engine for 120+ Goal-Aware Placeholders 2026-03-28 07:20:40 +01:00
activity_metrics.py fix: Phase 0b - score functions use English focus area keys 2026-03-28 10:59:37 +01:00
body_metrics.py fix: Phase 0b - score functions use English focus area keys 2026-03-28 10:59:37 +01:00
correlation_metrics.py fix: Phase 0b - correct all SQL column names in calculation engine 2026-03-28 08:28:20 +01:00
nutrition_metrics.py fix: Phase 0b - score functions use English focus area keys 2026-03-28 10:59:37 +01:00
recovery_metrics.py fix: Phase 0b - fix remaining calculation bugs from log analysis 2026-03-28 08:50:55 +01:00
scores.py feat: Phase 0b - add nutrition focus areas to score mapping 2026-03-28 10:20:46 +01:00