{"agent":"claude","input":"Python 3.12 prints \"DeprecationWarning: datetime.datetime.utcnow() is deprecated\" for this project. Do not do a blind search and replace. Find every call to datetime.utcnow() and datetime.utcfromtimestamp(), and for each one trace what happens to the value: is it compared with or subtracted from another datetime, converted with .timestamp(), formatted into a string, stored in a file, database or cache, sent over the network, or returned to callers of a public function. Flag every place where a naive UTC datetime meets .timestamp() or datetime.fromtimestamp(), because those assume local time. Before changing anything, write a short script that exercises each such path with the TZ environment variable set to UTC, to a zone east of UTC and to a zone west of UTC, and record what is stored and what age or difference the code computes. Then replace the calls with timezone-aware equivalents (datetime.now(timezone.utc), datetime.fromtimestamp(x, timezone.utc)), changing both sides of every comparison and every write and read pair together so that no naive and aware values meet. If stored data written by the old code would be read differently by the new code, say exactly how, by how many seconds and in which direction, and propose a migration or a version bump of the stored format. List every public return value whose type changes from naive to aware. Add tests that run under at least two time zones. Run the test suite with warnings turned into errors for this deprecation. Open a pull request with the measurements, the tests and what you left alone.","resources":[{"url":"https://github.com/your-org/your-app"}]}