docs(code-review): add experiment leaderboard table#705
Open
gggdttt wants to merge 2 commits into
Open
Conversation
added 2 commits
June 26, 2026 23:36
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
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.
Adds the Experiment Leaderboard section to the code-review docs page, decoupled from #696.
Why
#696 (live BCQuality consumption) is paused pending a review of how BCApps consumes BCQuality, but we still run the experiment data. The site page should reflect those runs independently of merging #696.
Changes
docs/code-review.md: rename baseline headerF1->Micro F1for consistency; add an Experiment Leaderboard table that renders rows whereagg.experimentis set (BCQuality live skills vs inline pre-#8700 knowledge).src/bcbench/types.py: addbcquality: bool = FalsetoExperimentConfiguration(and include it inis_empty()). Required so the leaderboard aggregation preserves the live-arm marker; otherwise pydantic drops the unknown key and live-arm rows mislabel as Other. Default-off and backward compatible — existing results are unaffected.Safety
Generated with the help of GitHub Copilot.