Time error if plan is across time change boundary

🚧 THIS IS A TICKET MIGRATED FROM UPVOTY. The original ticket and comments will be available for a limited time over at:
https://abrp.upvoty.com/b/report-a-bug/time-error-if-plan-is-across-time-change-boundary/
———————————————————————————
When I put in a plan for next April (it is now December), with a starting time of 8 AM, the route shows start at 7 AM, and all the times are an hour early. I predict this is due to using the current DST setting for the entered time and the time-of-trip DST setting for the route times. It should instead interpret the input time using the DST setting of the input date.