benchmark: harden discover-to-call v2 and publish corrected baseline#264
Merged
Conversation
4 tasks
linfangw
marked this pull request as ready for review
July 23, 2026 11:54
Collaborator
|
@codex review |
Collaborator
|
@codex review |
Collaborator
|
@codex review |
Collaborator
|
@codex review |
Collaborator
|
@codex review |
Collaborator
|
@codex review |
Collaborator
|
@codex review |
Collaborator
|
@codex review |
Collaborator
|
@codex review |
Collaborator
|
@codex review |
Collaborator
|
@codex review |
ax2
approved these changes
Jul 24, 2026
This was referenced Jul 24, 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
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.
What changed
tasks/v4.jsonlone_of_requiredvalues before billed executionQVERIS_*environment variables at adapter process boundariesresult.dataand explicitly requestsrespond_with: "full"discover-call-v2; summaries cannot mix historical v1 and corrected v2 recordsCorrected v2 baseline
The 2026-07-24 run is the first official configured-model baseline collected with corrected
discover-call-v2, immutabletasks/v4.jsonl, 18 tasks, three trials per task, Top-10 discovery, real calls, and complete failed-trial retention.gpt-5.6-solconfigured modelThe strict benchmark gap is 3/54 = 5.56 percentage points. It is not presented as a pure routing effect: both lanes observed API revision
2026-07-23.2, but the API reported no catalog revision and the sequential lanes have different catalog-observation digests. The intervals overlap, so this 18-task result is not a statistical-significance claim.Reference failures are three
timezone-tokyocatalog-coverage misses. The configured lane has three Tokyo constraint mismatches, twodomain-inteltool_use_rejectedadapter failures, and onedomain-intelconstraint mismatch. Every attempted call in both lanes succeeded and returned a non-empty result.The configured lane used
gpt-5.6-sol, medium reasoning, CLI 0.144.1, and toolkit revisiona7f2aa60ef143dbbb35eaf9006ed8123d778fb13. Its provider model revision isunreported, so this is an official configured-model baseline, not a pinned-model snapshot.Validation
git diff --checkpassAdvances #163. The remaining benchmark work is per-release repetition and a future pinned provider snapshot when one is available.