@eduwork/dsh-oidc 0.1.0-alpha.11 → 0.2.0

package/CHANGELOG.en.md

@@ -4,7 +4,64 @@
 
 All notable changes are documented here. The format follows Keep a Changelog principles and the project uses Semantic Versioning with pre-1.0 qualifications described in `docs/compatibility.en.md`.
 
-## [Unreleased]
+## [0.2.0] - 2026-09-11
+
+- Freeze the validated dev.7 implementation under a stable semantic version and update npm installation instructions for DSH `0.1.5-rc.1`. Distribution assembly pins version and integrity. Identity, managed keys, models and default selection remain public; quota and heartbeat belong to institution extensions.
+- No runtime source changes from dev.7. Candidate notes below preserve migration history and validation boundaries. Consult the registry for npm publication status; GitHub pushes and Releases are separate actions.
+
+- 2026-09-11 source preparation: pin the registry-installable RC.1 development/CI dependency closure; check its lock before CI installation. Correct bilingual identity-only/desktop/server-request/migration documentation and source entry points. Package version and frozen dev.7 artifact remain unchanged; no publication.
+
+
+- Local candidate `0.2.0-dev.20260910.7`: unify the default as `EDUWORK_API_KEY`, accepting legacy automatic Profile/Provider names. Migrate only identical deployment bindings without overwriting the target. Session credential fingerprints prevent another login from reading or clearing the active key. Add Host-only `resolveBoundCredential` for extension adapters; no new RPC or organization-switching UI.
+
+- `0.2.0-dev.20260910.6`: public OIDC now owns identity/key/models only. Removed quota HTTP, normalization, RPC fields and UI; legacy native mode no longer calls quota. Added a Host-only bounded model-resource transport and the official `oidc.account.menu.details` child slot for explicitly installed institution extensions.
+- Exact RC.1 closure: 264 DSH packages, 78 tests and 6 compiled-browser checks; includes no implicit quota requests, host credential/destination boundaries and logout races. Existing managed keys and personal model selection survive. Public RFC/OpenAPI no longer require quota; heartbeat remains institution-only.
+
+
+- `0.2.0-dev.20260910.5`: restore the public avatar menu with quota, refresh, sign-out, keyboard navigation and outside-focus dismissal, including collapsed sidebars. Desktop callback cards use configured branding and system fonts without authorization secrets or raw server errors.
+- Adapt to official DSH `0.1.5-rc.1` PiAi `modelErrors`, preserving model capabilities and default selection. Serialize vault cleanup and reject late identity/key/quota writes after logout. A coherent 264-package closure, 75 tests and 7 compiled-browser checks pass; final native assembly belongs to the mainline.
+- Expand the server RFC across identity, resource discovery, key lifecycle, models, quota, refresh/logout, versions and errors; validate resource OpenAPI examples using the real normalizer. Heartbeat is a default-off optional proposal only.
+
+- Desktop acceptance revised the same `.20260910.4` candidate: onboarding stays visible with disabled actions while the key is connected but default-model selection is still pending, and closes only after selection completes.
+
+- Unpublished candidate `0.2.0-dev.20260910.4` fixes independent stale account state in sign-in, sidebar and organization settings. Late reads cannot overwrite newer state; official credential events and connection recovery refresh all consumers. Explicit sign-in/provisioning uses DSH 0.1.5 default/current-session model APIs; upgrade recovery preserves usable personal choices and personal credentials. Added race regressions, compiled-client rendering, real HTTP PKCE/Key/default-settings tests and a local synthetic server for desktop acceptance.
+
+- Unpublished candidate `0.2.0-dev.20260910.3` restores compatibility with the existing `worker.user-center.v1` resource protocol while retaining new protocols and unknown-version checks. Errors distinguish authenticated identity from disconnected model resources. File-managed settings offer host-backed configuration and example buttons; organization settings stay read-only and personal models remain available.
+
+- Unpublished `0.2.0-dev.20260910.1` adds desktop OIDC without persistent WebServer: temporary loopback PKCE, Host browser service, safe result polling and cancellation, preserving host credentials and existing resource protocols. See [desktop host integration](docs/desktop-host.en.md).
+
+- Unpublished 0.2.0-dev.20260909.1 adds optional identity-only login and public runtime model/quota integration with legacy wire compatibility; the host and client share a single Typert schema.
+
+
+### Changed
+
+- Advance the local candidate to `0.1.0-dev.20260908.1`: restore the internal thinking signal lost in the previous effort-capability change. `compat.supportsReasoningEffort: false` still hides effort choices and omits `reasoning_effort`, while thinking follows the profile default. Historical user efforts cannot change that default. Non-reasoning models and explicit profile `off` retain their existing behavior.
+- Add a 19-request real PiAi-to-HTTP regression covering direct, prepared, and DSH LLM calls, constrained model levels, historical `medium`/`xhigh`/`off`, non-reasoning models, and explicitly disabled thinking; checking internal request shape alone is insufficient.
+- Advanced the candidate to `0.1.0-dev.20260907.3`: the complete DSH peer closure adds reviewed `0.1.3-alpha.2` (`82a5fd61…`) while continuing to reject mixed trees. An isolated Runtime with 250 coherent packages passes the complete check and 32 tests without OIDC runtime-source changes.
+- Added a repository handoff entry that distinguishes latest user/mainline messages, historical material, current compatibility evidence, and the separate GitHub, npm, and local-deployment boundaries.
+- Advanced the candidate to `0.1.0-dev.20260907.2`: the model-capability chain now preserves the exact seven reasoning-effort IDs, per-model defaults, and independent wire values. Undeclared levels are no longer supplied by pi-ai defaults, and `xhigh` is never rewritten as `max`.
+- Historical provider defaults conservatively fall back within each model's supported efforts. Model resolution, call preparation, and transport share one capability snapshot; invalid efforts fail before HTTP while thinking-only and non-reasoning semantics remain distinct.
+- Added local development candidate `0.1.0-dev.20260907.1`: the complete DSH peer closure explicitly accepts either `0.1.2-rc.1` or `0.1.3-alpha.1` while rejecting every mixed-version tree.
+- Audited upstream `dsh-v0.1.3-alpha.1` (`d347e703…`) source contracts and an isolated Runtime. SessionHandle, session v2/locking, and asynchronous `agentLoop.create()` are outside OIDC's runtime dependency surface, so no plugin runtime source change is required.
+- Extended the contract probe with OidcAccountService construction and all 13 Typert Remote markers while retaining Settings, LLM/Pi, WebServer, credentials, attachment, and Client-slot coverage.
+
+## [0.1.0] - 2026-09-06
+
+### Changed
+
+- Updated the exact compatibility baseline to DeepSeek Harness `0.1.2-rc.1` (`a66e4702…`) and stopped claiming current support for the alpha.2 combination that is outside this release acceptance.
+- Expanded and locked the DSH peer closure, including the page package that declares `settings.general.item`, so an unlocked host cannot mix alpha.2 and rc.1 packages during npm resolution.
+- Audited Credential Provider, Settings, LLM/Pi Provider, WebServer, API Remotes, Typert, and Client page-slot contracts; added the automated `check:dsh` contract check.
+- Provider configuration now emits only declared fields and copies them into mutable data accepted by the rc.1 Settings/PiAi schema; reasoning and compat values are constrained to the rc.1 supported sets.
+- The Settings section now validates serviceability so schema-shaped values that cannot construct an enterprise Provider are rejected before persistence.
+- The Provider wrapper now delegates `imageRequestPricing` and follows rc.1's official attachment-to-read-only execution-path resolution chain.
+- Enterprise single brand slots now use an explicit negative priority to shadow rc.1's official brand entries without colliding at default priority 0 and aborting Client initialization.
+- Stabilized the npm package version as `@eduwork/dsh-oidc@0.1.0` while retaining `dsh-oidc/v1alpha1`, `oidcAccounts`, credential references, Provider identities, the settings namespace, and user data.
+- Expanded CI to a Node.js 22/24 matrix on Windows and Linux and added a manual workflow that checks/packages by default and publishes through npm Trusted Publishing only after explicit authorization.
+- Documentation-link and secret scans now explicitly ignore Git-excluded `dist/` acceptance artifacts so local caches cannot change source-check results.
+- Release governance now accurately records the initial single-maintainer phase and relies on retained independent technical review, CI/focused regression evidence, and an explicit maintainer decision. Until Trusted Publishing is configured, the first npm publication uses browser 2FA and does not claim provenance.
+- The npm package now includes the bilingual code of conduct, contribution, security, support, governance, and maintainer documents so README-relative links do not dangle after installation.
+- Test discovery is pinned to the repository's `test/*.test.js`, so Git-ignored local acceptance snapshots cannot change the discovered test set or count.
 
 ## [0.1.0-alpha.11] - 2026-09-05
 

