Marc-André Bombeck 530f78dcf5 fix(sync): answer with what a run wrote, not that it completed ...

Six provider syncs returned a bare count, which narrowed their failures away:
a Nightscout window in which every SGV row was refused by a constraint
returned the same 0 as a quiet night, and an Oura or Polar run whose
collections all failed returned 0 too. The routes then answered 200 with a
count and the settings card drew a green tick over it.

Every sync now reports what it imported AND whether any part of it did not
land, and the route resolves the outcome server-side so the web card and the
native client cannot disagree. Google Health keeps its 502 for a run that
failed and wrote nothing, but a run that failed after writing some resources
is now a partial rather than a discarded result. The labs OCR commit carries
the same resolved outcome.

2026-07-27 22:53:43 +02:00

..

__tests__

fix(sync): answer with what a run wrote, not that it completed

2026-07-27 22:53:43 +02:00

client.ts

fix(polar): log envelope-shape drift instead of silently reading it as no data

2026-07-24 21:19:58 +02:00

credentials.ts

style: apply prettier across the tree

2026-06-19 22:20:31 +02:00

response-classifier.ts

fix(polar): lift invalid_grant to reauth and harden the credentials surface

2026-06-15 00:09:22 +02:00

sport-map.ts

test(polar): cover exercise sync, mapper parity, and the shared-ledger legs

2026-07-24 10:10:05 +02:00

sync-workouts.ts

fix(integrations): escalate a long transient failure streak, and scope a success to its own leg

2026-07-26 14:19:13 +02:00

sync.ts

fix(sync): answer with what a run wrote, not that it completed

2026-07-27 22:53:43 +02:00