`parse_range` sent each end through `chronify` on its own. A clock-only time never resolves into the future, so the two ends could land on different days, the start came out later than the end, and the swap turned a short window into the span between those days. It broke the query exactly when someone would type it: at 2pm, `--from "9am to 5pm"` returned yesterday evening through this morning. A range over midnight failed twice over, reaching back a day it was not asked for and dropping the entries that really did fall inside it. Each one exited zero and printed output that read as if it had worked. Resolve the start as before, then take the end as the first occurrence of its clock time at or after it. Skip the end-of-day extension on that path, since it exists for a date with no time and would stretch `9pm to midnight` by a day. Add `parser::clock_time` to tell a bare clock time from a timestamp that already names a day. Ranges written with dates are untouched. Closes #439