@eduwork/dsh-oidc 0.2.4 → 0.3.0-dev.2

package/docs/dsh-integration.en.md

@@ -12,7 +12,7 @@ The plugin uses public package exports rather than copied DSH source:
 | --- | --- |
 | `dsh-typert-protocol` | Host/client RPC descriptors. |
 | `dsh-host-webserver` | Exact `/oauth/callback` route. |
-| `dsh-credentials` | Session and runtime API-key storage. |
+| `dsh-credentials` | Authorization session storage. |
 | `dsh-llm` | Adapter registry, credentials, retry policy, stable errors. |
 | `dsh-llm-pi-ai` | Official `PiAiAdapter`. |
 | `dsh-settings` | Provider directory/readiness facts. |
@@ -23,7 +23,7 @@ The OpenAI-compatible wire implementation comes from `@earendil-works/pi-ai`, wh
 
 ## Why the Provider adapter is inside this package
 
-OIDC authentication alone does not yield a callable enterprise model. A closed-loop integration also needs a stable Provider route whose credential reference matches Key Binding output. Publishing a second organization-specific Provider package would recreate the coupling this repository is meant to remove.
+OIDC authentication alone does not yield a callable enterprise model. A closed-loop integration also needs a stable Provider route whose credential reference matches current token authorization. Publishing a second organization-specific Provider package would recreate the coupling this repository is meant to remove.
 
 The adapter is therefore an internal module of `dsh-oidc`, but its behavior is constrained:
 
@@ -49,12 +49,12 @@ The default export is `OidcAccountService`, a `TypertRemoteService` named `oidcA
 | `loginStatus(loginID)` / `cancelLogin(loginID)` | Poll or cancel the current desktop attempt. |
 | `resources(profileID)` | Model metadata and issues, without quota or secrets. |
 | `selectEnterpriseModel(profileID, options)` | Select a verified connected model through official defaults; no arbitrary Provider destination. |
-| `reconcile(profileID, {allowProvision})` | Bootstrap and resolve/provision/renew. |
+| `reconcile(profileID, {})` | Refresh authorization and model resources. |
 | `logout(profileID)` | Local cleanup and best-effort OIDC revocation. |
 | `management()` | Capability-aware projection consumed by the shared enterprise-model settings UI. |
 | `activate/configure/addCustom/updateCustom/removeProfile/configureModels/restart` | Optional native management operations; Web profiles reject mutation. |
 
-The client descriptor uses strict Zod codecs. Configuration sent to the browser excludes issuer, client ID, Key Binding base, model base URL, tokens, and keys.
+The client descriptor uses strict Zod codecs. Configuration sent to the browser excludes issuer, client ID, , model base URL, tokens, and keys.
 
 ## Web composition
 
@@ -80,7 +80,7 @@ dsh plugin --profile web add .
 
 The local-path install links the checkout into the Profile, so the source directory must remain available. It does not scan the current workspace. Team deployments should pin a reviewed, exact npm version and must not mix another DSH prerelease line into the same Profile.
 
-The shipped patch mounts exactly one `enterprise-oidc` instance using `EDUWORK_OIDC_PROFILE`. The Web backend requires the DSH WebServer to listen exactly on `127.0.0.1` and builds the fixed `/oauth/callback` from its actual port; no public callback-origin setting is accepted. The patch does not hard-code `agent-default-model`; after explicit login/key binding, the Client selects the connected organization model through official APIs. Restart recovery only repairs an unusable default and preserves personal selections. `DSH_OIDC_ENTERPRISE_PROFILE` remains a fallback.
+The shipped patch mounts exactly one `enterprise-oidc` instance using `EDUWORK_OIDC_PROFILE`. The Web backend requires the DSH WebServer to listen exactly on `127.0.0.1` and builds the fixed `/oauth/callback` from its actual port; no public callback-origin setting is accepted. The patch does not hard-code `agent-default-model`; after explicit gateway login, the Client selects the connected organization model through official APIs. Restart recovery only repairs an unusable default and preserves personal selections. `DSH_OIDC_ENTERPRISE_PROFILE` remains a fallback.
 
 ### Product-owned Bundle
 
@@ -101,50 +101,15 @@ The shipped patch mounts exactly one `enterprise-oidc` instance using `EDUWORK_O
 
 The containing DSH profile/bundle must also include the ordinary Web app, credentials, LLM/Pi adapter dependencies, settings, attachment services, and client surfaces. `dsh-oidc` is not a complete DSH distribution.
 
-See the [getting-started guide](getting-started.en.md) for OIDC registration, Key Binding implementation, environment variables, acceptance, and troubleshooting.
+See the [getting-started guide](getting-started.en.md) for OIDC registration, Token gateway implementation, environment variables, acceptance, and troubleshooting.
 
 ## Desktop composition
 
-New Wails/Electron products use `backend: desktop`: the plugin owns a temporary loopback callback and opens the browser through official `nativeCommand`. Both shells share identity, Key Binding and model behavior. The host still provides credential storage; no new `enterpriseAccounts` bridge is required. See [desktop host integration](desktop-host.en.md).
+New Wails/Electron products use `backend: desktop`: the plugin owns a temporary loopback callback and opens the browser through official `nativeCommand`. Both shells share identity, token lifecycle and model behavior. The host still provides credential storage; no new `enterpriseAccounts` bridge is required. See [desktop host integration](desktop-host.en.md).
 
 ## Legacy native bridge
 
