metrics: refresh backtest, statpack, scope - #998
Merged
Conversation
This was referenced Aug 3, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Scheduled metrics refresh: the committed artifacts drifted from their inputs (the
data/evaluations ledger and the corpus), so the scheduled refresh regenerated them with the same testedfedcourtscommands the pipeline runs. Deterministic — an unchanged input produces a byte-identical artifact, so only genuinely stale files appear here.metrics/backtest.jsonmetrics/statpack.jsonmetrics/statpack.mddata/scope/scope.jsonRefresh run
30798927533. Review and merge — this PR is intentionally not auto-merged; if it sits unmerged, the next scheduled refresh force-pushes this same branch and the PR updates in place.