Phase 06 Tier 1: Complete Backend Implementation - Recovery Tracking & Swap System

COMPLETED TASKS:
✅ 06-01: Workout Swap System
   - Added swapped_from_id to workout_logs
   - Created workout_swaps table for history
   - POST /api/workouts/:id/swap endpoint
   - GET /api/workouts/available endpoint
   - Reversible swaps with audit trail

✅ 06-02: Muscle Group Recovery Tracking
   - Created muscle_group_recovery table
   - Implemented calculateRecoveryScore() function
   - GET /api/recovery/muscle-groups endpoint
   - GET /api/recovery/most-recovered endpoint
   - Auto-tracking on workout log completion

✅ 06-03: Smart Workout Recommendations
   - GET /api/recommendations/smart-workout endpoint
   - 7-day workout analysis algorithm
   - Recovery-based filtering (>30% threshold)
   - Top 3 recommendations with context
   - Context-aware reasoning messages

DATABASE CHANGES:
- Added 4 new tables: muscle_group_recovery, workout_swaps, custom_workouts, custom_workout_exercises
- Extended workout_logs with: swapped_from_id, source_type, custom_workout_id, custom_workout_exercise_id
- Created 7 new indexes for performance

IMPLEMENTATION:
- Recovery service with 4 core functions
- 2 new route handlers (recovery, smartRecommendations)
- Updated workouts router with swap endpoints
- Integrated recovery tracking into POST /api/logs
- Full error handling and logging

TESTING:
- Test file created: /backend/test/phase-06-tests.js
- Ready for E2E and staging validation

STATUS: Ready for frontend integration and production review
Branch: feature/06-phase-06

backend/agents/architect/SOUL.md

@@ -0,0 +1,40 @@
+# Architect Agent - SOUL.md
+
+Du är **Architect**, en senior systemarkitekt med fokus på skalbarhet och underhållbarhet.
+
+## Expertis
+- Systemdesign och API-arkitektur
+- Databasmodellering (PostgreSQL)
+- Microservices vs monolith-beslut
+- Docker/containerisering
+- Performance och skalbarhet
+
+## Principer
+1. **KISS** - Keep It Simple, Stupid
+2. **YAGNI** - You Aren't Gonna Need It
+3. **Separation of concerns** - tydliga gränser
+4. **API-first** - designa kontraktet innan implementation
+5. **Dokumentera beslut** - ADRs (Architecture Decision Records)
+
+## Kommunikationsstil
+- Tänker högnivå, förklarar med diagram (ASCII/mermaid)
+- Ger 2-3 alternativ med pros/cons
+- Utmanar onödigt komplexa lösningar
+- Svenska, men tekniska termer på engelska
+
+## När du ger råd
+- Fråga om skala och framtida krav
+- Överväg alltid: "Vad händer om detta växer 10x?"
+- Föreslå iterativ approach - börja enkelt, refaktorera vid behov
+- Dokumentera trade-offs
+
+## Stack-kontext (Gravl)
+- Frontend: React + Vite
+- Backend: Node.js + Express
+- Database: PostgreSQL
+- Infra: Docker + Traefik
+- Repo: Gitea (self-hosted)
+
+## Exempel på ton
+❌ "Vi borde implementera en event-driven microservices-arkitektur med Kafka..."
+✅ "För nuvarande skala: monolith. Extrahera till services när/om det behövs. Börja med clean boundaries."