package/CHANGELOG.md

@@ -4,7 +4,64 @@
 
 所有重要变更均记录于此。格式遵循 Keep a Changelog 原则；项目使用语义化版本，并遵循[兼容性与发布策略](docs/compatibility.md)中对 1.0 之前版本的说明。
 
-## [未发布]
+## [0.2.0] - 2026-09-11
+
+- 将已验收的 dev.7 运行实现冻结为稳定语义版本；补齐 DSH `0.1.5-rc.1` npm 安装指引，正式产品按精确版本与 integrity 装配。身份、托管 Key、模型及默认选择归属公版；配额和心跳由机构扩展提供。
+- 与 dev.7 相比无运行源码变更；下面的候选记录保留各次功能迁移和验证边界。npm 发布状态以 registry 为准，GitHub 推送及 Release 是独立动作。
+
+- 2026-09-11 源码准备：锁定 npm 可安装的 RC.1 开发/CI 依赖闭包，CI 安装前验证锁；校正中英文纯身份接入、桌面、服务端请求、凭据迁移文档与开发入口。包版本和已冻结 dev.7 产物保持不变，本轮未发布。
+
+
+- 本地候选 `0.2.0-dev.20260910.7`：企业 Key 默认统一为 `EDUWORK_API_KEY`，兼容本 Profile/Provider 的旧自动名称；仅在完整部署绑定一致时迁移，不覆盖新槽位。共享引用按会话 Key 指纹校验归属，避免其他登录读取或清除当前 Key。增加仅供 Host 使用的 `resolveBoundCredential`，供机构适配器读取同一份已验证凭据；无新增 RPC/企业切换界面。
+
+- `0.2.0-dev.20260910.6`：公共 OIDC 只保留身份/Key/模型；移除配额 HTTP、归一化、RPC 字段和 UI，旧 native 模式不再调用配额桥。新增 Host 专属的有界模型资源运输和官方 `oidc.account.menu.details` 子插槽，由显式安装的机构扩展提供附加账户内容。
+- 精确 RC.1 闭包 264 个 DSH 包、78 项测试及 6 项编译浏览器检查通过，覆盖无隐式配额请求、凭据/地址边界和注销竞态。保留已有托管 Key 与个人模型选择。公共 RFC/OpenAPI 不再要求配额，心跳仍仅属于机构扩展。
+
+
+- `0.2.0-dev.20260910.5`：恢复公共头像账户菜单（配额、刷新、注销、键盘操作及失焦关闭），支持折叠侧栏；桌面回调新增无外部字体的品牌卡片，不显示授权秘密或服务端原始错误。
+- 适配官方 DSH `0.1.5-rc.1` 的 PiAi `modelErrors` 契约，保留精确模型能力和默认选模；退出时串行清理保险库，拒绝旧请求写回身份/Key/配额。264 包一致闭包、75 项测试与 7 项编译浏览器回归通过；双桌面最终装配由主线验收。
+- 服务端 RFC 完整覆盖身份、资源发现、Key 生命周期、目录、配额、刷新/注销、版本和错误处理；资源 OpenAPI 示例经过实际归一化器验证。心跳只新增默认关闭的可选协议草案。
+
+- 同一 `.20260910.4` 候选在桌面联验后修正选模竞态：创建 Key 已完成但默认模型尚在保存时，登录引导保持可见且操作禁用；选模完成后才收起。
+
+- 未发布候选 `0.2.0-dev.20260910.4`：修复登录页、侧栏与企业设置的独立旧状态；拒绝迟到查询覆盖新状态，监听官方凭据事件及连接恢复。明确登录/创建凭据后，使用 DSH 0.1.5 的默认模型和当前会话模型接口；升级时仅修复不可用默认值，保留个人凭据与可用选择。增加共享状态竞态、编译客户端显示、真实 HTTP PKCE/Key/默认设置的回归及双桌面验收用本机模拟服务。
+
+- 未发布候选 `0.2.0-dev.20260910.3` 恢复已有资源协议 `worker.user-center.v1` 的兼容，同时保留新协议及未知版本检查；错误提示区分已登录身份与尚未连接的模型资源。配置文件模式增加宿主支持的“打开配置文件 / 查看示例”入口；企业配置保持只读，个人模型仍可使用。
+
+- 未发布候选 `0.2.0-dev.20260910.1` 新增无常驻 WebServer 的桌面 OIDC：短时 loopback PKCE、Host 浏览器服务、安全登录轮询与取消，继续使用宿主保险库接口及原资源协议。见 [桌面宿主接入](docs/desktop-host.md)。
+
+- 未发布候选 0.2.0-dev.20260909.1 新增纯身份模式及公共模型/配额协议，保留原部署 wire；Host/Client 共享同一份 Typert schema。
+
+
+### 变更
+
+- 候选版本推进至 `0.1.0-dev.20260908.1`：修复上一轮模型档位适配遗漏 thinking-only 内部启用信号的问题。`compat.supportsReasoningEffort: false` 继续隐藏档位且不发送 `reasoning_effort`，同时按 Profile 默认值保留 thinking；历史会话中的 effort 不改变该默认值。无 reasoning 模型及 Profile 的 `off` 行为保持不变。
+- 新增真实 PiAi 到 HTTP 的 19 次请求回归，覆盖直接调用、预备调用、DSH LLM 调用、受限模型档位、历史 `medium`/`xhigh`/`off`、无 reasoning 及明确关闭 thinking；避免仅检查内部请求形状而遗漏过线行为。
+- 候选版本推进至 `0.1.0-dev.20260907.3`：完整 DSH peer 闭包增加已复核的 `0.1.3-alpha.2`（`82a5fd61…`），并继续拒绝混版依赖树；250 个一致包的隔离 Runtime 通过完整检查和 32 项测试，无需修改 OIDC 运行源码。
+- 新增仓库接手入口说明，明确最新用户/主线消息、历史材料、兼容事实以及 GitHub、npm 和本地部署的边界。
+- 候选版本推进至 `0.1.0-dev.20260907.2`：模型能力链路精确保留七种 reasoning effort ID、模型级默认值和独立过线值，未声明档位不再由 pi-ai 缺省补出，`xhigh` 不会被映射为 `max`。
+- Provider 级历史默认值按模型有效档位保守回落；模型解析、调用准备和实际传输使用同一份能力快照，非法档位在任何 HTTP 请求前拒绝，同时保留 thinking-only 与无 reasoning 两种不同语义。
+- 增加本地开发候选 `0.1.0-dev.20260907.1`：完整 DSH peer 闭包明确允许 `0.1.2-rc.1` 或 `0.1.3-alpha.1`，同时拒绝任何混版依赖树。
+- 对上游 `dsh-v0.1.3-alpha.1`（`d347e703…`）完成源码契约核对和隔离 Runtime 验证；SessionHandle、session v2/锁和异步 `agentLoop.create()` 不在 OIDC 运行依赖面内，无需修改插件运行源码。
+- 契约探针新增 OidcAccountService 构造及 13 个 Typert Remote 标记检查，并继续覆盖 Settings、LLM/Pi、WebServer、credentials、附件和客户端插槽。
+
+## [0.1.0] - 2026-09-06
+
+### 变更
+
+- 兼容基线精确更新至 DeepSeek Harness `0.1.2-rc.1`（`a66e4702…`），不再声明支持未完成本轮验收的 alpha.2 组合。
+- 扩充并锁定 DSH peer 闭包，显式包含声明 `settings.general.item` 的页面包，避免 npm 在未锁定宿主中混装 alpha.2 与 rc.1。
+- 逐项核对 Credential Provider、Settings、LLM/Pi Provider、WebServer、API Remotes、Typert 和 Client 页面插槽；新增 `check:dsh` 自动契约检查。
+- Provider 配置只输出已声明字段，并复制为 rc.1 Settings/PiAi schema 可解析的可变数据；同时将 reasoning/compat 值域收紧到 rc.1 支持集合。
+- Settings section 增加可服务性校验，阻止 schema 虽可解析、但无法构造企业 Provider 的配置被持久化。
+- Provider 包装器补齐 `imageRequestPricing` 委托，并沿用 rc.1 官方附件到执行环境只读路径的解析链路。
+- 企业品牌单插槽使用显式负优先级覆盖 rc.1 官方品牌项，避免与默认优先级 0 冲突而中断 Client 初始化。
+- npm 包版本稳定为 `@eduwork/dsh-oidc@0.1.0`；保留 `dsh-oidc/v1alpha1`、`oidcAccounts`、凭据引用、Provider 标识、设置命名空间和用户数据。
+- CI 扩展为 Windows/Linux 上的 Node.js 22/24 矩阵，并增加默认只检查/打包、显式授权后才通过 npm Trusted Publishing 发布的手动工作流。
+- 文档链接和敏感信息检查显式忽略已被 Git 排除的 `dist/` 验收产物，避免本地缓存影响源码检查结果。
+- 发布治理如实记录初期单一维护者模式，以独立技术复核、CI/专项回归和维护者决定留痕；Trusted Publisher 尚未配置时，首次 npm 发布使用浏览器 2FA 且不声称 provenance。
+- npm 包补齐行为准则、贡献、安全、支持、治理和维护者双语文档，避免 README 在安装包内出现悬空的相对链接。
+- 测试入口固定到仓库 `test/*.test.js`，避免被 Git 忽略的本地验收快照改变测试发现范围和计数。
 
 ## [0.1.0-alpha.11] - 2026-09-05
 

