Use Number.isNaN instead of global isNaN in dates utility

[pavankumar-vh]

Overview

Fix type safety issue in common/src/util/dates.ts by using Number.isNaN instead of the global isNaN function.

Bug Description

The global isNaN() function coerces non-numbers to numbers first, which can lead to unexpected results.

Fix

Changed isNaN(diffMs) to Number.isNaN(diffMs) for more predictable and safer type checking.

Testing

No existing tests for this function, but the fix improves type safety.

Files Changed

• common/src/util/dates.ts - Use Number.isNaN instead of global isNaN

Scope

This change only touches common/ which is an approved contribution area per the Contributing Guide.

[codebuff-team]

This is a minor but legitimate improvement. diffMs is already a number (result of subtracting two .getTime() calls), so Number.isNaN is strictly more correct here since it skips the coercion step of the global isNaN. Behaviorally identical in this specific case since diffMs is always a number, but using Number.isNaN is better practice and guards against future refactors that might pass a non-number in.

The change is small, scoped, and safe - easy to port by hand. No tests needed for a one-line type-safety tightening like this. Nothing to flag as risky.