darshankabariya 9812f99010 fix: clamp by range width, not absolute floor, to avoid clock-skew false clamp
Adversarial review found the previous clamp compared the incoming range's
lower bound to a fresh now()-derived selfLowerBound. Because the responder
samples now() later than the initiator, that floor is always slightly
higher, so the clamp fired even between EQUAL-window peers (store<->store),
skipping a sub-second sliver at the bottom of the window and risking
permanent store-fleet inconsistency for a message landing in it.

Compare range WIDTH to our syncRange instead: width is independent of each
peer's now() (both bounds subtract the same now+jitter), so equal windows
never clamp and only a genuinely wider-window peer is clamped, erring
toward reconciling slightly extra rather than dropping. Added an
equal-window near-floor guard test (suite 38/38).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-22 13:18:49 +05:30
..