The time synchronization drift occurred because the REST API dictionary hash processed time and timezone payload keys unordered, resulting in the time incorrectly being set before the timezone was applied. Furthermore, the web server's daemon process inherited a TZ=UTC environment variable, causing underlying Linux date subprocess commands to skew all time reads and writes toward UTC instead of /etc/localtime.

The changes has been tested locally.