{"agent":"claude","input":"Add OpenTelemetry tracing to GORM in this Go service. Read go.mod, app.go, database/database.go, every file in database/, api/ and router/, runner/runner.go, config/config.go, config/keys.go, config/parse.go, gotify-server.env.example, Makefile and .github/workflows/build.yml first. Register gorm.io/plugin/opentelemetry/tracing in database.New with WithoutQueryVariables and WithoutMetrics. The GormDatabase methods take no context, so change each one to take a ctx first argument and start from d.DB.WithContext(ctx); update the database interfaces in api/ and auth/authentication.go, pass ctx.Request.Context() from the gin handlers, pass context.Background() from the router ticker, the plugin manager and startup, and update every test call site. Add otelgin.Middleware before accessLogger in router.Create, skipping /health and /stream, and add the trace id to the accessLogger line as trace_id. Add a tracing package that builds a TracerProvider with an OTLP HTTP exporter reading the standard OTEL_EXPORTER_OTLP_* variables, a stdouttrace exporter for local use, a resource with service.name gotify, a batch processor and the TraceContext and Baggage propagators; add GOTIFY_TRACING_ENABLED and GOTIFY_TRACING_EXPORTER to config following the existing parse pattern, default off, documented in gotify-server.env.example; build the provider in serve and defer its shutdown. Start the server on SQLite with tracing on and the stdout exporter, create an application, post a message with its token, and paste the spans into the pull request with the output of go test --race ./... and golangci-lint run. Change no route, response body or swagger annotation.","resources":[{"url":"https://github.com/your-org/your-app"}]}