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

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/AGENTS.md CHANGED
@@ -205,6 +205,8 @@ Then run `pnpm verify:tarball -- artifacts/dsh-github-copilot-<package-version>.
205
205
 
206
206
  `pnpm verify` checks the Agent contract, source and local test types, baseline markers, a clean build, Vitest tests, Node tooling tests, and real built Host import/Client-loader/Remote smoke. `tests/fixtures` are intentionally excluded from local test typecheck because they import source from a separate pinned Core checkout. The checked-in code must pass; never suppress compiler errors or weaken a test to get a green report.
207
207
 
208
+ If the exact frozen install is blocked solely by an enterprise registry or network policy while the repository's GitHub Actions can obtain the unchanged pinned packages from an authorized official registry, record the attempted command and exact environmental failure as **local validation blocked**, not passed. A PR may proceed with that limitation disclosed; the complete required GitHub CI matrix, including its install, tests, build and package checks, is then the authoritative gate before merge. Never weaken or skip CI, substitute dependencies, bypass organizational restrictions, claim unrun local gates succeeded, or tag/release a revision whose required CI is not green. If CI has the same failure, resolve it through approved infrastructure rather than bypassing it.
209
+
208
210
  The release CI matrix targets only exact official `0.2.0-rc.2` on Windows and Linux; earlier pins are not support gates. It runs the unchanged tagged-source runtime fixture, optional native Chat fixture, and exact published-artifact adapter fixture. This is a required gate, not evidence that a candidate qualification has executed. `verify:upstream` is static seam-marker evidence. `verify:controlled-core` exclusively installs a temporary config fixture, refuses an existing target, and removes only its own file; it is not full plugin activation. Published-artifact synthetic adapter fixtures do not prove live provider transport. The release job must wait for the complete reusable CI matrix on the tagged revision, then verify its own packed bytes before publishing.
209
211
 
210
212
  ### Evidence and side effects
@@ -234,7 +236,7 @@ Never say GPT-6/search works merely because settings, typecheck or a package imp
234
236
 
235
237
  ## Changing capabilities
236
238
 
237
- Auto history compatibility (alpha.54, #204): official rc.2 `Session.append()` has no public ignorable-envelope option. Do not emit optional `github-copilot/auto-model-decision` events or borrow another event type; retain native real-model provenance and durable Auto selection without a new attribution footer. `scripts/repair-auto-model-history.mjs` is explicit source-checkout maintenance, not a runtime hook: strict pinned official v4 validation, check-only by default, optional detached repaired copy plus byte-exact backup. It never replaces live history. Applying a copy requires separately approved stopped writers and a fresh source-hash check. See `docs/automatic-model-routing.md`.
239
+ Auto history compatibility (alpha.54, #204): official rc.2 `Session.append()` has no public ignorable-envelope option. Do not emit optional `github-copilot/auto-model-decision` events or borrow another event type; retain native real-model provenance and durable Auto selection without new durable decision recording. The assistant-actions selection footer reads bounded Host-lifetime decisions through native agent-scoped lookup and compatible historical events. Explicit captured fixed selection alone proves Manual; missing evidence is unknown, never reconstructed from today's picker. Do not repeat model names, add Model details, change native Usage/context metering or modify parent DOM. `scripts/repair-auto-model-history.mjs` is explicit source-checkout maintenance, not a runtime hook: strict pinned official v4 validation, check-only by default, optional detached repaired copy plus byte-exact backup. It never replaces live history. Applying a copy requires separately approved stopped writers and a fresh source-hash check. See `docs/automatic-model-routing.md`.
238
240
 
239
241
  1. Identify the owning seam using `agent-contract.json`; do not duplicate an upstream owner.
240
242
  2. Add or update focused tests before changing deployment claims.
package/CHANGELOG.md CHANGED
@@ -1,9 +1,20 @@
1
1
  # Changelog
2
2
 
3
- ## 0.4.0-alpha.56 (prepared)
3
+ ## 0.4.0-alpha.58 (prepared)
4
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.
5
+ - Add compact Auto preference and expandable recorded reasons after the native reply time through the public assistant-actions slot; explicit fixed selection shows Manual, absent evidence shows Selection unknown. Remove the separate Model details candidate and repeated model name; actual models stay in native Usage.
6
+ - Keep new selection evidence in a bounded Host-lifetime store with native agent-scoped lookup, not incompatible durable events. Restart, disposal and eviction lose this evidence; compatible historical Auto records remain readable. Native Usage aggregation and its missing-route behavior are unchanged.
7
+ - Preserve plugin-owned credential invalidation and disposal reasons as specific `ABORTED` diagnostics, without changing transport retries, timeouts or partial output.
8
+ - Add offline native-SDK regressions distinguishing HTTP 408, transport termination, missing Responses terminal events, true cancellation and zero-usage measurement limits. These changes do not claim to fix upstream timeouts, disconnects or native context-meter resets.
9
+
10
+ ## 0.4.0-alpha.57 (released)
6
11
 
12
+ - Keep plugin-owned rc.2 lifecycle guidance visible before disable, removal, or upgrade, because the plugin UI is unloaded before Desktop can report dependent Web entries pending on a service (#185).
13
+ - Document that an already-Off plugin with only `pending (waiting for service: …)` dependent entries requires a full Desktop restart rather than repeated toggling, without reclassifying other native failures.
14
+ - Include the bounded rc.2 Web lifecycle characterization in the published package.
15
+
16
+ ## 0.4.0-alpha.56 (released)
17
+ - 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.
7
18
  ## 0.4.0-alpha.55 (prepared)
8
19
 
9
20
  - 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
@@ -12,7 +12,7 @@ A focused DSH companion for GitHub Copilot sign-in, account-aware model profiles
12
12
  ## Current experience
13
13
 
14
14
  - **Account and models:** sign in, inspect account-discovered models, refresh metadata, and manage the account from the native GitHub Copilot row under **Settings → Models**.
15
- - **Search routing:** choose the primary and fallback search providers under **Plugins → dsh-github-copilot → Details**. The page intentionally exposes only those user-facing choices; protocol probes, timeouts, allowlists, and transport switches are not presented as routine UI. If the updated routed service is not active yet, the card reports **Restart required** instead of presenting a broken form.
15
+ - **Search routing:** choose the primary and fallback search providers under **Plugins → dsh-github-copilot → Details**. The page intentionally exposes only those user-facing choices; protocol probes, timeouts, allowlists, and transport switches are not presented as routine UI. It also keeps the rc.2 lifecycle warning visible before disable/remove/upgrade actions. If the updated routed service is not active yet, the card reports **Restart required** instead of presenting a broken form.
16
16
  - **Usage:** eligible Copilot sessions get an optional **Credits** control beside the composer, with provider-reported billing-cycle data and explicit unavailable/stale states. The quota request alone combines Node default and OS trust roots without disabling certificate verification or relying on Desktop launcher environment inheritance.
17
17
  - **Compatibility:** the plugin applies Copilot-only tool-schema, reasoning-presentation, request-budget, and account-model compatibility through published DSH APIs. It does not patch Core or maintain a second model catalog.
18
18
 
@@ -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.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):
99
+ The commands below target the package version `0.4.0-alpha.58`. 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.56/dsh-github-copilot-0.4.0-alpha.56.tgz
112
+ dsh plugin --profile web add https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.0-alpha.58/dsh-github-copilot-0.4.0-alpha.58.tgz
113
113
  ```
