fix(routing): preserve configured provider namespace ownership

[lidge-jun]

Summary

A configured provider named agy or AgY must own its namespace. Prevent the built-in Google Antigravity alias from being advertised or selected over that configured name, while retaining existing exact canonical, explicit-alias and unknown-prefix precedence.

Carry #3935 from 7ad74746ed260b441ddbceb7a46204085945aa3e onto current dev without modifying the contributor fork. The original two source changes, regression and five-locale documentation are preserved; intervening routed-agent documentation remains intact. This is one bug and one PR.

Verification

• Local product tests, typecheck, builds and dependency installs: NOT RUN, explicitly prohibited by the owner.
• Independent intake and fresh C source/security audit PASS across all eight files. Stable patch-id matches original fix(routing): reserve configured provider names before registry aliases #3935, and all three source/test blobs are identical.
• Exact head 796f7fe34a3d503bc48b2588413ba2ef73ac8499 built 425 documentation pages on remote macmini-cf using Bun 1.4.0 and frozen dependencies; tracked files remained unchanged. No deployment ran.
• Hosted CI 34169304167 completed successfully with 19 successful jobs and 2 skips, including the successful aggregate ci check. Linux logs explicitly passed agy/AgY namespace regressions and warm-cache re-hinting. Windows runtime shards and macOS control are skipped, not passes.
• Current dev 9c8f66b9d adds only independent release-note renderer/scripts and tests after this candidate base. Alias/router source, affected tests and documentation build inputs are unchanged. Candidate CI is not claimed to have executed that later combined release-note tree; final merge-tree equality is checked separately.
• Owner-authorized maintainer integration into dev with exact-head CI, independent audit, live review gate and original luvs01 credit in the squash commit.
• Git diff/source/attribution checks only performed locally. No release, new provider or configuration migration.

Checklist

• Scope stays focused and avoids unrelated cleanup.
• Docs or release notes were updated when needed; five provider configuration locales retained.
• Security-sensitive changes were reviewed for secrets, auth, and unsafe defaults; configured namespace precedence remains authoritative.

Co-authored-by: luvs01 luvs01@hanmail.net

Summary by CodeRabbit

• New Features

  • Provider namespace alias handling now prevents built-in aliases from conflicting with configured provider names or explicit aliases.
  • Canonical provider names continue to require exact case matching, while unrecognized prefixes retain existing fallback routing.

• Documentation

  • Added provider namespace alias guidance in English, Japanese, Korean, Russian, and Simplified Chinese documentation.

[coderabbitai]

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Team

Run ID: a6f63d0c-b89d-48a5-bcbc-74a0cecf8b56

📥 Commits

Reviewing files that changed from the base of the PR and between 60bcb90 and 796f7fe.

📒 Files selected for processing (8)

• docs-site/src/content/docs/ja/reference/configuration/providers.md
• docs-site/src/content/docs/ko/reference/configuration/providers.md
• docs-site/src/content/docs/reference/configuration/providers.md
• docs-site/src/content/docs/ru/reference/configuration/providers.md
• docs-site/src/content/docs/zh-cn/reference/configuration/providers.md
• src/providers/default-aliases.ts
• src/router.ts
• tests/providers/provider-model-aliases.test.ts

---

📝 Walkthrough

Walkthrough

Configured provider names now suppress conflicting built-in aliases case-insensitively in catalog generation and routing. Tests cover canonical names, custom namespaces, case variants, and fallback behavior. Reference documentation describes the updated rules in five languages.

Changes

Provider namespace alias collision handling

Layer / File(s)	Summary
Alias claim detection src/providers/default-aliases.ts	At lines 18–21, effectiveProviderAlias also checks configured provider names when determining whether another provider claims a registry alias.
Routing, tests, and documentation src/router.ts, tests/providers/provider-model-aliases.test.ts, docs-site/src/content/docs/reference/configuration/providers.md, docs-site/src/content/docs/ja/reference/configuration/providers.md, docs-site/src/content/docs/ko/reference/configuration/providers.md, docs-site/src/content/docs/ru/reference/configuration/providers.md, docs-site/src/content/docs/zh-cn/reference/configuration/providers.md	At lines 706–715, registry-alias fallback routing applies the configured-name collision rule. Tests at lines 220–263 verify catalog output, canonical routing, custom namespaces, case variants, and fallback routing. The reference documentation describes the same behavior in five languages.

