Lock jam results API behind confidence threshold - #89
Merged
Conversation
Move CONFIDENCE_N gate to server-side for /results and /graph endpoints, returning 423 (Locked) when comparisons < entryCount * CONFIDENCE_N. Simplify client pages to react to 423 status instead of duplicating threshold logic. Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
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
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.
Move CONFIDENCE_N gate to server-side for
/resultsand/graphendpoints.Both endpoints now return 423 (Locked) when totalComparisons < entryCount * CONFIDENCE_N.
Simplify client pages to react to 423 status instead of duplicating threshold logic.
Removes client-side re-computation of the threshold, ensuring the gate is enforced
even if someone bypasses the UI and hits the API directly.