114
114
 
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.
115
+ For Desktop profiles, use Desktop's native package manager with `dsh-github-copilot@0.4.0-alpha.58` 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
 
@@ -126,7 +126,9 @@ Then open the Models UI listed above, find **GitHub Copilot**, select **Sign in*
126
126
 
127
127
  ### Auto model routing
128
128
 
129
- The managed GitHub Copilot group includes **Auto · Balance**, **Auto · Efficiency**, and **Auto · Intelligence** as flat virtual picker rows. They share one account-verified eligible pool. Before preference, routing evaluates input headroom against each candidate's hard input budget, filtering out candidates that cannot accommodate current messages. Soft preferences distribute across upper/lower/center candidate bands using deterministic in-memory seeds to avoid monopolizing a single top candidate across Sessions. If no candidate fits, Auto selects the largest input capacity model and triggers compaction pressure on compressible history. Auto resolves once per Core turn to a real model; every tool step, retry and automatic compaction recovery in that turn stays on that model, while a later Chat or Goal turn may choose again. Image turns require an account-verified image-capable candidate. New turns retain Core's actual model/usage details but omit the plugin-specific Auto explanation footer: official rc.2 cannot safely append the optional plugin event. Compatible historical attribution remains visible. Search keeps its independent provider-owned model policy, and subagents / Team teammates continue to inherit Core's concrete route rather than being relabeled as Auto. See the [policy and mockup](./docs/automatic-model-routing.md); model exclusions and a nested picker are still proposals.
129
+ The managed GitHub Copilot group includes **Auto · Balance**, **Auto · Efficiency**, and **Auto · Intelligence** as flat virtual picker rows. They share one account-verified eligible pool. Before preference, routing evaluates input headroom against each candidate's hard input budget, filtering out candidates that cannot accommodate current messages. Soft preferences distribute across upper/lower/center candidate bands using deterministic in-memory seeds to avoid monopolizing a single top candidate across Sessions. If no candidate fits, Auto selects the largest input capacity model and triggers compaction pressure on compressible history. Auto resolves once per Core turn to a real model; every tool step, retry and automatic compaction recovery in that turn stays on that model, while a later Chat or Goal turn may choose again. Image turns require an account-verified image-capable candidate. New turns retain Core's actual model/usage details without adding unsafe plugin events. Search keeps its independent provider-owned model policy, and subagents / Team teammates continue to inherit Core's concrete route rather than being relabeled as Auto. See the [policy and mockup](./docs/automatic-model-routing.md); model exclusions and a nested picker are still proposals.
130
+
131
+ Completed Copilot replies show **Auto (preference)** and an expandable recorded reason after native Usage/time, or **Manual** only with captured explicit fixed-selection evidence. Missing evidence shows **Selection unknown**, never a guess from today's picker. There is no repeated model name or separate Model details button: actual model display stays in native Usage, whose missing-route behavior is unchanged. New selection records are bounded and Host-local; restart, disposal or eviction loses them. Compatible historical Auto records remain readable. The public assistant-actions slot supports internal wrapping only, not changing the native fixed-height row.
130
132
 
