Uh oh!
There was an error while loading. Please reload this page.
feat(providers): add models.dev registry tracer - #863
Merged
Conversation
Astro-Hanforce-pushed
the
feat/860-provider-registry-tracer
branch
from
July 13, 2026 09:56
01d1115 to
52feda4CompareAstro-Han
marked this pull request as ready for review
July 13, 2026 11:02
Uh oh!
There was an error while loading. Please reload this page.
This was referenced Jul 13, 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 freeto 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
Why
Maka currently hand-maintains provider facts across parallel product layers. This implements the tracer bullet from Refs #860 so later provider slices can extend one proven registry and UI seam instead of adding another routing dependency or duplicated tables.
Scope
This PR is Phase 1 only. It does not migrate every existing provider to the registry, add the remaining target matrix, or redesign the existing provider-grouped connection list.
Verification
Impact
Adds first-class SiliconFlow support and a reusable provider-registry tracer without changing persisted provider IDs or adding a runtime dependency. The checked-in generated snapshot increases repository size and is updated only by the deterministic release command.
Reviewer notes
Review the generated snapshot as data; focus code review on registry ownership, exact model-ID preservation, provider override boundaries, and the Settings child-page navigation.
Ready for review