Garmin/Coros ingestion

[jessephus]

Problem

Garmin or Coros ingestion

Why this was deferred from the MVP

Garmin and Coros access are harder to automate safely and cleanly than Strava, so it should not block the first release.

Proposed future approach

Start with a supported API or a user-mediated import path that keeps raw files and tokens protected.

Security and privacy considerations

• Encrypt any stored Garmin or Coros tokens or raw files.
• Do not rely on scraping or unsupported session reuse.

Acceptance criteria

• A user can connect Garmin or Coros and import Garmin or Coros workout files and other training related health data such as training load, sleep, resting heart rate, and heart rate variability.
• Garmin or Coros workouts normalize into the same canonical workout model as Strava data.

Open questions

• What official Garmin or Coros access is realistically available for a personal app?