fix: prevent ghost changes when SSL data is empty or invalid

[manganate006]

Summary

• Fix ghost changes being recorded in domain_updates when SSL certificate fetch fails or returns empty data
• Skip recording changes when both old and new values are empty
• Skip recording date changes when new value is invalid/empty (NaN case)
• Skip recording non-date changes when new value is empty but old value exists (fetch failure scenario)

Problem

When SSL certificate fetching fails (timeout, network error, etc.), the updateSSL function was recording "changes" with empty or invalid values. This resulted in confusing entries in the Change History page showing entries like:

SSL Valid From changed
25 févr. 2026 -

With no meaningful old/new values displayed.

Root Cause

The date comparison logic at line 86:

if (isNaN(diffInDays) || diffInDays > 1) {

When SSL fetch fails, fresh.valid_from and fresh.valid_to are empty strings. new Date("") creates an invalid date, making diffInDays become NaN. The condition isNaN(diffInDays) evaluates to true, causing a "change" to be recorded even though there's no actual new data.

Evidence from database

SELECT * FROM domain_updates WHERE change_type LIKE 'ssl_%';

Shows entries with old_value = '', new_value = '' or new_value = '0'.

Test plan

• Verify that legitimate SSL certificate changes are still recorded correctly
• Verify that SSL fetch failures no longer create ghost entries in domain_updates
• Check Change History page shows only meaningful changes

🤖 Generated with Claude Code

[vercel]

@manganate006 is attempting to deploy a commit to the AS93 Team on Vercel.

A member of the Team first needs to authorize it.