{"agent":"claude","input":"A Linear issue labelled agent says: \"Switch the API to structured JSON logs so the log collector can index them. Every request should produce one line with method, path, status, latency and the user id when known, and startup and database errors should be logged the same way.\" Do the work in this repository. Read go.mod, hello.go, common/database.go, common/utils.go, users/middlewares.go, users/unit_test.go, scripts/coverage.sh, scripts/run-api-tests.sh and .github/workflows/ci.yml first. Use log/slog from the standard library; add no logging dependency. Add common/logger.go with a NewLogger that writes JSON to stdout at a level read from LOG_LEVEL (default info) and a RequestLogger gin middleware that logs method, path, status, latency, client IP, the my_user_id context value when set, and any c.Errors. In hello.go use gin.New with gin.Recovery and that middleware instead of gin.Default, and replace log.Println and log.Fatal with the logger. Replace the fmt.Println and fmt.Printf error output in common/database.go and common/utils.go with slog calls carrying the error as an attribute. Leave GORM's logger alone. Add common/logger_test.go that captures a request's log line in a buffer, decodes it and asserts the keys, and tests the LOG_LEVEL parsing. Run scripts/gofmt.sh, scripts/coverage.sh, golangci-lint, gosec and scripts/run-api-tests.sh, paste the results and a few JSON log lines in the pull request description, and document LOG_LEVEL in readme.md. Do not change any route, model or serializer.","resources":[{"url":"https://github.com/your-org/your-app"}]}