dsh-github-copilot 0.4.0-alpha.55 → 0.4.0-alpha.56

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -1,5 +1,9 @@
1
1
  # Changelog
2
2
 
3
+ ## 0.4.0-alpha.56 (prepared)
4
+
5
+ - Pin `undici` to 6.28.1 to resolve the observed 6.29.0 installation failure in the configured package mirror (#212). Keep the lockfile registry-neutral and preserve the quota-only TLS dispatcher; this does not establish full Desktop installation or activation.
6
+
3
7
  ## 0.4.0-alpha.55 (prepared)
4
8
 
5
9
  - Use a quota-only, reusable TLS-verified dispatcher with Node default and system CA roots for the GitHub Copilot usage endpoint (#209). This removes reliance on launcher inheritance of `NODE_USE_SYSTEM_CA` for quota requests, without changing Core, sign-in, model/search transport or global trust.
package/README.md CHANGED
@@ -96,7 +96,7 @@ The Host reads GitHub's internal quota endpoint using the existing canonical OAu
96
96
 
97
97
  ## Install and sign in
98
98
 
99
- The commands below target the package version `0.4.0-alpha.55`. Versioned URLs describe the intended release artifacts, not proof that publication or local activation has completed; use them only once that Release and its checksums are available. Install into the profile you use (replace `web` when targeting another profile):
99
+ The commands below target the package version `0.4.0-alpha.56`. Versioned URLs describe the intended release artifacts, not proof that publication or local activation has completed; use them only once that Release and its checksums are available. Install into the profile you use (replace `web` when targeting another profile):
100
100
 
101
101
  Before installing/updating, unpack the **checksum-verified** archive into a temporary directory and run its read-only composition preflight (replace all paths with absolute paths for the intended profile):
102
102
 
@@ -109,10 +109,10 @@ Include any launcher patch files with repeated `--patch /absolute/file` argument
109
109
  For a standalone named profile only, the supported CLI command is:
110
110
 
111
111
  ```sh
112
- dsh plugin --profile web add https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.0-alpha.55/dsh-github-copilot-0.4.0-alpha.55.tgz
112
+ dsh plugin --profile web add https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.0-alpha.56/dsh-github-copilot-0.4.0-alpha.56.tgz
113
113
  ```
114
114
 
115
- For Desktop profiles, use Desktop's native package manager with `dsh-github-copilot@0.4.0-alpha.55` after the same preflight and only when registry access is permitted. Desktop reserves its `desktop` profile from CLI management. If registry access is blocked or unavailable, stop; the documented [controlled offline CLI procedure](./docs/npm-distribution.md#controlled-offline-cli-maintenance-for-standalone-profiles) is not a Desktop workaround.
115
+ For Desktop profiles, use Desktop's native package manager with `dsh-github-copilot@0.4.0-alpha.56` after the same preflight and only when registry access is permitted. Desktop reserves its `desktop` profile from CLI management. If registry access is blocked or unavailable, stop; the documented [controlled offline CLI procedure](./docs/npm-distribution.md#controlled-offline-cli-maintenance-for-standalone-profiles) is not a Desktop workaround.
116
116
 
117
117
  Then open the Models UI listed above, find **GitHub Copilot**, select **Sign in**, and complete the GitHub device-code flow. Plugin installation changes the selected profile; activation follows that profile's normal reload/restart policy.
118
118
 
@@ -153,7 +153,7 @@ Agents should treat the browser authorization as a human handoff, not as a token
153
153
  5. Confirm **Signed in** and inspect the automatic discovery result before asking the user to choose a model. Already-signed-in Models opening ensures missing/stale metadata automatically; fresh ready cache makes no request. Use visible **Retry** for errors or **Manage → Refresh models** for an intentional forced update, not routine setup. Status alone does not discover, and login, metadata and successful model calls remain separate evidence.
154
154
  6. Use **Sign out** only when the user explicitly asks to disconnect the account. It deletes the Copilot credential record but preserves route settings.
155
155
 
156
- GitHub Releases and npm are the default distribution channels for each new version, using the same verified tarball. Pin the version and verify the evidence for the channel used: Release `SHA256SUMS`, and npm `dist.integrity` when installing from npm. Install into Desktop profiles only through Desktop's native package manager; the reserved `desktop` profile is not managed by the DSH CLI. After npm publication is verified, the native manager accepts `dsh-github-copilot@0.4.0-alpha.55`, not a URL or file. Controlled offline CLI maintenance is documented for standalone named profiles only, never Desktop-managed profiles. Follow the mandatory search-composition preflight, backup, single-writer and post-install checks; do not bypass a corporate registry ban, disable TLS verification or restart without separate approval. See [distribution and publication requirements](./docs/npm-distribution.md).
156
+ GitHub Releases and npm are the default distribution channels for each new version, using the same verified tarball. Pin the version and verify the evidence for the channel used: Release `SHA256SUMS`, and npm `dist.integrity` when installing from npm. Install into Desktop profiles only through Desktop's native package manager; the reserved `desktop` profile is not managed by the DSH CLI. After npm publication is verified, the native manager accepts `dsh-github-copilot@0.4.0-alpha.56`, not a URL or file. Controlled offline CLI maintenance is documented for standalone named profiles only, never Desktop-managed profiles. Follow the mandatory search-composition preflight, backup, single-writer and post-install checks; do not bypass a corporate registry ban, disable TLS verification or restart without separate approval. See [distribution and publication requirements](./docs/npm-distribution.md).
157
157
 
158
158
  **Desktop package-update and Web-lifecycle boundaries:** the native manager's `restart-required` result for an in-place installed-package upgrade is authoritative and distinct from plugin-bundle removal/re-add behavior. Any plugin upgrade involving service recomposition (`cordis.patch.yml`, such as the isolated routed web search layer) cannot rebind active consumers via hot reload; Desktop must be fully exited and cold-restarted to take effect. A pinned public Loader characterization records that, with the exact bundle IDs and an active provider, staged first-add can leave global `ctx.web` and an active consumer unavailable even after the routed row is enabled. A separate complete cold-loaded Web-routing composition works initially but loses global `ctx.web` and its consumer on removal and remains unavailable after re-add/reconciliation. An earlier temporary harness used alias IDs and no active provider, so its successful final add was not equivalent to the exact bundle fixture. These are synthetic Loader observations, not native Desktop manager coverage or proof of restart recovery. Do not use bundle removal/re-add as a hot-upgrade workaround; follow the manager's upgrade result and separately authorized restart requirements. See [the rc.2 lifecycle characterization and bounded public-API finding](https://github.com/cloga/dsh-github-copilot/blob/main/docs/web-lifecycle-rc2.md).
159
159
 
@@ -424,8 +424,8 @@ Report the published Release URL, version, tag/commit and verified asset SHA-256
424
424
  `package.json` declares public npm distribution. A release tag must equal `v${package.json.version}`. Versions use standard SemVer prerelease labels (`alpha`, `beta`, or `rc`), each with its matching npm dist-tag; only stable versions use `latest`. The Release workflow performs the frozen install and complete verification gate, packs once (or recovers the original archive on retry), verifies `SHA256SUMS`, publishes the immutable GitHub Release and then publishes those same bytes to npm through OIDC. Either channel failing means delivery is incomplete. First package creation needs an authorized maintainer; staging requires an existing package and is not a first-package bootstrap. Historical releases are not republished.
425
425
 
426
426
  ```sh
427
- curl -LO https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.0-alpha.55/dsh-github-copilot-0.4.0-alpha.55.tgz
428
- curl -LO https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.0-alpha.55/SHA256SUMS
427
+ curl -LO https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.0-alpha.56/dsh-github-copilot-0.4.0-alpha.56.tgz
428
+ curl -LO https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.0-alpha.56/SHA256SUMS
429
429
  sha256sum --check SHA256SUMS
430
430
  ```
431
431
 
@@ -433,7 +433,7 @@ PowerShell can verify the same two downloaded files with:
433
433
 
434
434
  ```powershell
435
435
  $expected = (Get-Content .\SHA256SUMS).Split()[0]
436
- $actual = (Get-FileHash .\dsh-github-copilot-0.4.0-alpha.55.tgz -Algorithm SHA256).Hash.ToLowerInvariant()
436
+ $actual = (Get-FileHash .\dsh-github-copilot-0.4.0-alpha.56.tgz -Algorithm SHA256).Hash.ToLowerInvariant()
437
437
  if ($actual -cne $expected) { throw 'Release checksum mismatch' }
438
438
  ```
439
439
 
package/README.zh.md CHANGED
@@ -20,7 +20,7 @@
20
20
 
21
21
  截图来自当前构建 Client 的隔离浏览器 fixture,使用合成 Provider。它只证明已发布配置界面的形态,不证明真实凭据、账号权限、搜索成功或当前 Desktop 已加载。
22
22
 
23
- > 当前文档与安装命令对应版本 `0.4.0-alpha.55`。源码、发布制品、已安装版本和实际加载运行时需分别确认;本地升级和中断会话的重启仍需用户批准。
23
+ > 当前文档与安装命令对应版本 `0.4.0-alpha.56`。源码、发布制品、已安装版本和实际加载运行时需分别确认;本地升级和中断会话的重启仍需用户批准。
24
24
 
25
25
  Web search 路由现在优先显示在插件详情页;宿主不支持详情页插槽时才回退到 **设置 → 模型**或独立 Web search section。搜索子 Fiber 仍独立等待 Remote,不影响账号控件和既有搜索安全检查。
26
26
 
@@ -111,10 +111,10 @@ node package/scripts/check-search-composition.mjs --profile-dir /absolute/profil
111
111
  仅对独立的具名 profile,获准且网络可用时,可通过受支持的 CLI 命令安装:
112
112
 
113
113
  ```sh
114
- dsh plugin --profile web add https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.0-alpha.55/dsh-github-copilot-0.4.0-alpha.55.tgz
114
+ dsh plugin --profile web add https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.0-alpha.56/dsh-github-copilot-0.4.0-alpha.56.tgz
115
115
  ```
116
116
 
117
- Desktop profile 请在完成同样的预检后,使用 Desktop 原生包管理器安装 `dsh-github-copilot@0.4.0-alpha.55`。Desktop 保留 `desktop` profile,CLI 不负责管理。若 registry 被公司封禁或不可用,不要更换网络绕行或使用离线 CLI;请停止。[受控离线 CLI 流程](./docs/npm-distribution.md#controlled-offline-cli-maintenance-for-standalone-profiles)仅适用于独立具名 profile,不适用于 Desktop。
117
+ Desktop profile 请在完成同样的预检后,使用 Desktop 原生包管理器安装 `dsh-github-copilot@0.4.0-alpha.56`。Desktop 保留 `desktop` profile,CLI 不负责管理。若 registry 被公司封禁或不可用,不要更换网络绕行或使用离线 CLI;请停止。[受控离线 CLI 流程](./docs/npm-distribution.md#controlled-offline-cli-maintenance-for-standalone-profiles)仅适用于独立具名 profile,不适用于 Desktop。
118
118
 
119
119
  随后打开上表对应的 Models UI,找到 **GitHub Copilot**,点击 **Sign in** 并完成 GitHub device-code 流程。安装会修改指定 profile;是否立即激活取决于该 profile 的常规 reload/restart 策略。
120
120
 
@@ -155,7 +155,7 @@ Agent 应把浏览器授权视为需要用户完成的 handoff,而不是自行
155
155
  5. 确认 **Signed in** 并检查自动发现结果,再请用户选择模型。已登录时打开 Models 会自动确保缺失/过期元数据,新鲜 ready 缓存不发请求。错误可使用 **Retry**,有意强制更新时使用 **Manage → Refresh models**,不作为常规设置步骤。状态读取本身不发现;登录、元数据与真实调用成功是独立证据。
156
156
  6. 只有用户明确要求断开账号时才使用 **Sign out**;它会删除 Copilot credential record,但保留 route settings。
157
157
 
158
- 每个新版本默认同时分发到 GitHub Releases 和 npm,两个渠道使用同一份已验证 tarball。应固定版本并核对所用渠道的证据:Release 的 `SHA256SUMS`;从 npm 安装时另核对 `dist.integrity`。Desktop profile 只能通过原生 Desktop 包管理器安装;获准且 registry 可用时输入 `dsh-github-copilot@0.4.0-alpha.55`,不是 URL 或本地文件。Desktop 保留 `desktop` profile,不能通过 DSH CLI 管理。受控离线 CLI 维护仅适用于独立具名 profile,不得作为 Desktop 安装绕行方案。[双渠道发布与 OIDC 要求](./docs/npm-distribution.md)保持不变。
158
+ 每个新版本默认同时分发到 GitHub Releases 和 npm,两个渠道使用同一份已验证 tarball。应固定版本并核对所用渠道的证据:Release 的 `SHA256SUMS`;从 npm 安装时另核对 `dist.integrity`。Desktop profile 只能通过原生 Desktop 包管理器安装;获准且 registry 可用时输入 `dsh-github-copilot@0.4.0-alpha.56`,不是 URL 或本地文件。Desktop 保留 `desktop` profile,不能通过 DSH CLI 管理。受控离线 CLI 维护仅适用于独立具名 profile,不得作为 Desktop 安装绕行方案。[双渠道发布与 OIDC 要求](./docs/npm-distribution.md)保持不变。
159
159
 
160
160
  **Desktop package 更新与 Web 生命周期边界:**原生 manager 对已安装 package 原位升级返回的 `restart-required` 是权威结果,与移除/重加 plugin bundle 的行为是两个不同问题。任何包含服务重编排补丁(`cordis.patch.yml`,如本插件所采用的隔离路由 Web 搜索层)的插件升级均无法通过热重载重新绑定活动组件与 consumer,必须退出应用并冷重启 Desktop 才能完全生效。pinned public Loader characterization 记录了:使用 bundle 的精确 ID 且 provider 已激活时,分阶段首次添加可能在 routed row 启用后仍令全局 `ctx.web` 和 consumer 不可用;另一独立序列从完整冷加载且正常工作的 Web-routing composition 开始,移除后全局 `ctx.web` 与 consumer 不可用,重加/重试 reconciliation 仍未恢复。较早的临时 harness 使用别名 ID 且没有 active provider,因此其最终添加成功并不等同于精确 bundle fixture。这些都是合成 Loader 观察,不是原生 Desktop manager 覆盖,也不证明重启后恢复。不要用移除/重加 bundle 作为热升级绕行;遵循 manager 的升级结果及另行批准的重启要求。详见 [rc.2 生命周期 characterization 与有限的 public API 结论](https://github.com/cloga/dsh-github-copilot/blob/main/docs/web-lifecycle-rc2.md)。
161
161
 
@@ -435,8 +435,8 @@ node scripts/agent.mjs attribution "DeepSeek Harness (DSH)"
435
435
  `package.json` 声明公开 npm 分发。Release tag 必须严格等于 `v${package.json.version}`。预发布使用 `alpha`、`beta` 或 `rc` 及对应 npm dist-tag,只有稳定版使用 `latest`。Release workflow 执行 frozen install 和完整门禁,只打包一次(重试恢复原始归档),验证 `SHA256SUMS`,发布不可变 GitHub Release,再通过 OIDC 将同一份字节发布到 npm。任一渠道失败都表示交付未完成。首次建包须由获准环境中的维护者完成;staging 要求包已存在,不能代替首次建包。不会批量补发历史版本。
436
436
 
437
437
  ```sh
438
- curl -LO https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.0-alpha.55/dsh-github-copilot-0.4.0-alpha.55.tgz
439
- curl -LO https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.0-alpha.55/SHA256SUMS
438
+ curl -LO https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.0-alpha.56/dsh-github-copilot-0.4.0-alpha.56.tgz
439
+ curl -LO https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.0-alpha.56/SHA256SUMS
440
440
  sha256sum --check SHA256SUMS
441
441
  ```
442
442
 
@@ -444,7 +444,7 @@ PowerShell 可以对已下载的同一组文件执行:
444
444
 
445
445
  ```powershell
446
446
  $expected = (Get-Content .\SHA256SUMS).Split()[0]
447
- $actual = (Get-FileHash .\dsh-github-copilot-0.4.0-alpha.55.tgz -Algorithm SHA256).Hash.ToLowerInvariant()
447
+ $actual = (Get-FileHash .\dsh-github-copilot-0.4.0-alpha.56.tgz -Algorithm SHA256).Hash.ToLowerInvariant()
448
448
  if ($actual -cne $expected) { throw 'Release checksum mismatch' }
449
449
  ```
450
450
 
@@ -8,7 +8,7 @@
8
8
  },
9
9
  "package": {
10
10
  "name": "dsh-github-copilot",
11
- "version": "0.4.0-alpha.55"
11
+ "version": "0.4.0-alpha.56"
12
12
  },
13
13
  "evidence": {
14
14
  "kind": "source-and-synthetic-test-inventory",
package/lib/index.js CHANGED
@@ -1647,7 +1647,7 @@ let GitHubCopilotUsageController = (() => {
1647
1647
  //#endregion
1648
1648
  //#region package.json
1649
1649
  var name$1 = "dsh-github-copilot";
1650
- var version = "0.4.0-alpha.55";
1650
+ var version = "0.4.0-alpha.56";
1651
1651
  //#endregion
1652
1652
  //#region lib/types/probe.js
1653
1653
  /**
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "dsh-github-copilot",
3
3
  "description": "DSH companion for GitHub Copilot sign-in, account-aware model profiles, tool compatibility, and provider-hosted search.",
4
- "version": "0.4.0-alpha.55",
4
+ "version": "0.4.0-alpha.56",
5
5
  "publishConfig": {
6
6
  "access": "public",
7
7
  "registry": "https://registry.npmjs.org/",
@@ -128,7 +128,7 @@
128
128
  },
129
129
  "dependencies": {
130
130
  "@earendil-works/pi-ai": "0.87.1",
131
- "undici": "6.29.0",
131
+ "undici": "6.28.1",
132
132
  "zod": "^4.4.3"
133
133
  },
134
134
  "devDependencies": {