Johannes Millan ed061f90fb fix(sync): clamp future timestamps instead of rejecting ... Operations with timestamps beyond maxClockDriftMs (60s) were being permanently rejected, causing silent data loss when a client's clock was slightly ahead. Now these timestamps are clamped to now + maxClockDriftMs and accepted. A TIMESTAMP_CLAMPED audit log is recorded for debugging. - Add clamping logic in SyncService.processOperation() - Remove future timestamp rejection from ValidationService - Add comprehensive tests verifying clamped values and boundaries - Update integration test to expect acceptance		2025-12-28 12:23:36 +01:00
..
multi-client-sync.integration.spec.ts	fix(sync): clamp future timestamps instead of rejecting	2025-12-28 12:23:36 +01:00
snapshot-skip-optimization.integration.spec.ts	test(sync-server): add tests for snapshot skip optimization	2025-12-17 11:36:04 +01:00