[beekld]

Summary

#489 reset the public DataSourceStatus.StateSince to the current time whenever a synchronizer started, even when State didn't change, and without broadcasting the new status. StateSince is documented as the time State most recently changed. An app that measures how long the SDK has been Interrupted had its clock reset on every failover, and status listeners held a different StateSince than GetStatus().

The reset existed so that each synchronizer gets its own fallback and recovery window. The data system now records when the current synchronizer started in a private field. The fallback and recovery conditions measure from the later of that time and StateSince, so their timing is unchanged. StateSince again changes only when State changes.

---

Note

Overview
Stops resetting public DataSourceStatus.StateSince when a new synchronizer starts without a state change. Previously, starting the next synchronizer after failover rewrote StateSince to “now” (often without broadcasting), which broke apps timing how long the SDK stayed Interrupted and could disagree with status listeners.

Fallback and recovery timing is preserved by recording syncStartedAt when the active synchronizer starts and evaluating fallbackCond / recoveryCond against the later of StateSince and that start time inside conditionAction. restartStatusClock is removed; StateSince is updated only when State changes in maybeUpdateStatus.

A new test asserts StateSince is unchanged when the secondary synchronizer starts after the primary fails.

^{Reviewed by Cursor Bugbot for commit 06f2eda. Bugbot is set up for automated code reviews on this repo. Configure here.}