The same 30-day jump, two different destinations
Adding 30 days to January 15, 2026 lands on February 14, 2026 — a Saturday — in a month that, checked against the real days-in-month calculation, has only 28 days that year. Adding that identical 30-day span to September 12, 2026 instead lands on October 12, 2026 — a Monday — in a month with 31 days. The same day count, two genuinely different landing months.
Why this isn't just a coincidence of the calendar
A date calculator's day-by-day arithmetic doesn't know or care what month it's rolling through — it just counts. Which month a result lands in, and how long that month happens to be, is a separate fact about the calendar that only the days-in-month calculation actually checks.
Why this matters for anything measured "one month out"
Something scheduled as "30 days from now" doesn't reliably mean "one calendar month away" — the actual gap to the same day-of-month next month varies from 28 to 31 days depending on which months are crossed. A billing cycle or deadline defined in days, rather than in calendar months, can drift against monthly expectations purely because of which months it happens to cross.
The practical takeaway
When a date calculation's result needs to be checked against "how long is this month," the days-in-month calculator answers that for whichever month the date landed in — a separate, real lookup, not something the date arithmetic itself already knows.