Wrong next run date when using .at() with a timezone

Wrong next run date when using .at() with a timezone: a task in repo2rlenv-swe-next (Harbor dataset). When scheduling a daily job with a specific time and timezone using .at(time, timezone) , the computed next run date can be off by one day in certain situations.