Marc-André Bombeck 814d3e0179 fix(fold): recompute a stored mean only where the record shows two folds ...

The fold leftovers were told from a person's deletions by syncVersion = 1,
but raw samples are raised in place before a fold takes them (the collision
merge, a changed Health Connect value). The repair then recomputed windows
without those samples and could overwrite a correct mean, also in windows
one run had folded whole.

A tombstone of fold age now counts as a leftover when it carries
syncVersion = 1 or shares its deletion instant with such a tombstone of the
same day; anything else of that age is ambiguous and leaves its window as
stored. Only a window taken in two parts (fold runs at least an hour apart,
or a run and later live samples) is recomputed.

Once the repair has been through an account, the purge may remove class-A
leftovers inside the horizon, so the folds' re-fold of a stored day or hour
leaves it as stored, and the purge takes the fold lock per account. The
fold-lock transactions get an explicit timeout and maxWait, since the lock
wait counts against Prisma's five-second default.

2026-10-09 12:02:25 +02:00

..

fixtures

fix(sharing): keep life events to their owner

2026-10-08 22:37:57 +02:00

integration

fix(fold): recompute a stored mean only where the record shows two folds

2026-10-09 12:02:25 +02:00