chore: regenerate coverage metrics - #877
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
chore/metrics-regen
branch
18 times, most recently
from
August 20, 2026 21:05
55bdbc4 to
9d0139f
Compare
github-actions
Bot
force-pushed
the
chore/metrics-regen
branch
from
August 20, 2026 23:56
9d0139f to
4aee707
Compare
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.
Auto-regenerated after a release. Coverage only.
Note
Published without a benchmark snapshot: **1.0.5 **
History points are measured on the reference workstation, not here.
Run
pnpm metricsandpnpm metrics:historythere, then open achore(bench): regenerate metricsPR.Benchmark numbers in this diff are the committed reference-host
measurements, re-emitted unchanged — a shared GitHub runner does not
pin the CPU, and measuring benches here would replace them with
whichever host this job drew.
To refresh benchmarks or the per-version history, run them on the
reference workstation: see "Regenerating metrics" in
.claude/rules/benchmarks.md.