Repository navigation
docs(benchmarks): "what is blocking this PR?" accuracy study (44 PRs, brick vs native) - #871
Merged
Merged
Conversation
This was referenced Oct 25, 2026
Co-authored-by: icfrelinger <icfrelinger@gmail.com>
…brick vs native) Co-authored-by: icfrelinger <icfrelinger@gmail.com>
…ble score output Co-authored-by: icfrelinger <icfrelinger@gmail.com>
… 109/109, no wrong claims Co-authored-by: icfrelinger <icfrelinger@gmail.com>
cursor
Bot
force-pushed
the
cursor/blockers-accuracy
branch
from
October 26, 2026 04:09
ab2fd91 to
0b8970c
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
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.
Accuracy study of the
github.blockersanswer. It covers 44 real pull requests in 5 public repositories, graded against ground truth computed from GitHub's API at one recorded snapshot. The brick arm and a native raw-REST arm both run onclaude-sonnet-5-5and replay the same fixtures.Rebased onto current master (
01366adc8, after 0.4.0). Head0b8970c01. The only conflict wasCHANGELOG.md: the study stays under[Unreleased], above the token-benchmark follow-up and the dogfood entry;[0.4.0]is unchanged.Headline (first snapshot, brick 1.0.0)
The study found three brick bugs, F1–F3. All have one cause: required checks and approvals came only from admin-only branch protection.
Re-run after the fix (second snapshot, brick 1.0.0 vs 1.1.0 back to back)
The fix is #874 (merged as
043a37a5). On a second snapshot (CI run40218094404, about 18:00 UTC), each PR was asked of both bricks:The doc states the limit on this result. Brick 1.1.0 now reads the GitHub sources the rubric is computed from, so the full agreement shows it applies them without error; it is not independent evidence. The native arm was not re-run.
Spend: $5.10 for the study and $0.33 for the re-run. Each time the key was used only as an env var and unset afterwards.
What changed
docs/benchmarks/blockers-accuracy.md: the written rubric, method, results, findings with their fix status, the re-run, limits and the per-PR table.tools/blockers-accuracy/: the harness (capture, fixtures, truth, run, score), both snapshots (fixtures/,fixtures-rerun/) and the raw runs.capture.py --extraasks a second host build.run.py --armsruns only the arms named.score.py --fixtures/--brick-dirgrades another snapshot or brick build.docs/DocsIndex.md,CHANGELOG.md(Unreleased), and the regenerated knowledge graph.Verification
scripts/ci/run-repo-gates.sh: all 44 gates pass on the rebased tip.verify-doc-anchors.py: passes.python3 tools/blockers-accuracy/score.py …re-grades offline.