owain 70c7e5c0a8 Fix VO2 max extraction: values nested under entry['generic'] not top-level ...

The maxmet/daily range query returns entries shaped as:
  {"generic": {"calendarDate": "...", "vo2MaxPreciseValue": 42.7, ...}, ...}

The extractor was looking at the top level of each entry, finding nothing, and
falling through to the single-point training_status fallback every time.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

2026-06-07 23:18:04 +01:00

..

__pycache__

Body

2026-06-07 15:26:54 +01:00

__init__.py

Initial Commit

2026-06-06 13:23:33 +01:00

fit_parser.py

Fix pace sentinel, route map thumbnails, tiled segments, health/dashboard layout

2026-06-07 16:36:54 +01:00

garmin_connect_sync.py

Fix VO2 max extraction: values nested under entry['generic'] not top-level

2026-06-07 23:18:04 +01:00

route_matcher.py

Add segments, YTD stats, route matching fixes, body battery layout, pace fix

2026-06-07 12:01:25 +01:00

wellness_parser.py

Health hypnogram, routes tiles, BB bar chart, segment delta

2026-06-07 18:44:00 +01:00