feat(benchmarks): add deterministic Sentry evaluation - #26
Merged
Conversation
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.
Summary
decidedCLI as an external process, with no Core imports or model judgeResults
All committed correctness floors are
1.0:sentry/gate --codeparityPublished macOS v0.26.0 binary, 30 iterations:
Timing remains diagnostic and outside the scored metrics.
The 5,000-decision profile separately passes clean/full, violating/full, violating/diff, composed-gate parity, attribution, coverage-accounting, and byte-determinism checks. A representative local run completed the dedicated Sentry profiles in 0.61–0.67 seconds and the composed gate in 1.74 seconds; these timings are reported, not gated.
Contract boundary
decided gate --codedoes not yet expose Sentry's decision and rule provenance. Parity therefore compares the public outcome, coverage, code, path, and line fields shared by both surfaces. Dedicated Sentry JSON remains authoritative for decision/rule attribution, and the missing composed-gate provenance is recorded as follow-up rather than inferred.Validation
RAC_BIN=/private/tmp/asd-v026-published/decided python3 sentry/run.py --checkRAC_BIN=/private/tmp/asd-v026-published/decided python3 sentry/run.py --scale --corpus-size 5000RAC_BIN=/private/tmp/asd-v026-published/decided uv run --extra dev pytest -q— 63 passed