fix(api): /api/stat returns insufficient status to match /api/citable (cherry-pick to main) - #627
Merged
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 freeto 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.
Cherry-pick of #626 to main.
/api/stat was claiming live data with a value and a leader for
benchmarks where the underlying harness has no usable sample
(network-fees, token-deployment-cost, oracle-deviation 3 samples).
/api/citable for the same bench correctly returned status draft.
LLMs and agents that fetch /api/stat directly were seeing the
misleading assertion. This change adds an isInsufficient predicate
that both endpoints now share, and propagates the same status
through headlineSentence so the /answers page and /api/llm-context
also degrade to "insufficient data" instead of asserting a winner.
No code in the harness changed.