Fix NaN Handling in processCommitTimestamps

[tmdeveloper007]

Summary of What Has Been Done

Added a guard to skip invalid date strings in processCommitTimestamps. When new Date(dateString) produces an Invalid Date, isNaN(date.getTime()) is now checked before reading hour. Invalid dates are skipped entirely instead of being silently classified as "night".

Changes Made

• utils/dateHelpers.ts: Added isNaN(date.getTime()) guard in processCommitTimestamps

Impact it Made

• Prevents malformed timestamps from corrupting time-of-day metrics
• Fixes silent data classification bug

Closes #8842

Note: Please assign this PR to the tmdeveloper007 account.

[retenta-bot]

This pull request addresses the handling of invalid date strings in the processCommitTimestamps function, ensuring that NaN values do not corrupt time-of-day metrics. This aligns with previous decisions made regarding this issue, which emphasized the importance of preventing silent data classification bugs. Thank you for your contribution, and feel free to reach out if you have any questions!

[github-actions]

📦 Next.js Bundle Size Report (Gzipped Sizes)

✨ No significant bundle size changes detected.

📊 Summary of Totals

Category	PR Size	Base Size	Difference
Total JS	4939.27 KB	4939.27 KB	0 B
Total CSS	348.46 KB	348.46 KB	0 B

[Aamod007]

Nice catch! Adding the \isNaN(date.getTime())\ check right after parsing the date string in \utils/dateHelpers.ts\ is a small but critical improvement. It cleanly prevents malformed timestamps from being misclassified as night commits. Thank you for fixing this silent classification bug. Looks good to me!