-The following adapter interface is only for existing integrations. It is not required for a new desktop:
-
-```yaml
-- insert:
-    - id: enterprise-oidc
-      name: '@eduwork/dsh-oidc'
-      config:
-        backend: native
-        uiMode: models-only
-        profilePathEnv: PRODUCT_ENTERPRISE_PROFILE
-```
-
-The host supplies Cordis service `enterpriseAccounts`. Any product-owned institution catalog MUST first be converted by the host or assembly layer into a standard Enterprise Profile; `dsh-oidc` does not read or interpret product catalogs:
-
-```ts
-interface EnterpriseAccounts {
-  status(institutionID: string): Promise<NativeStatus>
-  login(institutionID: string, options: { allowProvision: false }): Promise<NativeStatus>
-  reconcile(institutionID: string, options: { allowProvision: boolean }): Promise<NativeStatus>
-  logout(institutionID: string): Promise<NativeStatus>
-  configuration(): Promise<NativeManagement>
-  activate(institutionID: string): Promise<NativeManagement>
-  configure(institutionID: string): Promise<NativeManagement>
-  addCustom(baseURL: string): Promise<NativeManagement>
-  updateCustom(institutionID: string, baseURL: string): Promise<NativeManagement>
-  removeInstitution(institutionID: string): Promise<NativeManagement>
-  configureCustomModels(institutionID: string, mode: 'discovery' | 'manual', models: RuntimeModel[]): Promise<NativeManagement>
-  restart(): Promise<{restarting: true}>
-}
-```
-
-`NativeStatus` may include `displayName`, `organization`, `state`, `userName`, `affiliation`, `accessExpiresAt`, `runtimeCredentialRef`, `credentialReady`, `credentialState`, and `capabilities`. `runtimeCredentialRef` is only a host status assertion; when present, it MUST equal the normalized Enterprise Profile `keyBinding.credentialRef`. Credential naming belongs to the Profile, not to Wails, Electron, or any other host implementation.
-
-Only the first four lifecycle operations are required for a native identity backend. Management operations are capability-detected: when absent, the same UI remains a read-only profile/model viewer. This is a host adapter, not part of OIDC or Key Binding wire standards. It can be implemented by Wails, Electron, Tauri, a mobile bridge, or another local host.
-
-The public browser projection is versioned as `dsh-oidc/management/v1alpha1`. It deliberately excludes tokens and credentials. Web Enterprise Profiles set all mutation capabilities to false; a native adapter may set `manageProfiles`, `manageModels`, and `restart` according to the methods it actually provides.
+backend: native has been removed. Use the shared desktop backend and Host credential/browser services.
 
 ## Model capability transforms
 
@@ -174,7 +139,7 @@ For every DSH release candidate or stable upgrade:
 1. update exact peer versions in a branch;
 2. diff the public exports and relevant types used above;
 3. run unit and package tests;
-4. launch a plain Web DSH profile and complete login, provisioning, model call, refresh, logout;
+4. launch a plain Web DSH profile and complete login, model call, refresh, logout;
 5. launch the desktop/native composition and compare user-visible behavior;
 6. verify client loader format and slot names;
 7. review whether official DSH capability supersedes any local adapter code;
@@ -182,6 +147,6 @@ For every DSH release candidate or stable upgrade:
 
 No semver range should silently opt this security-sensitive plugin into an untested DSH release while DSH remains pre-1.0.
 
-## Credential reads for institution adapters
+## Authorized requests for institution adapters
 
-Explicitly installed local adapters may call `ctx.oidcAccounts.resolveBoundCredential(profileID, { credentialRef: "EDUWORK_API_KEY", runtimeBaseURL })`. The runtime URL must exactly match the reviewed Profile model-service URL. The result is a DSH credential record verified against the session, issuer/client ID, complete resource binding and credential fingerprint, or `undefined`. Use this same snapshot rather than checking status and resolving the name separately, which can race with a login change. This is Host-only, with no Typert/RPC registration and no addition to the server protocol. Adapters remain responsible for restricting request destinations. Desktop/Web support the method; the legacy native bridge does not fall back to an unverified key.
+Installed adapters use `ctx.oidcAccounts.modelResourceFetch(profileID, relativePath)` for requests authorized by the current Token. See [account extensions](account-extensions.en.md). The old `resolveBoundCredential` method has been removed. Host-only `modelAuthorization(profileID, expectedBaseURL)` checks readiness and the discovered API URL, returning only a boolean. The shared Host transport checks the active session, refreshes authorization, and restricts requests to the discovered model API.

package/docs/dsh-integration.md

@@ -12,7 +12,7 @@
 | --- | --- |
 | `dsh-typert-protocol` | Host/Client RPC 描述符。 |
 | `dsh-host-webserver` | 精确 `/oauth/callback` 路由。 |
-| `dsh-credentials` | Session 和运行时 API Key 存储。 |
+| `dsh-credentials` | 授权 Session 存储。 |
 | `dsh-llm` | Adapter 注册、凭据、重试策略和稳定错误。 |
 | `dsh-llm-pi-ai` | 官方 `PiAiAdapter`。 |
 | `dsh-settings` | Provider 目录和就绪状态。 |
@@ -23,7 +23,7 @@ OpenAI-compatible 网络实现来自 `@earendil-works/pi-ai`，它也是 DSH 官
 
 ## 为什么 Provider adapter 位于本包内
 
-只有 OIDC 认证还不能获得可调用的企业模型。闭环集成还需要稳定 Provider 路由，并确保其凭据引用与 Key Binding 输出一致。再发布一个机构特有 Provider 包，会重新制造本仓库要消除的耦合。
+只有 OIDC 认证还不能获得可调用的企业模型。闭环集成还需要稳定 Provider 路由，并确保其凭据引用与 当前 Token 授权一致。再发布一个机构特有 Provider 包，会重新制造本仓库要消除的耦合。
 
 因此 adapter 是 `dsh-oidc` 内部模块，但其行为受到严格约束：
 
