Calendar date or elapsed-time midpoint?
The exact midpoint is always an elapsed-time calculation. The ambiguity appears only when you insist on displaying that instant as one whole calendar date. Date-only mode makes that distinction visible instead of silently rounding it away.
Worked check
January 1 at 00:00 UTC to January 4 at 00:00 UTC spans exactly 3 days. The exact midpoint is January 2 at 12:00 UTC. If your workflow requires one whole-date label, January 2 and January 3 are the adjacent midnight candidates and the selected rounding policy decides which label to display.
Verification: subtract the earlier instant from the midpoint and the midpoint from the later instant. Those elapsed durations must be identical even when the displayed whole-date labels are not.
Why UTC serials are used for date-only mode
A pure calendar date has no time zone. Mapping each date to midnight UTC creates a stable integer-day axis, so daylight-saving transitions cannot turn a nominal one-day step into 23 or 25 hours. Date-time mode remains separate because clock-time inputs really do have zone semantics.
Planning beyond 50%
Equal-part boundaries and custom percentage checkpoints let the same span produce quarter reviews, thirds, payment stages or other elapsed-time milestones. These are not holiday-aware business-day calculations.