Repository navigation
fix: place functional lanes before vendor models - #1009
Merged
Merged
Conversation
Keep economy, balanced, premium first, then functional lanes, then vendor/model lanes. Preserve within-group order and routing behavior. Co-Authored-By: Codex <noreply@openai.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
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.
Display lane groups in this order: quality tiers (
economy,balanced,premium), functional lanes (coding, JSON, tool use, vision and transcription), then vendor/model lanes. Preserve the relative order within the functional and vendor groups.Update the existing config assertion and documentation. All 19 focused config tests pass. Both live configurations use the corrected grouping on the existing v0.30.58 image, with no routing changes or restart.