PROBLEM: Simple full_rest/active_recovery model doesn't support context-specific rest days (e.g., strength rest but cardio allowed). SOLUTION: JSONB-based flexible rest day configuration. ## Changes: **Migration 010:** - Refactor rest_days.type → rest_config JSONB - Schema: {focus, rest_from[], allows[], intensity_max} - Validation function with check constraint - GIN index for performant JSONB queries **Backend (routers/rest_days.py):** - CRUD: list, create (upsert by date), get, update, delete - Stats: count per week, focus distribution - Validation: check activity conflicts with rest day config **Frontend (api.js):** - 7 new methods: listRestDays, createRestDay, updateRestDay, deleteRestDay, getRestDaysStats, validateActivity **Integration:** - Router registered in main.py - Ready for weekly planning validation rules ## Next Steps: - Frontend UI (RestDaysPage with Quick/Custom mode) - Activity conflict warnings - Dashboard widget Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>