131
133
  **History loading error mentioning `github-copilot/auto-model-decision`:** alpha.54 prevents new incompatible events; upgrading or restarting does not repair existing logs. The [explicit recovery command](./docs/automatic-model-routing.md#recovering-affected-histories) validates a detached copy with the official codec and retains an exact original backup. Applying it to a live Session requires separate approval and stopped writers; no automatic history migration occurs.
132
134
 
@@ -153,9 +155,11 @@ Agents should treat the browser authorization as a human handoff, not as a token
153
155
  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
156
  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
157
 
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).
158
+ 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.58`, 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
159
 
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).
160
+ **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 disable, removal, or upgrade involving service recomposition (`cordis.patch.yml`, such as the isolated routed web search layer) may leave dependent entries pending until Desktop is fully exited and cold-restarted. If the native manager reports only entries such as `pending (waiting for service: web)` while this plugin already shows **Off**, the requested disabled state has been persisted; cold-restart Desktop instead of repeatedly toggling or reinstalling the plugin. Other errors are not covered by this guidance and must still be investigated.
161
+
162
+ 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; the native warning above is operational evidence, not proof that every pending diagnostic is harmless or that restart recovery has been exercised by the fixture. Do not use bundle removal/re-add as a hot-upgrade workaround. See [the rc.2 lifecycle characterization and bounded public-API finding](./docs/web-lifecycle-rc2.md).
159
163
 
160
164
  **Host TLS trust boundary:** this plugin adds system roots only to its quota request; it does not change Desktop process trust, sign-in, models, search or other requests. A correctly environmented Desktop launch previously restored quota, while a recovery launch without the inherited process variable caused it to regress despite HKCU retaining `NODE_USE_SYSTEM_CA=1`; normal relaunch restored it. The quota fix avoids this launcher dependency after an authorized upgrade and reload. No live Desktop profile, trust store or process is changed by the package alone.
161
165
 
@@ -424,8 +428,8 @@ Report the published Release URL, version, tag/commit and verified asset SHA-256
424
428
  `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
429
 
426
430
  ```sh
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
431
+ curl -LO https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.0-alpha.58/dsh-github-copilot-0.4.0-alpha.58.tgz
432
+ curl -LO https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.0-alpha.58/SHA256SUMS
429
433
  sha256sum --check SHA256SUMS
430
434
  ```
431
435
 
@@ -433,7 +437,7 @@ PowerShell can verify the same two downloaded files with:
433
437
 
434
438
  ```powershell
435
439
  $expected = (Get-Content .\SHA256SUMS).Split()[0]
436
- $actual = (Get-FileHash .\dsh-github-copilot-0.4.0-alpha.56.tgz -Algorithm SHA256).Hash.ToLowerInvariant()
440
+ $actual = (Get-FileHash .\dsh-github-copilot-0.4.0-alpha.58.tgz -Algorithm SHA256).Hash.ToLowerInvariant()
437
441
  if ($actual -cne $expected) { throw 'Release checksum mismatch' }
438
442
  ```
439
443
 
package/README.zh.md CHANGED
@@ -12,7 +12,7 @@
12
12
  ## 当前体验
13
13
 
14
14
  - **账号与模型:**在 **设置 → 模型** 的原生 GitHub Copilot 行内完成登录、查看账号发现模型、刷新元数据及账号管理。
15
- - **搜索路由:**在 **插件 → dsh-github-copilot → 详情**选择主搜索 Provider 与兜底 Provider。页面只保留用户真正需要的两项选择,不再把协议探测、超时、白名单或传输开关作为日常配置暴露。更新后的路由服务尚未激活时,卡片会明确显示 **需要重启生效(Restart required)**,而不是继续展示无法使用的表单。
15
+ - **搜索路由:**在 **插件 → dsh-github-copilot → 详情**选择主搜索 Provider 与兜底 Provider。页面只保留用户真正需要的两项选择,不再把协议探测、超时、白名单或传输开关作为日常配置暴露;同时会在停用/移除/升级前常驻显示 rc.2 生命周期提示。更新后的路由服务尚未激活时,卡片会明确显示 **需要重启生效(Restart required)**,而不是继续展示无法使用的表单。
16
16
  - **用量:**符合条件的 Copilot 会话会在输入框旁显示可选的 **Credits / 额度** 控件,展示供应方明确返回的计费周期数据,并如实区分不可用与历史快照。仅额度请求组合 Node 默认证书与系统信任根,无需依赖 Desktop launcher 的环境变量继承,且保持 TLS 验签。
17
17
  - **兼容处理:**插件通过 DSH 已发布公开接口提供 Copilot 专用 Tool Schema、Thinking 展示、请求预算及账号模型兼容,不修改 Core,也不维护第二套模型目录。
