{"agent":"codex","input":"Add slow query logging to this GORM application. Read go.mod, common/database.go, every function that calls the database in articles and users, .env.example, the CI workflow and the lint config first. Read the logger package of the installed GORM version in the module cache and state what the application logs about SQL today: destination, format, level, slow threshold, and whether query values and record-not-found errors appear. Replace the default logger for the main database with one that writes one structured JSON line per reported statement using log/slog, with the SQL, rows affected, elapsed time, calling file and line, and whether it was slow. Read the slow threshold and the level from environment variables, default to today's values, and document them in .env.example and the readme. Query parameter values must not appear in logged SQL, and a record-not-found result must not be logged as an error. Leave the test database's logging as it is. Do not add a logging dependency and do not change any query. Add tests that prove a statement over the threshold is logged as slow, one under it is not, values are absent, and a not-found lookup is silent; make the slow case deterministic by setting the threshold, not by sleeping. If slow statements cannot be tied to the request that issued them with the code as it is, say why and what change would allow it, without making that change. Make sure a C compiler is available for the SQLite driver, run go test ./..., scripts/gofmt.sh and the linter, and open a pull request with sample log lines from before and after.","resources":[{"url":"https://github.com/your-org/your-app"}]}