Resync model metadata with current provider lineups - #44
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
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.
Summary
Catalog enrichment resync against today's live
/modelslists and models.dev:deepseek-flashappears in authenticated Go discovery but has no models.devopencode-goentry; it is fully cataloged upstream under DeepSeek (V4.1 Flash, 1M context, 393K output, image input, low/high/max reasoning efforts, real costs $0.15/$0.60/$0.003). Mirrored intoSUPPLEMENTAL_MODELSso authenticated users get full metadata. Routes chat-completions (npm@ai-sdk/openai-compatible).minimax-m2.5,kimi-k2.5,glm-5.1,glm-5, andqwen3.5-plus(keeps its@ai-sdk/anthropicnpm → Messages endpoint). Mirrors only carry data a canonical upstream entry already publishes for the same model; nothing guessed.test,test-novita-dsf4.1, …) that leak into authenticated Zen discovery instead of listing them as unenriched picker entries.resolveEndpointKindalready resolves every new id correctly.jev-1.13/jev-1.13-free(Zen) andomen-alpha,mimo-v2-pro/mimo-v2-omni(Go anonymous) remain unenriched — no upstream signal anywhere; they will be enriched once models.dev catalogs them (supplemental entries are superseded by canonical ones automatically).Verification
npm testpasses (new supplemental-mirror and test-id filter tests).opencode-bridge-copilot-chat).