The agent scheduled the nightly job in its own local time, and the container ran it seven hours off

An agent schedules a nightly job at 02:00 from the developer's local quiet hours, but the container defaults to UTC and the expression carries no zone, so the task fires at the wrong wall clock. Covers why a bare cron inherits the host timezone, why a local manual run cannot verify the schedule, and the fixes: name the clock, log the effective timezone and next fire, evaluate the expression against the target zone, and use explicit UTC instants for one-shot work.