refactor(models): keep one selector field - #82
Merged
Conversation
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Germey
force-pushed
the
fix/model-selector-cleanup
branch
from
August 6, 2026 04:32
0803694 to
1684d09
Compare
Germey
approved these changes
Aug 6, 2026
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
2 participants
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.
Context
Follow-up to the already merged #81. That PR separated selector provenance from the resolved model, but retained both
modelandmodel_selectornames in runtime/session payloads.Cleanup
model_selector.model_selector; resolved identity remainsresolved_model.model_contractand the outbound compatibilitymodelalias are removed.modelis normalized once at the connection boundary for rolling client compatibility and is never persisted or emitted.Verification
🤖 Generated with Claude Code