@@ -49,12 +49,12 @@ OpenAI-compatible 网络实现来自 `@earendil-works/pi-ai`，它也是 DSH 官
 | `loginStatus(loginID)` / `cancelLogin(loginID)` | 查询或取消当前桌面登录。 |
 | `resources(profileID)` | 模型元数据与问题，不含配额或秘密。 |
 | `selectEnterpriseModel(profileID, options)` | 通过官方默认值选择已验证连接的模型，不接受任意 Provider 目的地。 |
-| `reconcile(profileID, {allowProvision})` | 执行 bootstrap 和 resolve/provision/renew。 |
+| `reconcile(profileID, {})` | 刷新授权和模型资源，不申请模型 Key。 |
 | `logout(profileID)` | 本地清理，并尽力执行 OIDC 撤销。 |
 | `management()` | 共用企业模型设置 UI 使用的宿主能力投影。 |
 | `activate/configure/addCustom/updateCustom/removeProfile/configureModels/restart` | 可选 native 管理操作；Web Profile 拒绝修改。 |
 
-Client 描述符使用严格 Zod codec。发送给浏览器的配置不包含 issuer、client ID、Key Binding base、模型 base URL、Token 或 Key。
+Client 描述符使用严格 Zod codec。发送给浏览器的配置不包含 issuer、client ID、、模型 base URL、Token 或 Key。
 
 ## Web 组合
 
@@ -101,50 +101,15 @@ dsh plugin --profile web add .
 
 所属 DSH Profile/Bundle 还必须包含普通 Web 应用、credentials、LLM/Pi adapter 依赖、settings、attachment 服务和 Client 界面。`dsh-oidc` 不是完整 DSH 发行版。
 
-OIDC 注册、Key Binding 实现、环境变量、验收和排障见[接入指南](getting-started.md)。
+OIDC 注册、Token 网关实现、环境变量、验收和排障见[接入指南](getting-started.md)。
 
 ## Desktop 组合
 
-新 Wails/Electron 产品使用 `backend: desktop`：插件管理临时 loopback 回调，通过官方 `nativeCommand` 打开浏览器。两壳共享身份、Key Binding 和模型行为；宿主仍提供凭据存储，无需另写 `enterpriseAccounts`。见[桌面 Host 集成](desktop-host.md)。
+新 Wails/Electron 产品使用 `backend: desktop`：插件管理临时 loopback 回调，通过官方 `nativeCommand` 打开浏览器。两壳共享身份、Token 生命周期和模型行为；宿主仍提供凭据存储，无需另写 `enterpriseAccounts`。见[桌面 Host 集成](desktop-host.md)。
 
-## 旧 native 桥兼容
+## 旧 native 桥
 
-以下 adapter 仅用于已有集成，不是新桌面的必做项：
-
-```yaml
-- insert:
-    - id: enterprise-oidc
-      name: '@eduwork/dsh-oidc'
-      config:
-        backend: native
-        uiMode: models-only
-        profilePathEnv: PRODUCT_ENTERPRISE_PROFILE
-```
-
-宿主提供 Cordis 服务 `enterpriseAccounts`。产品自有机构目录必须由宿主或装配层先转换为标准 Enterprise Profile；`dsh-oidc` 不读取或解释产品目录：
-
-```ts
-interface EnterpriseAccounts {
-  status(institutionID: string): Promise<NativeStatus>
-  login(institutionID: string, options: { allowProvision: false }): Promise<NativeStatus>
-  reconcile(institutionID: string, options: { allowProvision: boolean }): Promise<NativeStatus>
-  logout(institutionID: string): Promise<NativeStatus>
-  configuration(): Promise<NativeManagement>
-  activate(institutionID: string): Promise<NativeManagement>
-  configure(institutionID: string): Promise<NativeManagement>
-  addCustom(baseURL: string): Promise<NativeManagement>
-  updateCustom(institutionID: string, baseURL: string): Promise<NativeManagement>
-  removeInstitution(institutionID: string): Promise<NativeManagement>
-  configureCustomModels(institutionID: string, mode: 'discovery' | 'manual', models: RuntimeModel[]): Promise<NativeManagement>
-  restart(): Promise<{restarting: true}>
-}
-```
-
-`NativeStatus` 可以包含 `displayName`、`organization`、`state`、`userName`、`affiliation`、`accessExpiresAt`、`runtimeCredentialRef`、`credentialReady`、`credentialState` 和 `capabilities`。`runtimeCredentialRef` 只是宿主状态回报；若提供，必须等于 Enterprise Profile 规范化后的 `keyBinding.credentialRef`。凭据命名策略属于 Profile，不属于 Wails、Electron 或其他宿主实现。
-
-Native 身份后端只必须实现前四项生命周期操作。管理操作通过能力探测：缺少这些方法时，同一 UI 会保持为只读 Profile/模型查看器。这是宿主 adapter，不属于 OIDC 或 Key Binding 网络标准；Wails、Electron、Tauri、移动桥接或其他本地宿主均可实现。
-
-浏览器公共投影版本为 `dsh-oidc/management/v1alpha1`，有意排除 Token 和凭据。Web Enterprise Profile 的所有修改能力为 false；native adapter 可以根据实际方法声明 `manageProfiles`、`manageModels` 和 `restart`。
+backend: native 已移除。桌面使用共享 desktop 后端及宿主凭据、浏览器服务。
 
 ## 模型能力转换
 