18
18
 
@@ -20,7 +20,7 @@
20
20
 
21
21
  截图来自当前构建 Client 的隔离浏览器 fixture,使用合成 Provider。它只证明已发布配置界面的形态,不证明真实凭据、账号权限、搜索成功或当前 Desktop 已加载。
22
22
 
23
- > 当前文档与安装命令对应版本 `0.4.0-alpha.56`。源码、发布制品、已安装版本和实际加载运行时需分别确认;本地升级和中断会话的重启仍需用户批准。
23
+ > 当前文档与安装命令对应版本 `0.4.0-alpha.58`。源码、发布制品、已安装版本和实际加载运行时需分别确认;本地升级和中断会话的重启仍需用户批准。
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.56/dsh-github-copilot-0.4.0-alpha.56.tgz
114
+ dsh plugin --profile web add https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.0-alpha.58/dsh-github-copilot-0.4.0-alpha.58.tgz
115
115
  ```
116
116
 
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。
117
+ Desktop profile 请在完成同样的预检后,使用 Desktop 原生包管理器安装 `dsh-github-copilot@0.4.0-alpha.58`。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
 
@@ -128,7 +128,9 @@ Desktop profile 请在完成同样的预检后,使用 Desktop 原生包管理
128
128
 
129
129
  ### Auto 模型路由
130
130
 
131
- 托管 GitHub Copilot 分组提供三个平铺的虚拟选择:**Auto · Balance**(均衡)、**Auto · Efficiency**(效率)和 **Auto · Intelligence**(智能)。三档共用当前账号验证过的合格模型池。在应用偏好前,路由会根据候选模型的硬输入预算计算输入余量,剔除无法容纳当前消息的候选。软偏好通过确定性内存种子在候选区间(上段/下段/中段)内分布,避免单一顶配模型跨 Session 被垄断。若所有候选均超限,Auto 会选择输入容量最大的模型并对可压缩历史触发 compaction pressure。Auto 在每个 Core turn 只解析一次;同轮工具步骤、重试和自动 compact 恢复使用同一真实模型,新轮次可重新选择。图片轮次必须有验证过的图片候选。新轮次保留 Core 的真实模型/用量信息,但暂不生成插件专属的 Auto 原因提示:官方 rc.2 无法安全追加这类可选插件事件;兼容历史中的归因仍保留显示。搜索仍由独立策略管理;原生子代理与 Team 队友继承 Core 的具体模型,不被重新标为 Auto。详见[策略与 mockup](./docs/automatic-model-routing.md);模型排除与嵌套菜单仍只是提案。
131
+ 托管 GitHub Copilot 分组提供三个平铺的虚拟选择:**Auto · Balance**(均衡)、**Auto · Efficiency**(效率)和 **Auto · Intelligence**(智能)。三档共用当前账号验证过的合格模型池。在应用偏好前,路由会根据候选模型的硬输入预算计算输入余量,剔除无法容纳当前消息的候选。软偏好通过确定性内存种子在候选区间(上段/下段/中段)内分布,避免单一顶配模型跨 Session 被垄断。若所有候选均超限,Auto 会选择输入容量最大的模型并对可压缩历史触发 compaction pressure。Auto 在每个 Core turn 只解析一次;同轮工具步骤、重试和自动 compact 恢复使用同一真实模型,新轮次可重新选择。图片轮次必须有验证过的图片候选。新轮次保留 Core 的真实模型/用量信息,不追加不兼容的插件事件。搜索仍由独立策略管理;原生子代理与 Team 队友继承 Core 的具体模型,不被重新标为 Auto。详见[策略与 mockup](./docs/automatic-model-routing.md);模型排除与嵌套菜单仍只是提案。
132
+
133
+ 已完成的 Copilot 回复在原生 Usage/时间后显示 **Auto(偏好)**,点信息按钮查看本轮记录的选择原因;只有捕获到明确固定选择才显示**手动**。缺记录显示**选择方式未知**,不借当前 picker 推断历史。不重复模型名、不另设 Model details 按钮:实际模型仍由原生 Usage 显示,其缺失归属行为未改变。新选择记录仅限当前 Host 内存且有容量上限,重启、释放 Agent 或淘汰后会丢失;兼容历史 Auto 记录仍可读取。公开 assistant-actions slot 只允许插件内部换行,不能改变原生固定高度尾栏。
132
134
 
133
135
  **历史加载报错包含 `github-copilot/auto-model-decision`:**alpha.54 阻止新问题事件写入,但升级或重启不会修复已有日志。[显式恢复命令](./docs/automatic-model-routing.md#recovering-affected-histories)使用官方 codec 校验独立修复副本,同时保存原始字节备份。替换实际 Session 日志必须另行批准并先停止所有写入者;插件不会自动迁移历史。
134
136
 
@@ -155,9 +157,11 @@ Agent 应把浏览器授权视为需要用户完成的 handoff,而不是自行
155
157
  5. 确认 **Signed in** 并检查自动发现结果,再请用户选择模型。已登录时打开 Models 会自动确保缺失/过期元数据,新鲜 ready 缓存不发请求。错误可使用 **Retry**,有意强制更新时使用 **Manage → Refresh models**,不作为常规设置步骤。状态读取本身不发现;登录、元数据与真实调用成功是独立证据。
156
158
  6. 只有用户明确要求断开账号时才使用 **Sign out**;它会删除 Copilot credential record,但保留 route settings。
157
159
 
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)保持不变。
160
+ 每个新版本默认同时分发到 GitHub Releases 和 npm,两个渠道使用同一份已验证 tarball。应固定版本并核对所用渠道的证据:Release 的 `SHA256SUMS`;从 npm 安装时另核对 `dist.integrity`。Desktop profile 只能通过原生 Desktop 包管理器安装;获准且 registry 可用时输入 `dsh-github-copilot@0.4.0-alpha.58`,不是 URL 或本地文件。Desktop 保留 `desktop` profile,不能通过 DSH CLI 管理。受控离线 CLI 维护仅适用于独立具名 profile,不得作为 Desktop 安装绕行方案。[双渠道发布与 OIDC 要求](./docs/npm-distribution.md)保持不变。
159
161
 
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)。
162
+ **Desktop package 更新与 Web 生命周期边界:**原生 manager 对已安装 package 原位升级返回的 `restart-required` 是权威结果,与移除/重加 plugin bundle 的行为是两个不同问题。涉及服务重编排补丁(`cordis.patch.yml`,如本插件所采用的隔离路由 Web 搜索层)的停用、移除或升级,可能让依赖条目保持 pending,直到完全退出并冷重启 Desktop。若原生 manager 只报告类似 `pending (waiting for service: web)` 的条目,同时本插件已经显示 **Off**,说明请求的停用状态已经落盘;请冷重启 Desktop,不要反复切换或重装插件。其它错误不属于此提示范围,仍需单独排查。
163
+
164
+ 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 观察;上述原生 warning 属于运行证据,不代表所有 pending 诊断都可忽略,也不代表 fixture 已证明重启恢复。不要用移除/重加 bundle 作为热升级绕行。详见 [rc.2 生命周期 characterization 与有限的 public API 结论](./docs/web-lifecycle-rc2.md)。
161
165
 
162
166
  **Host TLS trust 边界:**本插件只为额度请求添加系统信任根,不修改 Desktop 进程级信任、登录、模型、搜索或其他请求。之前带有正确环境变量的 Desktop 启动让额度恢复;后续恢复脚本启动没有继承进程变量,尽管 HKCU 保留 `NODE_USE_SYSTEM_CA=1`,额度仍再次失败;正常手动启动后又恢复。更新后的插件在获准升级和重新加载后消除额度请求对该继承链的依赖;仅发布包不会修改当前 Desktop profile、trust store 或进程。
163
167
 
@@ -435,8 +439,8 @@ node scripts/agent.mjs attribution "DeepSeek Harness (DSH)"
435
439
  `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
