docs(validator): diagnose stop matching during reasoning - #118
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
Document six bounded owned-Qwen backend calls across two retained stop assignments and correct the earlier interpretation of empty evidence.
Why
The no-stop controls produced correct normalized final prefixes and contained the marker in reasoning. Original-stop streaming and non-streaming calls ended with reasoning but no visible answer. Deployed Core retains reasoning only for token-limit probes, so null stored reasoning is not proof of zero backend generation.
Verification
Six HTTP 200 backend captures; independently parsed marker placement and both expected-prefix commitments. Original 1024-token budgets preserved. git diff --check and staged plus full reachable-history gitleaks passed. Private prompts, credentials and raw responses remain outside the repository.
Risk
Documentation only. No runtime, score, assignment, historical evidence, payment or service changes. The existing preview.20 delivery fix remains valid. Revised stop-policy qualification and operator compensation activation are separate unfinished work.
Refs #68