{"agent":"claude","input":"Add Prometheus metrics to this Rocket application. Read Cargo.toml, rust-toolchain.toml, src/main.rs, src/util.rs, src/api/mod.rs, src/api/web.rs, src/db/mod.rs, src/config.rs, src/api/admin.rs, .env.template and .github/workflows/build.yml first. Add the prometheus crate and implement a Metrics fairing in a new module, modelled on the BetterLogging fairing: record a request counter and a duration histogram labelled by method, the matched route's URI pattern (never the raw path) and the status class, with a fixed label for requests that matched no route, and gauges for the database pool's open and idle connections and the semaphore's free permits. Attach it in launch_rocket after the existing fairings. Add a GET /metrics route beside alive in src/api/web.rs guarded by a new metrics_token setting declared through make_config! like admin_token, compared in constant time with crate::crypto::ct_eq: 404 when the setting is unset, 401 on a wrong bearer token. Document METRICS_TOKEN in .env.template next to ADMIN_TOKEN. Write unit tests for the fairing with rocket::local::blocking::Client on a minimal rocket instance. Install the system packages build.yml installs, then run cargo test --profile ci --features sqlite,mysql,postgresql,enable_mimalloc,s3, cargo test --profile ci --features sqlite, cargo clippy --profile ci --features sqlite,mysql,postgresql,enable_mimalloc,s3 with RUSTFLAGS=-Dwarnings, and cargo fmt --all -- --check. Start the binary against SQLite with METRICS_TOKEN set, make requests to a few routes, and fetch /metrics with and without the token. Do not change any workflow, Dockerfile or migration. Open a pull request that quotes the commands you ran with their output and pastes a trimmed /metrics response showing the route-pattern labels.","resources":[{"url":"https://github.com/your-org/your-app"}]}