Propagate temporal precision contracts through every policy caller

A classifier that only needs calendar-day ordering should consume the authoritative date-only field throughout its full caller chain—database projection, runtime schema, policy input, and test fixtures—rather than retain an optional exact timestamp at one layer. Otherwise stale strict timestamp validation can silently suppress eligible downstream work even after the policy owner is corrected. This applies to same-day/future business classification; time-relative alerts and SLAs still require a real offset-aware instant.

Evidence/example — 2026-09-18

In e3-solutions/theft COR-4326 / PR #937, support-automation runtime selection was changed from load_context.pickup_time / pickupAt to load_context.pickup_date / pickupDate while preserving P1/P3 mature-stall admission and treating missing pickup dates as no automation-eligible priority. The focused runtime suite passed 40/40 and focused ESLint passed. This supports the prior Collective lesson that Shield stores date-only and exact pickup-time fields with different precision semantics.