the date is in the "system prompt", so the cron job that updates the prompts to the current date may be in a different time zone than you.
7f5dbb71f54322f271c4d3fc3aaa4d3282a1af5541d82b2cbc5aa10c1420b6bc
They're not actually processing the entire system prompt (which is rather long) on every query, but continuing from a model state saved after processing the system prompt once.
That makes it a bit harder, but still, spitting out the wrong date just seems like a plain old time-zone bug.