440
 
437
441
  ```sh
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
442
+ curl -LO https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.0-alpha.58/dsh-github-copilot-0.4.0-alpha.58.tgz
443
+ curl -LO https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.0-alpha.58/SHA256SUMS
440
444
  sha256sum --check SHA256SUMS
441
445
  ```
442
446
 
@@ -444,7 +448,7 @@ PowerShell 可以对已下载的同一组文件执行:
444
448
 
445
449
  ```powershell
446
450
  $expected = (Get-Content .\SHA256SUMS).Split()[0]
447
- $actual = (Get-FileHash .\dsh-github-copilot-0.4.0-alpha.56.tgz -Algorithm SHA256).Hash.ToLowerInvariant()
451
+ $actual = (Get-FileHash .\dsh-github-copilot-0.4.0-alpha.58.tgz -Algorithm SHA256).Hash.ToLowerInvariant()
448
452
  if ($actual -cne $expected) { throw 'Release checksum mismatch' }
449
453
  ```
450
454
 
@@ -8,7 +8,7 @@
8
8
  },
9
9
  "package": {
10
10
  "name": "dsh-github-copilot",
11
- "version": "0.4.0-alpha.56"
11
+ "version": "0.4.0-alpha.58"
12
12
  },
13
13
  "evidence": {
14
14
  "kind": "source-and-synthetic-test-inventory",
@@ -989,8 +989,11 @@
989
989
  "sourceMarkers": [
990
990
  {"file": "src/preview-route.ts", "marker": "GITHUB_COPILOT_AUTO_MODEL_ID"},
991
991
  {"file": "src/auto-model-host.ts", "marker": "keep attribution out of the log"},
992
- {"file": "src/auto-model-presentation.ts", "marker": "conversation.chat.turnTail"},
993
- {"file": "src/auto-model-presentation.ts", "marker": "data-time-hover-root"},
992
+ {"file": "src/auto-model-presentation.ts", "marker": "conversation.chat.assistant-actions"},
993
+ {"file": "src/auto-model-presentation.ts", "marker": "turnModelProvenanceDefinition"},
994
+ {"file": "src/turn-model-provenance.ts", "marker": "assistant/message"},
995
+ {"file": "src/turn-selection-card.ts", "marker": "Selection unknown"},
996
+ {"file": "src/turn-selection-remote.ts", "marker": "lookup: 'agent'"},
994
997
  {"file": "docs/automatic-model-routing.md", "marker": "plugin-only"}
995
998
  ],
996
999
  "tests": [
@@ -1000,7 +1003,8 @@
1000
1003
  {"file": "tests/auto-model-host.spec.ts", "name": "replaces Core virtual-Auto switch guidance with the resolved real route"},
1001
1004
  {"file": "tests/auto-model-presentation.spec.ts", "name": "folds a durable decision into turn-scoped credential-free attribution"},
1002
1005
  {"file": "tests/auto-model-presentation.spec.ts", "name": "omits attribution when a compatible history contains no optional decision"},
1003
- {"file": "tests/auto-model-presentation.spec.ts", "name": "places Auto attribution after the settled clock and reveals it only on hover"},
1006
+ {"file": "tests/turn-selection-card.spec.ts", "name": "reads exact completed turn evidence once through the public action slot and keeps actual model out of footer"},
1007
+ {"file": "tests/turn-model-provenance.spec.ts", "name": "retains known models around zero-usage failed attempts without reading payloads"},
1004
1008
  {"file": "tests/preview-route.spec.ts", "name": "publishes Auto as a virtual picker entry but refuses unresolved adapter dispatch"},
1005
1009
  {"file": "tests/fixtures/compaction-pressure-core.fixture.ts", "name": "shrinks durable history and rebuilds the switched model request without sending the oversized original"}
1006
1010
  ]
@@ -37,7 +37,7 @@ Before applying soft preferences, routing checks whether each candidate can acco
37
37
  3. **Headroom filtering:** Candidates with insufficient headroom (`estimatedInputTokens > hardInputLimit`) are filtered out. If one or more fitting candidates exist, soft preference selects among the `fitting` subset.
38
38
  4. **No-fit and compaction recovery:** If no candidate can fit the current messages:
39
39
  - Auto selects the candidate with the **largest input capacity** to give Core compaction maximum headroom.
40
- - It records a structured diagnostic in the decision event:
40
+ - Its in-memory routing decision includes a structured diagnostic (not a new durable event):
41
41
  - `fixed-content-cannot-fit`: the latest user turn alone exceeds maximum capacity and cannot be compacted away.
42
42
  - `compaction-unavailable`: compaction is disabled or has zero retries configured.
43
43
  - `attempted-but-still-oversized`: a compaction summary already exists in history and the turn remains oversized.
@@ -104,28 +104,13 @@ Chat Auto does not own or alter the independent `github-copilot-hosted` search p
104
104
 
105
105
  ## Attribution and explanation
106
106
 
107
- **Compatibility fix (alpha.54):** new turns omit the plugin-specific Auto footer. Official `0.2.0-rc.2` cannot set an `ignorable` envelope through public `Session.append()`, and its reader rejects unknown required plugin events. The plugin therefore stops writing `github-copilot/auto-model-decision` rather than patching Core, mutating event objects, or borrowing an unrelated event type. Core's actual model/usage provenance and Auto routing remain unchanged. Restore new attribution only when a supported public informational-event or equivalent storage seam has proven cold-read compatibility.
107
+ **Compatibility fix (alpha.54):** new turns omit plugin-specific Auto decision events. Official `0.2.0-rc.2` cannot set an `ignorable` envelope through public `Session.append()`, and its reader rejects unknown required plugin events. The plugin therefore stops writing `github-copilot/auto-model-decision` rather than patching Core, mutating event objects, or borrowing an unrelated event type. Core's actual model/usage provenance and Auto routing remain unchanged. Restore new decision recording only when a supported public informational-event or equivalent storage seam has proven cold-read compatibility.
108
108
 
109
- The following presentation remains available for compatible historical decision events; absence of such an event produces no plugin attribution or guessed explanation.
109
+ Completed Copilot replies show **Auto (preference)** with an information button, **Manual** with captured explicit fixed-selection evidence, or **Selection unknown** when that evidence is absent. The public `conversation.chat.assistant-actions` slot places the plugin's own flex item after native Usage/time using `order: 1`. There is no separate Model details entry or repeated model name. The native parent is a fixed-height, non-wrapping row: the plugin can shrink/wrap its own item but cannot promise whole-row wrapping, and does not modify native ancestors. A turn without a closing message has no assistant-actions anchor.
110
110
 
111
- Core already places route and usage details at the end of a completed turn. The MVP follows that interaction pattern rather than adding provider/model tags above the answer.
111
+ New Auto decisions and matching explicit fixed selections are captured at dispatch in a bounded in-memory store (64 Agents, 128 turns per Agent, first decision per turn). `githubCopilotTurnSelection.get` uses Core's native agent scope and lookup, with its existing Session resolution and ownership checks, rather than a plugin-owned arbitrary-session metadata endpoint. The lookup can use normal Core resume semantics; it is not a new access-control system. The Client reads once for the exact displayed Session/turn, cancels stale responses and never polls. Agent disposal, plugin disposal, eviction or Host restart removes evidence; no new Session event is emitted. Compatible historical Auto events can supply a recorded preference and reason; omitted historical preference is not guessed.
112
112
 
113
- For a completed Auto response, the attribution sits on the same footer row as Core's usage and clock, after the end time. It stays hidden until the message is hovered or focused, matching that chrome. It is not a separate line above the answer. The turn-tail display is:
114
-
115
- ```text
116
- [actions] [usage] [time] Auto · <actual model> ?
117
- ```
118
-
119
- The `?` opens a compact explanation using normalized facts such as:
120
-
121
- - short text turn;
122
- - standard turn;
123
- - large structured turn;
124
- - image capability required;
125
- - number of eligible account models;
126
- - number of models that can fit turn context (when restricted by input headroom).
127
-
128
- Earlier releases recorded a credential-free `github-copilot/auto-model-decision` Session event before Core persisted the real request header. Historical attribution is derived from that durable decision, never from the current picker or a later catalog snapshot. Raw prompts, credentials, provider response bodies, and guessed prices are never disclosed.
113
+ The expandable explanation reports only the actual routing classification, capacity preference and eligible/fitting counts. It is selection evidence, **not proof of execution**. Absence of Auto evidence never implies Manual, and today's picker/request header never fills a historical gap. Native Usage remains the only model/usage display; its existing all-or-nothing missing-route behavior is not fixed here. A metadata-only projection flags incomplete attempts/history without duplicating or allocating tokens. The disclosure never reads message content, replay data or credentials.
129
114
 
130
115
  ### Recovering affected histories
131
116
 
@@ -28,6 +28,7 @@ Follow the [plugin-only boundary](../AGENTS.md#plugin-only-implementation-bounda
28
28
  - Advertised reasoning labels that the native SDK cannot express must show `REASONING_EFFORTS_UNSUPPORTED` rather than being silently hidden or guessed. Such a warning need not disable ordinary model requests.
29
29
  - The Core-facing adapter integration uses the public `streamSimple` path. Its advanced protocol-specific `stream` entry must reject explicitly rather than accepting incompatible client objects from another SDK version. The event-stream compatibility boundary must verify the full public surface at compile time and preserve the original stream object.
30
30
  - Cached catalog entries do not authorize requests independently. A change in the current grant's model-permission list invalidates old proofs even when the token and account identity are unchanged; a new server-enabled model absent from the earlier grant list remains discoverable without rewriting the grant.
31
+ - A plugin-owned credential invalidation or disposal preserves its specific `ABORTED` diagnostic through the native stream boundary. Only the plugin's own abort reason identity authorizes that diagnostic; upstream text never does. This does not repair HTTP 408 request-body timeouts or transport termination, change retries/timeouts, or turn incomplete Responses output into success. SDK error events can contain initialized zero usage without a received measurement; the public usage object lacks a presence flag, so the plugin does not discard zeros or rewrite native context metering.
31
32
 
32
33
  ## Delivery and local acceptance
33
34
 
@@ -0,0 +1,55 @@
1
+ # DSH 0.2.0-rc.2 Web lifecycle characterization
2
+
3
+ This is a bounded characterization of the public Loader and Web APIs in the pinned DSH 0.2.0-rc.2 packages. It records a known limitation; it is not a passing acceptance test for desired add/remove/re-add behavior and does not exercise the native Desktop package manager.
4
+
5
+ ## Reproduce
6
+
7
+ From the repository root, after the normal build:
8
+
9
+ ```powershell
10
+ pnpm build
11
+ node --test tests/scripts/web-lifecycle-characterization.test.mjs
12
+ ```
13
+
14
+ The test uses the installed `@deepseek-ai/dsh-app-boot` and `@deepseek-ai/dsh-web` packages, loads the built plugin-owned delegate and router through the public Loader, and creates temporary synthetic provider/consumer modules. It makes no network calls and removes its temporary directory and Loader fibers in `finally`.
15
+
16
+ ## Observed transitions
17
+
18
+ The test first checks an unaffected no-overlay control: the stock global `ctx.web`, a registered synthetic search provider, and an independent global consumer are active, and a search returns the provider's marker result.
19
+
20
+ For the exact-bundle first-add sequence, it records the activation ordering explicitly. Immediately before the bundle is applied, global `ctx.web`, provider search, and the independent consumer are all active. During staged Loader reconciliation using the bundle's real Web/delegate/router IDs, global `ctx.web` becomes unavailable and the consumer becomes pending. The registered provider remains callable through the captured official WebRuntime, but adding the delegate and routed rows does not restore global `ctx.web` or the consumer in this fixture. This is not evidence that all cold starts fail: the separate cold-load fixture below succeeds.
21
+
22
+ For the separate remove/re-add sequence, the complete Web-routing rows are loaded at boot, then global `ctx.web`, provider search, and the consumer are verified usable before removal. Removal leaves global `ctx.web` unavailable and the consumer pending, while the captured official WebRuntime still answers through the registered synthetic provider. Before re-add, the test asserts and reports this stranded state rather than claiming an active-consumer precondition: removal has already invalidated it. Re-adding the exact candidate rows and retrying reconciliation do not restore global `ctx.web` or consumer activation in this fixture.
23
+
24
+ These are isolated public Loader observations using synthetic plugins. The older untracked reproduction used temporary IDs `delegate` and `routed` and no active provider; it reported that the staged route became usable after the final reconcile. The tracked fixture now uses the exact IDs from `cordis.patch.yml`, tests an active provider for the add/remove scenarios, and separates staged hot-add from a complete cold-loaded route. This accounts for the differing observations; the older alias-ID result is not evidence that the exact bundle hot-add succeeds.
25
+
26
+ The fixture does not exercise the native Desktop package manager, installation behavior, recovery after process restart, or every profile composition. The native manager's `restart-required` result for upgrading an installed package in place is a separate package-update boundary and is not evidence that the hot route lifecycle is repaired.
27
+
28
+ ## Native disable warning guidance
29
+
30
+ An observed native Desktop disable completed with the plugin shown as **Off**, then reported only:
31
+
32
+ ```text
33
+ web-search-deepseek: pending (waiting for service: web)
34
+ web-fetch-http: pending (waiting for service: web)
35
+ ```
36
+
37
+ The plugin cannot change or reclassify that native result after disable because its Client contribution has already been unloaded. While enabled, the plugin details card therefore warns that disable, removal, and upgrade operations affecting this Web composition require a full Desktop exit and cold restart. When the plugin is already **Off** and the native diagnostic contains only dependent entries pending while waiting for a service, restart Desktop instead of repeatedly toggling or reinstalling the plugin. This guidance does not convert other activation errors, mutation failures, or mixed diagnostics into success.
38
+
39
+ The test names begin `known-bug characterization` intentionally. They pass only when the pinned rc.2 fixtures continue to exhibit the documented states. A desired recovery acceptance test must instead prove that the consumer and provider stay usable through each supported transition, global `ctx.web` remains available, official/delegate/routed paths remain correctly owned, and teardown removes only the registrations owned by their fibers. Do not reinterpret this characterization test as approval of the current behavior.
40
+
41
+ ## Bounded public-API finding
42
+
43
+ In the exact published rc.2 `WebRuntime` declarations, public search/fetch APIs are provider registration plus `search()` and `fetch()`. Provider maps and configured provider IDs are private. There is no public middleware/interceptor, selected-provider lookup or dispatch operation, or service replacement/rebinding contract for active consumers.
44
+
45
+ The included public-API test also checks additive registration directly: a configured existing provider continues to win over an added routing provider, while two usable providers without a configured ID produce `WEB_PROVIDER_AMBIGUOUS`. It therefore cannot transparently preserve configured-provider selection and the plugin's exact primary/fallback dispatch. A second global `web` service collides with the existing service name; moving the official service to a child scope is the current composition that exposes the consumer lifecycle problem. Cordis effects own this plugin's own registrations but do not rebind other active fibers when a service's scope changes.
46
+
47
+ The specific extension needed for a feature-equivalent plugin route is a public, disposable search-dispatch middleware on the existing `WebRuntime`, invoked after normal provider selection and receiving `(request, signal, next)` so it can route eligible Copilot calls while delegating all other calls to the already-selected provider. It must preserve cancellation, result caps, configured-provider semantics, registration ownership, and unrelated consumers. A Loader-owned alternative would be an explicit public service-replacement operation that rebinds dependents when service isolation changes. Neither contract is present in the pinned rc.2 API examined here.
48
+
49
+ This finding is limited to those inspected APIs and the requirement to preserve current routing behavior for active global consumers; it is not a claim that all possible future APIs or behavior-changing opt-ins are impossible. An independent plugin-owned Web provider/configuration path would require user configuration and would alter existing selection/fallback behavior, so this task does not present it as a transparent repair.
50
+
51
+ ## TLS system trust is a separate, unverified operational option
52
+
53
+ The signed rc.2 Desktop main process starts the Host as a separate Node-mode child and passes inherited environment settings to it. The documented Node option `NODE_USE_SYSTEM_CA=1` keeps certificate validation enabled while adding the operating-system CA store to Node's trust sources. This changes which trusted roots Node accepts; it is not a Desktop setting and does not configure Chromium's separate trust behavior. Earlier no-credential HEAD diagnostics reached an HTTP response with system CA enabled where the signed Node runtime's default trust failed certificate verification. This does not prove the cause of the prior OAuth failure or that authentication will work.
54
+
55
+ If an operator later chooses this diagnostic option, use only a user-owned, reversible launcher that sets the variable for a fresh Desktop launch. First fully quit the existing Desktop so a new invocation cannot be handed off to an already-running single instance; then launch the signed executable as the new main process. Do not set a machine/user-global environment variable, edit the installed shortcut or Desktop profile, bypass TLS checks, or install roots. Keep the launcher process and any redirected standard I/O handles alive for the full Desktop process lifetime; do not pipe them through a short-lived shell, which can close the stream and produce `EPIPE`. Removing the user-owned launcher reverses this opt-in. This is a recommendation only: no launcher was created or run, no live Desktop state was changed, and no sign-in retry was performed.