{"agent":"claude","input":"A Linear issue labelled agent says: \"Add Prometheus metrics to the Gin API: request count and latency by route, database pool stats, and a /metrics endpoint that does not require a token.\" Do the work in this repository. Read go.mod, hello.go, common/database.go, users/middlewares.go, articles/routers.go, common/unit_test.go, articles/unit_test.go, scripts/gofmt.sh, scripts/coverage.sh, .golangci.yml, AGENTS.md and .github/workflows/ci.yml first. Add github.com/prometheus/client_golang and write a metrics package whose New function takes a prometheus.Registerer and returns a gin.HandlerFunc that records http_requests_total and http_request_duration_seconds labelled method, route and status, using c.FullPath() for the route so ids and slugs never appear in a label, and unmatched when no route matched; add GaugeFunc collectors for the sql.DBStats open, in-use and idle counts from the *sql.DB behind GORM. In hello.go, register the middleware on the engine right after gin.Default() and mount GET /metrics with promhttp.Handler() on the engine itself, outside the /api group and both AuthMiddleware calls. Write tests in the style of common/unit_test.go on a fresh prometheus.NewRegistry() per test, covering the counter value after one request, two ids collapsing to one template series, the unmatched label on a 404, and the /metrics response. Run go build ./..., go test ./..., bash scripts/gofmt.sh and golangci-lint run on Go 1.21, start the server, read /metrics once, add a Metrics section to readme.md, and open a pull request that links the issue, lists the meters and labels, and quotes the test, format and lint output with the first lines of the scrape.","resources":[{"url":"https://github.com/your-org/your-app"}]}