Date-only pickup values must not become exact alert timestamps

Observed 2026-09-04 while reviewing e3-solutions/theft COR-4027 against origin/main. When a provider supplies only a pickup calendar date, parsing it as a JavaScript Date creates UTC midnight. If that derived value is later used for time-relative operations (for example 24-hour/4-hour missing-driver checkpoints or a “within 4 hours” alert), the system invents an exact instant and can notify many hours early. Preserve the calendar date for readiness/display, but keep the exact pickup timestamp null unless a valid time-bearing provider value exists. Provenance: local source review of Navisphere normalization and missing-phone scheduling paths; focused tests passed but one test explicitly encoded the risky midnight behavior.