fix(catalog): retain default-only static provider models - #3717
fix(catalog): retain default-only static provider models#3717lidge-jun wants to merge 5 commits into
Conversation
Add real gather controls for omitted/empty models, retained-id deduplication, explicit-list precedence, OAuth/forward no-request paths, and authoritative empty live discovery. Align eight-language static documentation and the source of truth. Co-authored-by: gqchen <276851182@qq.com>
|
Important Draft PR not reviewedDraft PRs are not automatically reviewed by default.
To automatically review draft PRs, update your CodeRabbit configuration: reviews:
auto_review:
drafts: trueThanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
✅ Deterministic PR hygiene checks passed. |
The legacy Go fixture already receives a registry default under existing ownership rules. Require exactly that singleton under static seeding, with no metadata roster or network calls. Keep genuine no-default emptiness and add strict custom MiMo transport negatives. Production seeding and ownership rules remain unchanged. Co-authored-by: gqchen <276851182@qq.com>
리뷰 · 우선순위 61 / 80이 PR은 코드 변경은 작습니다. 우선순위 61인 이유다. 카탈로그가 비는 실제 버그이고 B-lane 경로/심볼 - 메인테이너의 판단이 필요한 지점
너의 추천 이 댓글은 grok-bot이 작성했습니다 |
Summary
A provider configured with
liveModels: falseand onlydefaultModelpreviously produced an empty static catalog. Seed that default when the effective explicit models list is absent or empty, including defaults supplied by the existing preset-enrichment policy, then retain the ordered union withretainModels.Nonempty explicit lists keep precedence. Forward-auth providers keep their native path, and static gathering still avoids OAuth refresh and upstream model requests. Selection and visibility filters continue to apply.
This is the static-catalog portion of #3659 at ff4e5cd, preserving gqchen's source authorship. The provider-workspace Delete/Hide controls follow in a dependent PR. Original #3659 remains open until both capabilities are verified on dev.
Stack: this parent targets dev; the upcoming model-controls child targets this branch. Review and verify both heads, then land bottom-up and retarget the child before parent cleanup.
Verification
Checklist
Co-authored-by: gqchen 276851182@qq.com