The time-sync feature computed a server clock offset and warned the user about drift, but initializeTimeSync() — the function that actually patches global Date to apply the offset — was never called anywhere in the codebase. This meant all timestamps (including chat message createdAt) used the raw, uncorrected system clock, causing messages to sort incorrectly when the user's clock was skewed. Changes: - Call initializeTimeSync() in js/app/src/polyfills.tsx, which runs before React mounts and before any chat message can be created. - Export initializeTimeSync from @streamplace/components barrel. - Add idempotency guard to initializeTimeSync to prevent double-patching. - Fix checkClockDrift to use OriginalDate instead of patched Date, so drift detection still measures the real system clock after the patch is active (otherwise it would always report ~0 drift). - Fix getSyncedDate to use OriginalDate.now() to avoid double-applying the offset once the monkeypatch is active. - Raise CLOCK_DRIFT_THRESHOLD_MS from 5s to 1h since auto-correction now handles smaller drifts; only notify the user for severe drift. - Update toast message to reflect that times are auto-corrected.