Estimated code review effort: 2 (Simple) | ~10 minutes

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/248-a-alias-8c62

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

✅ Deterministic PR hygiene checks passed.

[lidge-jun]

리뷰 · 우선순위 71 / 80

이 PR은 사용자가 설정한 공급자 이름이 agy처럼 레지스트리 기본 축약명과 겹칠 때, Google Antigravity 같은 다른 공급자의 내장 별칭이 카탈로그·라우팅을 가로채지 못하게 합니다. 예: 설정에 agy라는 공급자를 두면 Google 모델은 google-antigravity/<model>로 남고, agy/<model>은 설정 공급자를 고릅니다. 기여 원본은 #3935이고, 이 PR은 그 소스 두 곳 + 회귀 + 5개 로케일 문서를 현재 dev에 올린 maintainer carry 입니다.

지금 dev HEAD 60bcb9050의 src/providers/default-aliases.ts effectiveProviderAlias와 src/router.ts Pass 2 registry alias 매칭을 보면, claimedByOther가 다른 공급자의 명시적 alias 필드만 봅니다. 공급자 이름 자체가 agy/AgY인 경우는 “이미 점유됨”으로 안 칩니다. 그래서 설정 이름 agy가 있어도 google-antigravity의 레지스트리 별칭 agy가 카탈로그 display와 alias 라우팅에 남을 수 있습니다. #3531 리뷰 이후 “명시 alias가 점유하면 내장 별칭 억제”는 들어갔지만, canonical 이름이 점유하는 경우는 빠져 있었습니다.

변경은 같은 판정을 두 곳에 대칭으로 넣습니다. name.toLowerCase() === lower(또는 requestedLower)이거나 명시 alias가 같으면 claimed로 보고, 내장 별칭을 끕니다. 정규(canonical) 공급자 이름은 계속 대소문자 완전 일치이고, 인식 못 하는 접두사는 기존 default-provider 폴백을 탑니다. 테스트는 agy/AgY 설정 이름이 Google의 providerAlias를 null로 만들고, agy/<model>은 설정 공급자, AGY/<model>(다른 대소문자)은 기본 공급자 폴백인 것을 확인합니다. en/ko/ja/ru/zh-cn providers 문서에 네임스페이스 별칭 절을 같은 내용으로 넣었습니다. types/config 분할과 안 겹칩니다.

라인 src/providers/default-aliases.ts · claimedByOther - 카탈로그 표시용 별칭 억제입니다. 이름 점유를 alias 점유와 같이 보지 않으면 GUI/카탈로그에 agy/...가 Google로 다시 뜹니다.

라인 src/router.ts · Pass 2 registryMatches - 라우팅 쪽 같은 판정입니다. 한쪽만 고치면 “목록과 실제 라우트가 다른” 상태가 됩니다. 두 파일 대칭을 유지하세요.

경로 #3935 - 같은 수정의 contributor 원본(open)입니다. 이 carry가 먼저 들어가면 #3935는 landed-via-maintainer로 닫으면 됩니다. 새 공급자나 마이그레이션은 없습니다.

메인테이너의 판단이 필요한 지점

• 지금 draft이고 hosted CI가 아직 pending입니다. 그린 확인 후 ready/머지할지
• 머지 직후 fix(routing): reserve configured provider names before registry aliases #3935 leftover 정리 여부
• 대소문자 폴백(AGY/... → default-provider) 동작이 문서/기대와 맞는지(테스트는 의도적으로 그 폴백을 고정)

너의 추천
CI 그린이면 draft 해제 후 머지하세요. 설정 네임스페이스 소유권을 이름·별칭 양쪽에서 맞추는 작은 패치이고, #3935는 머지 후 닫으면 됩니다.

이 댓글은 grok-bot이 작성했습니다

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-09-07T23:35:16.602172Z	796f7fe	Draft marked ready

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.