Marc-André Bombeck 81e1f4cad1 fix(workouts): keep tracks and climb for accounts that already had them ...

Migration 0434 turns the route opt-in on for every account that already
holds a stored workout track, so its tracks keep arriving after the
upgrade; only accounts without one start off.

Workouts stored before this release with a track but no elevation get
their metres climbed written into Workout.elevationM by a one-time
background pass. It runs detached at worker boot, reads one track at a
time with a pause between batches of 100, and keeps its position in
app_settings, so a restart resumes and a finished pass ends at once.

The "starting" health reason is bounded: after five minutes the probe
says plain degraded and the process logs one line, and the time the
background role took to come up is logged either way. The compose
healthcheck's ten-minute start period already keeps those probes from
counting; its comment now says so.

2026-10-21 20:51:13 +02:00

..

fixtures

docs: publish the UI standards in docs/contributing

2026-10-21 19:37:22 +02:00

integration

fix(workouts): keep tracks and climb for accounts that already had them

2026-10-21 20:51:13 +02:00