Pin generation identities and preserve portable model limits - #179
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.
Release evidence now binds each logical review alias to one canonical provider generation, preventing calibration or release artifacts from being accepted after an alias silently changes models. The verifier rejects self-maps, duplicate canonical identities, incomplete chains, and evidence produced under another screening profile.
Unpinned OpenRouter routes retain portable
max_tokens; only explicitly pinned Azure routes receivemax_completion_tokens. This keeps strict parameter routing compatible with non-Azure endpoints while preserving the qualified Azure request contract.