@@ -167,9 +132,9 @@ const dispose = ctx.enterpriseTransforms.register({
 
 转换是可执行本地插件，必须单独审查，绝不会从 Enterprise Profile 加载。
 
-## 机构适配器的凭据读取
+## 机构资源传输
 
-显式安装的本地适配器可调用 `ctx.oidcAccounts.resolveBoundCredential(profileID, { credentialRef: "EDUWORK_API_KEY", runtimeBaseURL })`。`runtimeBaseURL` 必须精确等于该 Profile 已审查的模型服务基址；返回已同时验证 session、issuer/client ID、完整资源绑定和 Key 指纹的 DSH credential record，未满足条件则返回 `undefined`。适配器直接使用这份 record，不应在检查状态后另行解析同名 Key，避免两个读操作之间发生账户切换。此方法只在 Host 存在，没有 Typert/RPC 注册，也不属于服务端协议。适配器仍负责限制其请求目的地址；当前桌面/Web 后端支持该方法，旧 native 桥不会降级返回未经验证的 Key。
+扩展通过 modelResourceFetch(profileID, relativePath) 使用当前 Token 授权，见[账户扩展](account-extensions.md)。旧 resolveBoundCredential 已移除；可用性检查使用 Host-only modelAuthorization(profileID, expectedBaseURL)，只返回布尔值。
 
 ## DSH 升级流程
 
@@ -178,8 +143,8 @@ const dispose = ctx.enterpriseTransforms.register({
 1. 在分支中更新精确 peer version；
 2. 对比上述公开 export 和相关类型；
 3. 运行单元测试和打包测试；
-4. 启动纯 Web DSH Profile，完成登录、provision、模型调用、刷新和退出；
-5. 启动 Desktop/native 组合并比较用户可见行为；
+4. 启动纯 Web DSH Profile，完成登录、模型调用、刷新和退出；
+5. 启动 Desktop 组合并比较用户可见行为；
 6. 验证 Client loader 格式和 slot 名称；
 7. 审查 DSH 官方能力是否已替代任何本地 adapter 代码；
 8. 发布前在 `docs/compatibility.md` 记录结果。

package/docs/ecnu-reference.en.md

@@ -1,66 +1,9 @@
-# ECNU reference composition
+# Institution integration reference
 
 [简体中文](ecnu-reference.md) | **English**
 
-This repository uses East China Normal University / ChatECNU only as a concrete reference for the generic standard. The public example contains placeholders and no production endpoint, OIDC client identifier, API key, token, personal data, or logo asset.
+The public package contains no real institution endpoints, client registrations, accounts or quota data. Start from the [OIDC Token example](../examples/oidc-llm.enterprise-profile.example.json) or [LiteLLM example](../examples/litellm.enterprise-profile.example.json).
 
-The reference file is [`examples/ecnu.enterprise-profile.example.json`](../examples/ecnu.enterprise-profile.example.json).
+Own-account quota follows existing institutional server rules. Optional extensions use shared Host modelResourceFetch with the current Access Token and their existing parser. The public package defines no quota object or RPC.
 
-## Intended composition
-
-EduWork@ECNU composes the public core with institution extensions:
-
-```text
-DeepSeek Harness
-  + dsh-oidc
-      - standard OIDC identity
-      - worker-user-center-v1 Key Binding
-      - ECNU Enterprise Profile
-      - declarative ChatECNU Provider/models
-      - bounded brand/account UI and shared enterprise-model settings UI
-  + ECNU product plugins
-      - image-understanding fallback for text-only ecnu-max
-      - enterprise search route and official DSH result rendering
-      - product presets/skills/resources
-      - legacy native account bridge only (new desktops use the public desktop backend)
-      - quota or institution-specific business UI
-  + desktop shell/packaging/updater
-```
-
-New desktop compositions use the public `desktop` backend and host browser service for temporary loopback login; local functional validation uses `web`. The older Wails `native`/`enterpriseAccounts` bridge is a migration compatibility path, not a requirement for another institution. Trusted files manage organization configuration, while UI shows status and sign-in. Explicit institution plugins own quota, heartbeat and campus search; the public package does not request them. All modes follow the `EDUWORK_API_KEY` rules and complete deployment-binding checks without changing the existing OIDC/Key Binding wire.
-
-## Identity expectation
-
-The OIDC Provider should return standard UserInfo:
-
-```json
-{
-  "sub": "opaque-stable-subject",
-  "name": "Display Name"
-}
-```
-
-If `name` is absent, UI falls back to `sub`. The plugin does not call an ECNU-private profile endpoint and does not map `data.attributes.XM` or similar paths. This is deliberate: the organization OIDC service should expose the standard claim.
-
-## Model example
-
-The placeholder shows two common facts:
-
-- `ecnu-max`: text-only, large context, selectable reasoning efforts;
-- `ecnu-plus`: native text/image input, thinking enabled but no selectable reasoning-effort parameter.
-
-For `ecnu-plus`, `supportsReasoningEffort: false` removes the unsupported effort while preserving thinking behavior. For `ecnu-max`, a separate ECNU image-understanding plugin can register `enterpriseTransforms` to add an aggregate image capability without altering the profile or replacing the Provider route.
-
-## Before any public release
-
-ECNU maintainers must separately approve:
-
-- the GitHub organization and repository visibility;
-- copyright holder wording;
-- use of university/ChatECNU names and brand values;
-- public support and security contact addresses;
-- publication of the npm package name;
-- removal of every internal endpoint, identifier, log, archive, and credential;
-- the production deployment's privacy/security review.
-
-The existence of this reference document is not authorization to publish institutional infrastructure details or brand assets.
+See [migration](key-binding-protocol.en.md) for old profiles. Real environment configurations and diagnostic records stay outside the public repository.

package/docs/ecnu-reference.md

@@ -1,66 +1,9 @@
-# 华东师范大学参考组合
+# 机构接入参考
 
 **简体中文** | [English](ecnu-reference.en.md)
 
-本仓库仅以华东师范大学 / ChatECNU 作为通用标准的一项具体参考实现。公开示例全部使用占位符，不包含生产 endpoint、OIDC Client ID、API Key、Token、个人数据或 Logo 资产。
+公共包不包含真实机构地址、客户端注册信息、账号或配额数据。部署方可使用[OIDC Token 示例](../examples/oidc-llm.enterprise-profile.example.json)或[LiteLLM 示例](../examples/litellm.enterprise-profile.example.json)。
 
-参考文件为 [`examples/ecnu.enterprise-profile.example.json`](../examples/ecnu.enterprise-profile.example.json)。
+本人配额沿用机构服务端既有规则。可选机构扩展通过共享 Host 的 modelResourceFetch 发送当前 Access Token，并复用自己的解析器；公共包不定义配额对象或 RPC。
 
-## 预期组合
-
-EduWork@ECNU 使用公共核心加机构扩展的组合：
-
-```text
-DeepSeek Harness
-  + dsh-oidc
-      - 标准 OIDC 身份
-      - worker-user-center-v1 Key Binding
-      - ECNU Enterprise Profile
-      - 声明式 ChatECNU Provider/模型
-      - 有边界的品牌/账号 UI 和共用企业模型设置 UI
-  + ECNU 产品插件
-      - 面向纯文本 ecnu-max 的图像理解回退
-      - 企业搜索通路和 DSH 官方结果渲染
-      - 产品预设、Skill 和资源
-      - 仅旧版需要的 native 账号桥（新桌面使用公共 desktop 后端）
-      - 配额或机构特有业务 UI
-  + 桌面外壳、打包与更新器
-```
-
-新桌面组合使用公共 `desktop` 后端，通过宿主浏览器服务完成临时 loopback 登录；本机功能验证用 `web` 后端。旧 Wails 发行版的 `native`/`enterpriseAccounts` 桥属于迁移兼容路径，不是新机构接入要求。企业配置由可信文件管理，界面负责展示和登录。配额、心跳、校内搜索由明确安装的机构插件提供；公版不请求这些服务。所有模式共用 `EDUWORK_API_KEY` 规则和完整部署绑定校验，不改变现有 OIDC/Key Binding wire。
-
-## 身份预期
-
-OIDC Provider 应返回标准 UserInfo：
-
-```json
-{
-  "sub": "opaque-stable-subject",
-  "name": "Display Name"
-}
-```
-
-如果没有 `name`，UI 会降级显示 `sub`。插件不会调用 ECNU 私有人员信息接口，也不会映射 `data.attributes.XM` 等路径。这是有意设计：机构 OIDC 服务应提供标准 claim。
-
-## 模型示例
-
-占位示例展示了两类常见模型事实：
-
-- `ecnu-max`：纯文本、大上下文、支持选择 reasoning effort；
-- `ecnu-plus`：原生文本/图片输入，支持 thinking，但不支持选择 reasoning-effort 参数。
-
-对 `ecnu-plus` 设置 `supportsReasoningEffort: false`，会移除不支持的 effort 参数但保留 thinking。对 `ecnu-max`，独立的 ECNU 图像理解插件可注册 `enterpriseTransforms`，在不修改 Profile、不替换 Provider 路由的情况下增加聚合图像能力。
-
-## 任何公开发布之前
-
-ECNU 维护者必须另行批准：
-
-- GitHub 组织和仓库可见性；
-- 版权主体表述；
-- 校名、ChatECNU 名称和品牌值的使用；
-- 公开支持和安全联系地址；
-- npm 包名发布；
-- 清除全部内部 endpoint、标识符、日志、归档和凭据；
-- 生产部署的隐私与安全审查。
-
-存在这份参考文档不代表已获准发布任何机构基础设施细节或品牌资产。
+旧 Key Binding 配置迁移见[迁移说明](key-binding-protocol.md)。真实环境的联调日志和配置不进入公开仓库。

package/docs/enterprise-profile.en.md

@@ -1,12 +1,12 @@
 # Enterprise Profile specification (`dsh-oidc/v1alpha1`)
 
-> Candidate extension: omit both keyBinding/provider for identity-only OIDC; brand is optional. Resource mode accepts keyBinding.type=eduwork-resources-v1 (default worker-user-center-v1). provider.modelSource=discovery may omit models; normal profile mode requires models. See [Public resource protocol](public-resource-protocol.en.md).
+> Current source accepts token gateway profiles or identity-only OIDC. Key Binding profiles are removed; see [migration](key-binding-protocol.en.md).
 
 [简体中文](enterprise-profile.md) | **English**
 
 ## Status and conformance
 
-This document specifies the data contract consumed by `dsh-oidc` `0.2.x`. The key words **MUST**, **MUST NOT**, **REQUIRED**, **SHOULD**, **SHOULD NOT**, and **MAY** are interpreted as described by RFC 2119 and RFC 8174.
+This document specifies the current unpublished source branch contract. See the migration link above for previously released configurations. The key words **MUST**, **MUST NOT**, **REQUIRED**, **SHOULD**, **SHOULD NOT**, and **MAY** are interpreted as described by RFC 2119 and RFC 8174.
 
 The canonical machine-readable schema is [`schema/enterprise-profile.v1alpha1.schema.json`](../schema/enterprise-profile.v1alpha1.schema.json). Runtime validation is intentionally stricter in several security-sensitive URL cases. A conforming profile MUST pass both JSON Schema validation and `normalizeEnterpriseProfile()`.
 
@@ -20,7 +20,6 @@ Profiles are trusted deployment configuration, not user input. Nevertheless, the
 - development HTTP needs an explicit loopback allowance or exact development-origin allowlist;
 - URL credentials, fragments, and endpoint-base query strings are rejected;
 - only the built-in `openai-compatible` adapter can be selected;
-- Key Binding accepts only its protocol base and an optional local DSH credential reference; network paths and fields remain fixed;
 - logo data URLs accept PNG/WebP only, not SVG.
 
 A remote administration system MAY distribute profile JSON only if the host authenticates the source, verifies integrity, and stages changes through review. Downloaded JSON does not become safe merely because it contains no JavaScript.
@@ -33,12 +32,11 @@ A remote administration system MAY distribute profile JSON only if the host auth
 | `id` | yes | Profile ID matching `^[a-z][a-z0-9-]{0,63}$`. |
 | `displayName` | yes | Human-readable integration name. |
 | `organization` | no | Organization label; defaults to `displayName`. |
-| `nativeInstitutionID` | no | Identifier passed only to a native backend; defaults to `id`. |
-| `allowInsecureDevelopment` | no | Enables loopback HTTP for local development. Network HTTP additionally requires `insecureDevelopmentOrigin`. |
-| `insecureDevelopmentOrigin` | no | Exact non-TLS development origin. It is accepted only together with `allowInsecureDevelopment: true`, and every HTTP OIDC/key-binding/provider endpoint must use this exact origin. Never ship it in a production profile. |
+| `allowInsecureDevelopment` | Optional boolean; `false` (default) accepts HTTPS only, `true` also accepts HTTP service URLs. |
+| `insecureDevelopmentOrigin` | Deprecated; accepted in old files but ignored. Omit from new configurations. |
 | `brand` | no | Bounded presentational values. |
-| `oidc` | yes | OIDC public-client facts. |
-| `keyBinding` | resource mode | Key Binding base URL and optional local DSH credential reference. |
+| `oidc` | identity-only | OIDC public-client facts; cannot include auth or provider. |
+| `auth` | models | Full discovery URL; see the gateway guide for explicit protocol fields. |
 | `provider` | resource mode | One local OpenAI-compatible Provider route and model list. |
 
 ## Branding
@@ -72,31 +70,12 @@ Profiles MUST NOT include logos or names without permission from the rights hold
 - `clientId` identifies a public client. No client secret belongs in a profile or this plugin.
 - `scopes` MUST contain `openid` and `profile`, contain no whitespace within an item, and contain no duplicates.
 - `offline_access` SHOULD be requested when the Provider issues refresh tokens and policy allows it.
-- Key Binding authorization scopes are deployment-specific but SHOULD use the names in the reference example.
 
 The Web redirect URI is fixed to `http://127.0.0.1:<DSH-port>/oauth/callback`. The host and path are not configurable; the port follows the DSH WebServer's actual listening port.
 
-## Key Binding object
+## Gateway auth
 
-```json
-{
-  "baseURL": "https://ai.example.edu/api/worker/v1",
-  "credentialRef": "EDUWORK_API_KEY"
-}
-```
-
-| Field | Required | Meaning |
-| --- | --- | --- |
-| `baseURL` | yes | Base URL of the `worker-user-center-v1` Key Binding interface group. |
-| `credentialRef` | no | Local DSH Credential Provider name under which the bound model API key is stored. It must match `^[A-Za-z_][A-Za-z0-9_]*$` and is limited to 128 characters. |
-
-The Provider ID sent on the wire is always `provider.id`. An omitted `credentialRef` now defaults to `EDUWORK_API_KEY`. Legacy automatic references derived from this Profile’s `id` or `provider.id` (uppercase, non-alphanumerics replaced with `_`, followed by `_API_KEY`) normalize to this common name. Other explicit references remain unchanged.
-
-`credentialRef` names a local secret-store entry; it is not a key and is never sent over the network. Normal deployments use `EDUWORK_API_KEY`; explicit independent overrides such as `MY_TEST_MODEL_KEY` remain supported. With a shared reference, only a verified login whose bound credential fingerprint matches the current key may read it. Rebinding leaves other profiles disconnected from that key, and their logout cannot delete a key written by another login. Independently configured personal model credentials are unaffected.
-
-An upgrade imports an old key only when issuer, client ID, management URL, runtime URL and Provider ID all match and only the automatic reference changed. It neither overwrites nor adopts an occupied target. Unproven ownership retains identity but requires reconnecting model resources. Pre-fingerprint sessions are accepted only with an identical complete binding and unambiguous reference ownership.
-
-Endpoint paths, request/response fields, and Provider ID semantics are protocol facts and MUST NOT be customized by profiles. If a native host returns `runtimeCredentialRef`, it MUST equal the normalized profile value or the plugin fails closed.
+Use [LiteLLM](gateway-auth/README_EN.md) or [experimental oidc-llm](gateway-auth/experimental-oidc-llm.en.md). auth.discoveryUrl is explicit; OIDC mode requires the experimental flag, clientId and identityMode. No model-key fallback is supported.
 
 ## Provider object
 
@@ -107,7 +86,7 @@ The Provider object is data interpreted by a local audited adapter.
 | `id` | yes | DSH route ID, independent of the shared default credential reference. Must be unique across loaded profiles. |
 | `displayName` | no | User-facing Provider name. |
 | `adapter` | yes | Exact string `openai-compatible`. |
-| `baseURL` | yes | HTTPS OpenAI-compatible API base. |
+| `baseURL` | not configurable | Derived only from validated gateway discovery. |
 | `reasoning` | no | Default DSH/pi-ai reasoning level: `off`, `minimal`, `low`, `medium`, `high`, `xhigh`, or `max`; default `high`. |
 | `defaultContextWindow` | no | Positive safe integer, default 262144. |
 | `defaultMaxTokens` | no | Positive safe integer, default 32768. |
@@ -117,8 +96,8 @@ The Provider object is data interpreted by a local audited adapter.
 | `streamIdleTimeoutMs` | no | Positive idle timeout, default 300000. |
 | `retryPolicy` | no | DSH provider-owned retry policy; default normal/2 retries. |
 | `compat` | no | Bounded pi-ai OpenAI compatibility facts. |
-| `modelSource` | no | `profile` (default) or `discovery`; discovery requests `/models` with the managed key. |
-| `models` | profile mode | 1–128 unique entries; discovery may omit them, and configured entries supply reviewed capabilities. |
+| `modelSource` | no | Only discovery, the default; fetches /models with the current Access Token. |
+| `models` | no | Reviewed model capabilities; cannot expose models absent from the authorized catalog. |
 
 `retryPolicy.mode` is `normal` or `always`. `always` can retry indefinitely until success, cancellation, or disposal and SHOULD NOT be enabled without an explicit product decision. The policy is validated again by DSH.
 

package/docs/enterprise-profile.md

@@ -1,12 +1,12 @@
 # Enterprise Profile 规范（`dsh-oidc/v1alpha1`）
 
-> 当前候选扩展：纯身份模式同时省略 keyBinding/provider；brand 可省略。资源模式支持 keyBinding.type=eduwork-resources-v1，默认兼容 worker-user-center-v1。provider.modelSource=discovery 时 models 可省略；默认 profile 模式仍要求模型列表。见 [公共资源协议](public-resource-protocol.md)。
+> 当前源码接受 Token 网关或纯身份 OIDC 配置。Key Binding 配置已移除，见[迁移说明](key-binding-protocol.md)。
 
 **简体中文** | [English](enterprise-profile.en.md)
 
 ## 状态与符合性
 
-本文规定 `dsh-oidc` `0.2.x` 使用的数据契约。关键词 **必须（MUST）**、**不得（MUST NOT）**、**必需（REQUIRED）**、**应该（SHOULD）**、**不应该（SHOULD NOT）** 和 **可以（MAY）** 按 RFC 2119 与 RFC 8174 解释。
+本文规定当前未发布源码分支使用的数据契约，旧已发布版本的配置迁移见上文链接。关键词 **必须（MUST）**、**不得（MUST NOT）**、**必需（REQUIRED）**、**应该（SHOULD）**、**不应该（SHOULD NOT）** 和 **可以（MAY）** 按 RFC 2119 与 RFC 8174 解释。
 
 权威机器可读 Schema 为 [`schema/enterprise-profile.v1alpha1.schema.json`](../schema/enterprise-profile.v1alpha1.schema.json)。运行时对若干安全敏感 URL 的校验有意比 JSON Schema 更严格。符合规范的 Profile 必须同时通过 JSON Schema 和 `normalizeEnterpriseProfile()` 校验。
 
@@ -17,10 +17,9 @@ Profile 是受信任的部署配置，不是用户输入。即便如此，解析
 - 根对象和所有涉及可执行行为的嵌套对象都会拒绝未知字段；
 - 序列化后的 Profile 总大小不超过 512 KiB；
 - 生产 URL 必须使用 HTTPS；
-- 只有显式 loopback 主机可以在开发环境使用 HTTP；
+- 开发环境使用 HTTP 必须显式允许 loopback，或绑定精确的开发 origin；
 - 拒绝 URL 凭据、fragment 和 endpoint-base query string；
 - 只能选择内置的 `openai-compatible` adapter；
-- Key Binding 只接受协议基址和可选的本地 DSH 凭据引用，不能改写网络路径或字段；
 - logo data URL 只接受 PNG/WebP，不接受 SVG。
 
 远程管理系统只有在宿主能够认证来源、校验完整性并通过审查流程暂存变更时，才可以分发 Profile JSON。下载的 JSON 不会仅仅因为不包含 JavaScript 就自动变得安全。
@@ -33,12 +32,11 @@ Profile 是受信任的部署配置，不是用户输入。即便如此，解析
 | `id` | 是 | 匹配 `^[a-z][a-z0-9-]{0,63}$` 的 Profile ID。 |
 | `displayName` | 是 | 面向用户的集成名称。 |
 | `organization` | 否 | 机构名称；默认使用 `displayName`。 |
-| `nativeInstitutionID` | 否 | 仅传给 native 后端的标识符；默认使用 `id`。 |
-| `allowInsecureDevelopment` | 否 | 为本地开发启用 loopback HTTP。网络 HTTP 还必须配置 `insecureDevelopmentOrigin`。 |
-| `insecureDevelopmentOrigin` | 否 | 精确的非 TLS 开发 origin。只有与 `allowInsecureDevelopment: true` 一起使用时才有效，且所有 HTTP OIDC/Key Binding/Provider endpoint 必须使用该 origin。不得放入生产 Profile。 |
+| `allowInsecureDevelopment` | 可选布尔值，默认 `false` 仅接受 HTTPS；`true` 也接受 HTTP 服务地址。 |
+| `insecureDevelopmentOrigin` | 已废弃，仅兼容旧文件；不再参与校验，新配置无需填写。 |
 | `brand` | 否 | 有边界的展示配置。 |
-| `oidc` | 是 | OIDC public client 配置事实。 |
-| `keyBinding` | 资源模式 | Key Binding 基础 URL，以及可选的本地 DSH 凭据引用。 |
+| `oidc` | 纯身份模式 | OIDC public client 信息，不得同时配置 auth 或 provider。 |
+| `auth` | 模型模式 | 完整发现地址，协议字段见网关指南。 |
 | `provider` | 资源模式 | 一个本地 OpenAI-compatible Provider 路由和模型列表。 |
 
 ## 品牌替换
@@ -72,31 +70,12 @@ Profile 是受信任的部署配置，不是用户输入。即便如此，解析
 - `clientId` 标识 public client。Profile 和本插件都不应包含 client secret。
 - `scopes` 必须包含 `openid` 和 `profile`；每项内部不得包含空白，且不得重复。
 - 当 Provider 会签发 refresh token 且策略允许时，应该请求 `offline_access`。
-- Key Binding 授权 scope 由部署决定，但建议使用参考示例中的名称。
 
 Web 重定向地址固定为 `http://127.0.0.1:<DSH端口>/oauth/callback`。host 和 path 不可配置；端口取 DSH WebServer 的实际监听端口。
 
-## Key Binding 对象
+## 网关 auth
 
-```json
-{
-  "baseURL": "https://ai.example.edu/api/worker/v1",
-  "credentialRef": "EDUWORK_API_KEY"
-}
-```
-
-| 字段 | 必需 | 含义 |
-| --- | --- | --- |
-| `baseURL` | 是 | `worker-user-center-v1` Key Binding 接口组的基址。 |
-| `credentialRef` | 否 | 保存绑定后模型 API Key 的本地 DSH Credential Provider 名称。必须匹配 `^[A-Za-z_][A-Za-z0-9_]*$`，最长 128 字符。 |
-
-请求中的 Provider ID 固定取 `provider.id`。`credentialRef` 省略时统一为 `EDUWORK_API_KEY`。旧配置中按本 Profile 的 `id` 或 `provider.id` 大写、非字母数字替换为 `_` 后追加 `_API_KEY` 的引用，按兼容别名规范化到同一默认值，不再按企业生成名称。其他显式引用原样保留。
-
-`credentialRef` 只是本地秘密存储的引用名，不是 API Key，不发送给 OIDC、Key Binding 或模型服务。常规部署使用 `EDUWORK_API_KEY`；需要额外独立管理的显式引用仍可使用例如 `MY_TEST_MODEL_KEY`。默认槽位记录当前绑定的企业 Key；多个 Profile 共用时，仅凭据指纹与当前 Key 匹配的已验证登录可以读取它。重新绑定后，其他 Profile 不会借用该 Key，登出也不会删除其他登录写入的新 Key。个人模型使用的独立引用不受影响。
-
-升级只在同一 issuer、client ID、资源管理基址、模型服务基址、Provider ID 且仅旧自动引用改名时迁移原 Key。新槽位已有值时既不覆盖也不自动接管；无法证明归属时保留身份并重新连接模型资源。旧会话缺少指纹时，仅完整绑定相同且引用归属无歧义才兼容。
-
-Endpoint 路径、请求/响应字段和 Provider ID 语义属于协议事实，不得由 Profile 自定义。Native 宿主若返回 `runtimeCredentialRef`，其值必须与本字段规范化后的结果一致，否则插件失败关闭。
+选择 [LiteLLM](gateway-auth/README.md) 或 [oidc-llm 实验](gateway-auth/experimental-oidc-llm.md)。auth.discoveryUrl 必须完整；实验 OIDC 另外填写显式开关、clientId 和 identityMode。不支持回退到模型 Key 流程。
 
 ## Provider 对象
 
@@ -107,7 +86,7 @@ Provider 对象是由本地、经过审查的 adapter 解释的数据。
 | `id` | 是 | DSH 路由 ID；在所有已加载 Profile 中必须唯一。 |
 | `displayName` | 否 | 面向用户的 Provider 名称。 |
 | `adapter` | 是 | 精确字符串 `openai-compatible`。 |
-| `baseURL` | 是 | HTTPS OpenAI-compatible API 基址。 |
+| `baseURL` | 不得配置 | 只能来自已校验的网关发现。 |
 | `reasoning` | 否 | 默认 DSH/pi-ai reasoning level，取值为 `off`、`minimal`、`low`、`medium`、`high`、`xhigh`、`max`，默认为 `high`。 |
 | `defaultContextWindow` | 否 | 正安全整数，默认 262144。 |
 | `defaultMaxTokens` | 否 | 正安全整数，默认 32768。 |
@@ -117,8 +96,8 @@ Provider 对象是由本地、经过审查的 adapter 解释的数据。
 | `streamIdleTimeoutMs` | 否 | 正数空闲超时，默认 300000。 |
 | `retryPolicy` | 否 | 由 DSH Provider 管理的重试策略；默认 normal/重试 2 次。 |
 | `compat` | 否 | 有边界的 pi-ai OpenAI 兼容事实。 |
-| `modelSource` | 否 | `profile`（默认）或 `discovery`；后者通过受管 Key 请求 `/models`。 |
-| `models` | `profile` 模式 | 1–128 个唯一模型条目；`discovery` 可省略，已配置条目作为能力声明。 |
+| `modelSource` | 否 | 仅支持 discovery，默认值；使用当前 Access Token 读取 /models。 |
+| `models` | 否 | 已审查的模型能力元数据，不得扩大获授权目录。 |
 
 `retryPolicy.mode` 可以是 `normal` 或 `always`。`always` 可能一直重试，直到成功、取消或销毁；没有明确产品决策时不应启用。该策略还会由 DSH 再次校验。