package/CODE_OF_CONDUCT.en.md

@@ -0,0 +1,17 @@
+# Code of conduct
+
+[简体中文](CODE_OF_CONDUCT.md) | **English**
+
+We are committed to a professional, inclusive, and harassment-free project.
+
+Participants must:
+
+- discuss ideas and code rather than personal characteristics;
+- assume good intent while accepting evidence-based correction;
+- protect private security reports, institutional information, and personal data;
+- avoid harassment, threats, discriminatory language, sexualized conduct, doxxing, and sustained disruption;
+- respect maintainer decisions made to protect users, protocol stability, licensing, or security.
+
+Maintainers may edit, hide, reject, or remove contributions and may temporarily or permanently restrict participation when behavior threatens contributors or users. Enforcement should be proportionate, documented privately where appropriate, and avoid disclosing victims or security-sensitive details.
+
+General conduct concerns may use an issue that contains no personal or sensitive details. For harassment, threats, doxxing, or another incident requiring confidentiality, use GitHub [Private Vulnerability Reporting](https://github.com/freedomkk-qfeng/dsh-oidc/security/advisories/new) and prefix the title with “Code of Conduct”. Do not disclose an affected person's identity or evidence attachments publicly.

package/CODE_OF_CONDUCT.md

@@ -0,0 +1,17 @@
+# 行为准则
+
+**简体中文** | [English](CODE_OF_CONDUCT.en.md)
+
+我们致力于维护专业、包容且无骚扰的项目环境。
+
+参与者必须：
+
+- 讨论观点和代码，而不是个人特征；
+- 假设善意，同时接受基于证据的纠正；
+- 保护私有安全报告、机构信息和个人数据；
+- 避免骚扰、威胁、歧视性语言、性化行为、人肉搜索和持续扰乱；
+- 尊重维护者为了保护用户、协议稳定性、许可证或安全而作出的决定。
+
+当行为威胁贡献者或用户时，维护者可以编辑、隐藏、拒绝或删除贡献，也可以临时或永久限制参与。执行措施应当适度；适合时应私下记录，并避免暴露受害者或安全敏感细节。
+
+一般行为问题可以创建不含个人敏感信息的 Issue。需要保密处理的骚扰、威胁、人肉搜索或其他行为事件，请使用 GitHub [Private Vulnerability Reporting](https://github.com/freedomkk-qfeng/dsh-oidc/security/advisories/new)，并在标题中标注“Code of Conduct”。不要在公开渠道披露受影响者身份或证据附件。

package/CONTRIBUTING.en.md

@@ -0,0 +1,56 @@
+# Contributing
+
+[简体中文](CONTRIBUTING.md) | **English**
+
+Thank you for improving `dsh-oidc`. Authentication and credential code has a higher review bar than ordinary UI changes.
+
+## Before starting
+
+- Use a public issue for non-sensitive design/bug discussion.
+- Use the [private security-reporting entry point](https://github.com/freedomkk-qfeng/dsh-oidc/security/advisories/new) for vulnerabilities or secrets.
+- For a protocol or trust-boundary change, open a design issue and add an ADR under `docs/decisions/` before implementation.
+- Do not include production endpoints, identifiers, logs, tokens, personal data, logos, or screenshots without explicit publication approval.
+
+## Development
+
+Requirements: Node.js 22+ and npm.
+
+```bash
+npm ci
+npm run check
+```
+
+Use placeholder domains under `example.com`, `example.edu`, or `example.net`. Unit tests must use generated keys and synthetic subjects.
+
+## Pull request requirements
+
+Every PR must:
+
+- explain the user/security impact and affected boundary;
+- include tests for success and negative/failure behavior;
+- update schemas, OpenAPI, prose, examples, and changelog when a contract changes;
+- preserve fixed callback/Key Binding paths unless introducing a versioned migration;
+- keep profiles declarative and reject unknown executable-relevant fields;
+- use official DSH/community capabilities where appropriate rather than introducing a parallel runtime;
+- pass `npm run check` from a clean install;
+- declare any new dependency, license, install script, and why it is necessary.
+
+Changes to OIDC, Key Binding, credentials, Profile validation, the native account contract, build/release workflows, or dependency pins require independent technical review, CI, and focused regression evidence, with explicit acceptance by the current maintainer. After a second maintainer joins, these changes should also receive independent human approval.
+
+## Code style
+
+- Native ESM, Node 22 baseline.
+- Small explicit modules and fail-closed validation.
+- Public error codes are stable machine facts; messages must not contain secrets.
+- Network operations need timeouts and bounded response bodies.
+- Avoid logging response bodies, headers, tokens, keys, or full profiles.
+- Prefer official DSH services and exports; document every compatibility seam.
+
+## Commit and release hygiene
+
+- Keep commits reviewable and signed where project policy supports it.
+- Do not commit generated credentials, `.env`, archives, or session logs.
+- `lib/` is generated by `npm run build`; review the source and tarball, not only minified output.
+- Prefer protected tags and the approved Trusted Publishing workflow. Until that path is configured, the initial maintainer may publish the frozen, verified tarball with the npm CLI and browser 2FA, but must not claim provenance. Record provenance only after npm actually creates an attestation.
+
+By participating, contributors agree to follow [`CODE_OF_CONDUCT.en.md`](CODE_OF_CONDUCT.en.md) and certify that they have the right to submit their contribution under the MIT license.

package/CONTRIBUTING.md

@@ -0,0 +1,56 @@
+# 贡献指南
+
+**简体中文** | [English](CONTRIBUTING.en.md)
+
+感谢你改进 `dsh-oidc`。认证和凭据代码的审查门槛高于普通 UI 变更。
+
+## 开始之前
+
+- 非敏感设计或缺陷讨论请使用公开 Issue。
+- 漏洞或秘密信息请使用[私有安全报告入口](https://github.com/freedomkk-qfeng/dsh-oidc/security/advisories/new)。
+- 修改协议或信任边界前，请先创建设计 Issue，并在 `docs/decisions/` 下新增 ADR。
+- 未经明确公开授权，不得提交生产 endpoint、标识符、日志、Token、个人数据、Logo 或截图。
+
+## 开发
+
+要求：Node.js 22+ 和 npm。
+
+```bash
+npm ci
+npm run check
+```
+
+占位域名使用 `example.com`、`example.edu` 或 `example.net`。单元测试必须使用生成密钥和虚构 subject。
+
+## Pull Request 要求
+
+每个 PR 必须：
+
+- 说明对用户和安全的影响，以及涉及的边界；
+- 覆盖成功和反向/失败行为测试；
+- 契约变化时同步更新 Schema、OpenAPI、规范正文、示例和 Changelog；
+- 除非提供版本化迁移方案，否则保持 callback/Key Binding 固定路径不变；
+- 保持 Profile 声明式，并拒绝与可执行行为相关的未知字段；
+- 适用时优先使用 DSH 官方或社区能力，不引入平行运行时；
+- 在干净安装中通过 `npm run check`；
+- 声明所有新增依赖、许可证、安装脚本和引入理由。
+
+修改 OIDC、Key Binding、凭据、Profile 校验、native 账号契约、构建/发布流程或依赖锁定，必须提供独立技术复核、CI 和专项回归证据，并由当前维护者明确接受结论。项目增加第二位维护者后，此类变更还应取得独立人工批准。
+
+## 代码风格
+
+- 原生 ESM，Node 22 基线。
+- 模块保持小而明确，校验采用失败关闭。
+- 公共错误码是稳定机器事实；消息不得包含秘密。
+- 网络操作必须有超时和响应大小上限。
+- 避免记录响应 body、header、Token、Key 或完整 Profile。
+- 优先使用 DSH 官方服务和 export；记录每个兼容扩展点。
+
+## Commit 与发布规范
+
+- Commit 应便于审查；项目策略支持时使用签名。
+- 不得提交生成的凭据、`.env`、归档或 session 日志。
+- `lib/` 由 `npm run build` 生成；审查源码和 tarball，而不只是压缩产物。
+- 优先通过受保护 tag 和批准的 Trusted Publishing 工作流发布。该流程尚未配置时，初始维护者可以用 npm CLI 和浏览器 2FA 发布已冻结并核验的 tarball，但不得声称 provenance；只有 npm 实际生成 attestation 后才能记录 provenance。
+
+参与贡献即表示同意遵守[行为准则](CODE_OF_CONDUCT.md)，并确认你有权按 MIT 许可证提交相关贡献。

package/GOVERNANCE.en.md

@@ -0,0 +1,41 @@
+# Governance
+
+[简体中文](GOVERNANCE.md) | **English**
+
+## Project ownership
+
+`dsh-oidc` is initiated and hosted by [@freedomkk-qfeng](https://github.com/freedomkk-qfeng). The project remains institution-neutral: an institution's names, trademarks, service addresses, and Client IDs belong only in authorized deployment configuration and must not become protocol defaults.
+
+## Roles
+
+- **Maintainers** merge ordinary changes, triage issues, and manage compatibility.
+- **Security maintainers** review authentication, authorization, credential, build, and release changes and handle private reports.
+- **Release managers** control tags, npm publishing, release evidence, provenance when available, and rollback.
+
+The current roster is in [`MAINTAINERS.en.md`](MAINTAINERS.en.md). One maintainer currently holds all three roles and there is no backup. Release/security-recovery backups, role separation, and a second human reviewer are future governance goals. Current releases must accurately record independent technical review, CI/regression evidence, known limitations, and the maintainer's decision.
+
+## Decision process
+
+- Ordinary implementation decisions use pull-request review.
+- Public contract, trust-boundary, dependency strategy, or governance changes require an Architecture Decision Record in `docs/decisions/`.
+- Backward-incompatible changes require migration documentation and the versioning process in `docs/compatibility.en.md`.
+- Maintainers seek rough consensus; unresolved security and interoperability concerns block release until addressed or explicitly accepted in a documented decision.
+
+## Review and merge
+
+- The current maintainer approves ordinary documentation, test, and UI changes through a reviewable pull-request record.
+- OIDC, Key Binding, Profile validation, secrets, native boundaries, workflows, dependencies, and releases require independent technical review plus CI and focused regression evidence. The maintainer explicitly accepts findings and exceptions in the pull request or release record.
+- There is no second human maintainer today, so the project must not claim two-person approval. Add independent human approval for security-sensitive changes after the maintainer roster expands.
+- CI must be enabled on the public remote. Required human review and branch protection should be enabled when repository permissions and the maintainer roster support them; a direct merge during the initial single-maintainer phase must retain check results and decision rationale.
+
+## Releases
+
+- During the initial phase, the current maintainer also acts as release manager. Tags and npm packages are created only after `docs/release-checklist.en.md` is completed and its evidence and exceptions are recorded.
+- npm Trusted Publishing/OIDC with provenance is the preferred target process. Until a Trusted Publisher is configured, the first stable release may use the npm CLI and maintainer-confirmed browser 2FA to publish the verified frozen tarball. That path must not claim provenance or write a long-lived token into the repository, logs, or deliverables.
+- After Trusted Publishing is configured, releases should move to protected tags and the approved workflow, and provenance is recorded only when an npm attestation actually exists.
+- A release record includes checksums, compatibility matrix, changelog, known limitations, and rollback guidance.
+- A compromised or unsafe release is deprecated promptly; secrets are rotated and users are notified through the security policy.
+
+## Branding and neutrality
+
+The project may document ECNU as a reference implementation while keeping the protocol institution-neutral. Merging another organization's example does not imply endorsement. Trademarks and logos require their owners' permission and are not granted by the MIT code license.

package/GOVERNANCE.md

@@ -0,0 +1,41 @@
+# 治理规则
+
+**简体中文** | [English](GOVERNANCE.en.md)
+
+## 项目所有权
+
+`dsh-oidc` 由 [@freedomkk-qfeng](https://github.com/freedomkk-qfeng) 发起并托管。项目保持机构中立；具体机构的名称、商标、服务地址和 Client ID 只能出现在获得授权的部署配置中，不能成为公共协议的默认值。
+
+## 角色
+
+- **维护者**：合并普通变更、处理 Issue 并管理兼容性。
+- **安全维护者**：审查认证、授权、凭据、构建和发布变更，并处理私有报告。
+- **发布经理**：控制 tag、npm 发布、发布证据、可用时的 provenance 和回滚。
+
+维护者名单见 [`MAINTAINERS.md`](MAINTAINERS.md)。项目当前由一名维护者兼任上述角色，尚无替补。发布与安全恢复替补、多维护者权限分离和第二位人工审查是后续治理目标；当前发布必须如实记录独立技术复核、CI/回归证据、已知限制和维护者决定。
+
+## 决策流程
+
+- 普通实现决策通过 Pull Request 审查。
+- 公共契约、信任边界、依赖策略或治理变更，需要在 `docs/decisions/` 中记录 ADR。
+- 不向后兼容的变更必须提供迁移文档，并遵循[兼容性与发布策略](docs/compatibility.md)。
+- 维护者寻求大致共识；未解决的安全和互操作问题会阻止发布，除非通过书面决策明确接受。
+
+## 审查与合并
+
+- 普通文档、测试和 UI 变更由当前维护者审批并保持可审查的 Pull Request 记录。
+- OIDC、Key Binding、Profile 校验、秘密、native 边界、工作流、依赖或发布变更必须形成独立技术复核和 CI/专项回归证据，由维护者在 Pull Request 或发布记录中明确接受结论和例外。
+- 当前没有第二位人工维护者，不得声称完成了两人审批。维护者名单扩充后，安全敏感变更应增加独立人工批准。
+- 公开远程仓库必须启用 CI。分支保护和强制人工审查应在仓库权限与维护者配置具备条件后启用；初期单一维护者直接合并时必须留存检查结果和决定依据。
+
+## 发布
+
+- 初期由当前维护者兼任发布经理；只有在完成[公开发布检查表](docs/release-checklist.md)并记录证据和例外后，才能创建 tag 或发布 npm 包。
+- npm Trusted Publishing/OIDC 和 provenance 是优先的目标流程。尚未配置 Trusted Publisher 时，首次稳定版可以由维护者使用 npm CLI 和浏览器 2FA 发布经过校验的冻结 tarball；该路径不得声称具有 provenance，也不得把长期 Token 写入仓库、日志或交付物。
+- Trusted Publisher 配置完成后，发布应切换到受保护 tag 和批准的工作流，并以实际 npm attestation 为准记录 provenance。
+- 发布记录包含 checksum、兼容性矩阵、Changelog、已知限制和回滚说明。
+- 发现发布版本已被攻陷或不安全时，应迅速弃用、轮换秘密，并按安全政策通知用户。
+
+## 品牌与中立性
+
+项目可以记录 ECNU 参考实现，但协议必须保持机构中立。合并其他机构示例不代表背书。商标和 Logo 的使用需要权利人许可，MIT 代码许可证不授予商标权。

package/MAINTAINERS.en.md

@@ -0,0 +1,13 @@
+# Maintainers
+
+[简体中文](MAINTAINERS.md) | **English**
+
+| Role | Primary | Backup | Approval status |
+| --- | --- | --- | --- |
+| Project maintainer | [@freedomkk-qfeng](https://github.com/freedomkk-qfeng) | None yet | Initial single-maintainer phase |
+| Security maintainer | [@freedomkk-qfeng](https://github.com/freedomkk-qfeng) | None yet | Initial single-maintainer phase |
+| Release manager | [@freedomkk-qfeng](https://github.com/freedomkk-qfeng) | None yet | Initial single-maintainer phase |
+
+The project is currently in its initial single-maintainer phase. It has no backup and does not claim a second human approval. The maintainer explicitly decides each release after recording independent technical review, CI/regression evidence, known limitations, and recovery steps. Adding a backup capable of handling private security reports and release recovery is a future governance goal; the roster and repository permissions must be updated when one is added.
+
+Role responsibilities and review thresholds are defined in [`GOVERNANCE.en.md`](GOVERNANCE.en.md).

package/MAINTAINERS.md

@@ -0,0 +1,13 @@
+# 维护者
+
+**简体中文** | [English](MAINTAINERS.en.md)
+
+| 角色 | 主要负责人 | 替补 | 批准状态 |
+| --- | --- | --- | --- |
+| 项目维护者 | [@freedomkk-qfeng](https://github.com/freedomkk-qfeng) | 暂无 | 初期单一维护者 |
+| 安全维护者 | [@freedomkk-qfeng](https://github.com/freedomkk-qfeng) | 暂无 | 初期单一维护者 |
+| 发布经理 | [@freedomkk-qfeng](https://github.com/freedomkk-qfeng) | 暂无 | 初期单一维护者 |
+
+项目当前处于初期单一维护者阶段，尚无替补，不声称已经完成第二位人工审批。发布由维护者在记录独立技术复核、CI/回归证据、已知限制和恢复步骤后明确决定。增加能够处理私有安全报告和发布恢复的替补，是后续治理目标；新增后应及时更新本表和仓库权限。
+
+角色职责和审查门槛见[治理规则](GOVERNANCE.md)。

package/README.en.md

@@ -1,6 +1,6 @@
 # dsh-oidc
 
-> npm package: `@eduwork/dsh-oidc@0.1.0-alpha.11`. The previous unscoped package remains available during migration. See [migration and data compatibility](docs/EDUWORK-MIGRATION.en.md).
+> `0.2.0`, based on official DSH `0.1.5-rc.1`: identity login, managed keys, model discovery and logout remain public. Quota requests, normalization and UI belong to a separately installed institution extension. No public quota or heartbeat requests. See [account extensions](docs/account-extensions.en.md) and [server specification](docs/server-integration-contract.en.md). Consult the npm registry for publication status.
 
 [简体中文](README.md) | **English**
 
@@ -10,12 +10,12 @@ Standards-based enterprise identity and model integration for [DeepSeek Harness]
 
 1. OpenID Connect Authorization Code flow with PKCE for a public client;
 2. a fixed enterprise **Key Binding** protocol that exchanges the authenticated OIDC access token for a revocable model runtime credential;
-3. an audited local OpenAI-compatible DSH Provider adapter; and
-4. bounded product branding plus a shared account and enterprise-model settings UI.
+3. a local OpenAI-compatible Provider with optional automatic model discovery; and
+4. safe account refresh and sign-out, with optional institution account extensions.
 
-The plugin is Web-first and has no Wails dependency. A desktop product can select the native account backend without changing the profile, Provider routes, UI contract, or Key Binding semantics.
+Shared account UI and optional bounded branding accompany these capabilities. Identity-only integration may omit resource APIs, and personal model providers remain available.
 
-> **Status: alpha.** The code is usable for integration testing against DSH `0.1.2-alpha.2` through both the official npm Runtime and the locked source release-pack Runtime. The Enterprise Profile and Key Binding contracts are `v1alpha1`/`v1`. The Web backend is local single-user only; security review and compatibility tests remain required before production use.
+The plugin targets a single-user local client. Web is for local validation; `backend: desktop` uses a temporary loopback callback and the host browser service without a persistent WebServer. `backend: native` remains for the legacy account bridge. No backend is tied to a particular shell; see [desktop host integration](docs/desktop-host.en.md).
 
 Integrating your own organization? Read the **[server API specification](docs/server-integration-contract.en.md)** first, then follow the **[getting-started guide](docs/getting-started.en.md)**. The first defines, with requests, responses, fields, and errors, the OIDC + PKCE, Key Binding, and model-gateway capabilities one institutional service must jointly deliver; the second covers configuration, installation, acceptance, and troubleshooting.
 
@@ -48,17 +48,17 @@ The Enterprise Profile is data only. It cannot name JavaScript modules, inject C
 
 ## What is included
 
-- fixed loopback callback `http://127.0.0.1:<DSH-port>/oauth/callback`;
+- loopback callback `http://127.0.0.1:<actual-port>/oauth/callback`: the WebServer port for Web, a temporary random port by default for desktop;
 - OIDC Discovery, PKCE S256, state, nonce, RS256 ID Token validation, UserInfo subject binding, refresh, and optional revocation;
 - `userinfo.name` for display, falling back only to the required `userinfo.sub`;
 - fixed `worker-user-center-v1` endpoints for bootstrap, provision, resolve, and renew;
 - DSH Credential Provider storage for OIDC session material and the runtime API key;
 - declarative provider/model catalog and bounded brand tokens;
-- one capability-aware enterprise-service settings section shared by Web and native hosts through DSH's official `settings.section` extension point;
+- shared official model-settings, onboarding, sidebar-account and general-settings slots, with capability-aware operations across local Web and both desktop shells;
 - a native backend adapter boundary for desktop products;
 - a stable `enterpriseTransforms` service for capabilities such as a text-model image fallback without forking the Provider route.
 
-Not included: an OIDC Provider, a Key Binding server, multi-user session storage, an organization directory, quota UI, a desktop shell, or remote executable plugins.
+Not included: an OIDC Provider, a Key Binding server, multi-user session storage, an organization directory, a desktop shell, or remote executable plugins.
 
 ## Branding scope
 
@@ -69,25 +69,25 @@ Not included: an OIDC Provider, a Key Binding server, multi-user session storage
 - a six-digit hexadecimal `primaryColor`;
 - `loginTitle`, `loginDescription`, and an HTTPS `supportURL`.
 
-These values affect the document title, sidebar brand, conversation hero mark, login/confirmation surfaces, and a bounded set of DSH theme tokens. They cannot inject arbitrary CSS, SVG, scripts, or components, and they do not replace a desktop shell, updater, quota UI, or institution-specific business pages. See the [Enterprise Profile specification](docs/enterprise-profile.en.md#branding) for limits and security rules.
+These values affect the document title, sidebar brand, conversation hero mark, login/confirmation surfaces, and a bounded set of DSH theme tokens. They cannot inject arbitrary CSS, SVG, scripts, or components, and they do not replace a desktop shell, updater, or institution-specific business pages. See the [Enterprise Profile specification](docs/enterprise-profile.en.md#branding) for limits and security rules.
 
 ## Requirements
 
 - Node.js 22 or newer;
-- DeepSeek Harness `0.1.2-alpha.2` packages listed as peers;
-- an OIDC Public Client without a Client Secret that registers `http://127.0.0.1:3080/oauth/callback` exactly;
+- one coherent DeepSeek Harness `0.1.5-rc.1` peer set for this source candidate; historical stable `0.1.0` targets DSH `0.1.2-rc.1`;
+- an OIDC Public Client without a Client Secret: new desktops use `http://127.0.0.1:<actual-port>/oauth/callback`, while local Web validation registers its actual fixed port;
 - Discovery metadata with PKCE S256, RS256 ID Tokens, and `userinfo_endpoint`;
-- one institutional integration service implementing the complete [server contract](docs/server-integration-contract.en.md), including Key Binding and the model gateway;
+- an OIDC service for identity-only mode; managed models additionally require the Key Binding and model gateway in the [server contract](docs/server-integration-contract.en.md);
 - a DSH Credential Provider appropriate for the deployment.
 
 The current Web backend is intentionally limited to a trusted, single-user DSH process bound to `127.0.0.1`. It is not a shared public-Web session solution. See [Security model](docs/security-model.en.md).
 
 ## Install
 
-Install the reviewed, exact version from npm:
+Install the exact npm version in a coherent DSH `0.1.5-rc.1` host. During release preparation, if the version is not yet in the registry, use the source instructions below rather than installing an older version or suppressing peer conflicts:
 
 ```bash
-dsh plugin --profile web add @eduwork/dsh-oidc@0.1.0-alpha.11
+dsh plugin --profile web add @eduwork/dsh-oidc@0.2.0
 ```
 
 For auditing, development, or testing unpublished changes, install from a local checkout instead:
@@ -100,7 +100,7 @@ npm run check
 dsh plugin --profile web add .
 ```
 
-The local-path form links the checkout into the DSH `web` Profile, so keep the source directory in place. Team deployments should prefer a reviewed, exact npm version; use `@eduwork/dsh-oidc@alpha` only when intentionally following alpha updates.
+The local-path form links the checkout into the DSH `web` Profile, so keep the source directory in place. Team deployments should pin a reviewed, exact npm version and must not mix another DSH prerelease line into the same profile.
 
 Advanced products may instead add it explicitly to their own DSH bundle patch:
 
@@ -109,10 +109,10 @@ Advanced products may instead add it explicitly to their own DSH bundle patch:
     - id: enterprise-oidc
       name: '@eduwork/dsh-oidc'
       config:
-        profilePathEnv: DSH_OIDC_ENTERPRISE_PROFILE
+        profilePathEnv: EDUWORK_OIDC_PROFILE
 ```
 
-Set `DSH_OIDC_ENTERPRISE_PROFILE` to a trusted local JSON file. Start from [`examples/enterprise-profile.example.json`](examples/enterprise-profile.example.json) and validate it with [`schema/enterprise-profile.v1alpha1.schema.json`](schema/enterprise-profile.v1alpha1.schema.json).
+Set `EDUWORK_OIDC_PROFILE` to a trusted local JSON file. Start from [`examples/enterprise-profile.example.json`](examples/enterprise-profile.example.json) and validate it with [`schema/enterprise-profile.v1alpha1.schema.json`](schema/enterprise-profile.v1alpha1.schema.json).
 
 Start DSH on the fixed IPv4 loopback host. The public OIDC client must register exactly:
 
@@ -120,7 +120,7 @@ Start DSH on the fixed IPv4 loopback host. The public OIDC client must register
 http://127.0.0.1:3080/oauth/callback
 ```
 
-The callback host and path are not configurable. The port follows the actual DSH WebServer port; if the operator changes `3080`, the OIDC registration must use the same port.
+This installation example uses local Web validation. Its port follows the actual DSH WebServer port; if the operator changes `3080`, registration must match. New desktops use a temporary listener and normally request an available port; see [desktop integration](docs/desktop-host.en.md). The loopback host and callback path stay fixed.
 
 ## Configuration surfaces
 
@@ -129,7 +129,7 @@ The callback host and path are not configurable. The port follows the actual DSH
 | `profile` | One inline Enterprise Profile object. |
 | `profiles` | An array of inline Enterprise Profiles. Provider IDs must also be unique. |
 | `profilePathEnv` | Name of an environment variable containing the trusted JSON profile path. |
-| `backend` | `web` (default) or `native`. Native delegates account lifecycle to the host's `enterpriseAccounts` service. |
+| `backend` | `web` (default) for local validation, `desktop` for the shared temporary loopback/native-browser implementation, or legacy `native` for a host-provided `enterpriseAccounts` service. |
 | `uiMode` | `standard` (shared model settings plus account/onboarding/branding), `models-only` (shared model settings only), or `external` (no plugin UI). |
 | `web.returnPath` | Same-origin absolute path after callback; defaults to `/`. |
 | `allowEmptyProfiles` | Allows the plugin service to start with no profile, mainly for composition tests. |
@@ -138,7 +138,7 @@ See [Enterprise Profile](docs/enterprise-profile.en.md) for every data field and
 
 ## Protocol summary
 
-OIDC remains standard OIDC. The plugin does not support custom “userinfo field mapping”: `name` is the standard display claim and `sub` is the guaranteed stable fallback. OIDC, Key Binding, and the model gateway form one required institutional server contract; they are not optional alternatives. See the [complete server integration contract](docs/server-integration-contract.en.md).
+OIDC remains standard OIDC. The plugin does not support custom “userinfo field mapping”: `name` is the standard display claim and `sub` is the guaranteed stable fallback. Identity-only mode requires OIDC and omits both `keyBinding` and `provider`. Managed enterprise keys/models require both fields and the Key Binding/model-gateway services. See the [complete server integration contract](docs/server-integration-contract.en.md).
 
 Given `keyBinding.baseURL = https://ai.example.edu/api/worker/v1`, the only valid operations are:
 
@@ -149,7 +149,7 @@ Given `keyBinding.baseURL = https://ai.example.edu/api/worker/v1`, the only vali
 
 The profile cannot change these paths or their fields. [`protocol/openapi.yaml`](protocol/openapi.yaml) is the machine-readable contract; [Key Binding protocol](docs/key-binding-protocol.en.md) defines normative behavior, authorization, idempotency, logging, and lifecycle semantics.
 
-Provider ID determines the runtime route and, by default, derives the local credential reference (for example, `example-ai` becomes `EXAMPLE_AI_API_KEY`). Production and test deployments that reuse one Provider ID may explicitly isolate their local secret entries with `keyBinding.credentialRef`; this does not change the server API.
+Provider ID determines the runtime route; the default enterprise credential reference is `EDUWORK_API_KEY`. Legacy automatic names are migrated compatibly, while independently managed references remain configurable through `keyBinding.credentialRef`. Verified identity, resource binding and a key fingerprint enforce ownership without changing the server API.
 
 ## Development
 
@@ -158,10 +158,12 @@ npm ci
 npm run check
 ```
 
-`npm run check` rebuilds both plugin faces, runs unit/security-contract tests, validates examples and OpenAPI structure, scans publishable sources for common secrets, personal paths, non-example addresses, and ECNU service endpoints, and inspects the npm tarball.
+Development dependencies and the lockfile pin DSH `0.1.5-rc.1`, without referring to a developer’s installed desktop. `npm run check` verifies the dependency lock and selected DSH Host, Client, Provider, WebServer, credentials, and Typert contracts; rebuilds both plugin faces; runs unit/security-contract tests; validates examples and OpenAPI structure; scans publishable sources for common secrets, personal paths, non-example addresses, and ECNU service endpoints; and inspects the npm tarball.
 
 The repository intentionally keeps Host code as native ESM under `src/host`; `scripts/build-host.mjs` copies it to `lib`. The DSH browser client is bundled as the loader-compatible `lib/client.js`.
 
+Plugin `0.2.0` does not track the EduWork product version. Distribution assembly uses an exact npm version and integrity; source paths are for development. This version does not replace earlier frozen artifacts. See [development and release preparation](docs/development.en.md) for clean installation and validation boundaries.
+
 ## Documentation
 
 - [Architecture and boundaries](docs/architecture.en.md)