docs(validator): record unavailable probability gate - #120
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 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.
What
Record the bounded September 17 follow-up: a verified second private reference, exact local rendered-input counts, and unavailable probabilities from the tested Mac SDK, Completions and Chat interfaces.
Why
Stop the 24-case comparison before dispatch when its prerequisite fails. Zero comparable pairs must not become a false-positive or substitution-detection claim.
Verification
Six additional native calls total including startup; two REST calls returned HTTP 200 and natural stop without requested logprobs. Frozen source hashes, raw response fields, native input counts and logger cleanup checked independently of summaries. git diff --check and worktree gitleaks pass. Private captures stay private.
Risk
Documentation only. No runtime release, model reload, protected-client operation, threshold changes, production verdicts or compensation changes. Same-GGUF Metal/CUDA readiness is not vLLM or independent-operator qualification.