lukaszraczylo d421f49ff1 test(yaegi-check): verify the metrics endpoint under the interpreter ...

Compiled tests have repeatedly passed on this codebase while the
interpreted shape failed, so the metrics feature needs its own probe
in this harness, not just go test coverage.

Enable metrics in the harness config, with modelLabel on so the
opt-in provider-model breakdown runs interpreted too. Add
exerciseMetricsRoute, driving four real requests: unauthenticated
from outside the allowed CIDR block returns 401, a non-admin key
returns 403, the admin key returns 200 with the expected TYPE lines
and live provider and model data in the body, and a keyless request
from inside the allowed CIDR block returns 200.

Run the new probe last, after the breaker probe settles, since GET
/metrics triggers the same maybeRefresh call every route does and
the breaker probe's own hit counting is timing-sensitive.

2026-08-23 00:19:09 +01:00

..

pricing-sync

fix(pricing): content-digest snapshot instead of a wall-clock date

2026-08-22 02:12:29 +01:00

yaegi-check

test(yaegi-check): verify the metrics endpoint under the interpreter

2026-08-23 00:19:09 +01:00