dsh-github-copilot 0.1.0-alpha.1.dsh.0.2.1.rc.3 → 0.1.0-alpha.2.dsh.0.2.1.rc.3

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
@@ -102,6 +102,12 @@ See `src/copilot-login-environment.ts` and `docs/copilot-accounts.md`.
102
102
 
103
103
  Identity presentation uses additive `ensureIdentity` Remotes, including explicit-Agent Session lookup. Keep `get` metadata-only; visible surfaces may ensure on their sixty-second cadence. Fresh ten-minute cache avoids requests, same-account consumers join a bounded flight, and failures cool down thirty seconds unless explicitly refreshed. Credential notifications revoke pending work even when token bytes are unchanged; no late cache publication. Quota may settle independently only with account-coherent metadata. Presentation cache never replaces fresh identity validation for switch, reauthorization or duplicate checks. Preserve strict sanitized diagnostics and Session/turn ownership (#309).
104
104
 
105
+ Models account-management/add controls apply a fifteen-second presentation
106
+ deadline only to metadata/identity reads (#346). A failed initial read offers
107
+ metadata-only Retry; late results and disposal cannot publish stale state.
108
+ Never apply this deadline to add/cancel/switch/reauthorize/remove mutations,
109
+ release their fences, cancel Host work or introduce an automatic retry.
110
+
105
111
  Account display names survive freshness expiry in bounded Host memory, never credential invalidation or failed verification. Visible account lists may ensure missing configured names without activating accounts; no disk name cache, credential copying or identity-based authorization. Turn admission captures the first verified name for the frozen account. A missing name may be filled by one existing nonforcing account-bound lookup only during that exact active, uncancelled turn/signal; never after turn/end/disposal. Evidence still requires actual native delivery and never reconstructs completed history (#322).
106
112
 
107
113
  The user approved independently authorized account records in the existing DSH credentials service. The canonical `llm-pi-ai/github-copilot` record remains unchanged as the compatibility account. Additional plugin-owned `github-copilot/account-<opaque-id>` records must be written directly by official pi-ai OAuth through public account-bound stores; never copy/move grants, refill the canonical record, introduce a separate credential storage service, patch Core, or implement another wire/catalog. Native `Models.getAuth()` and DSH `modifyRecord()` remain the refresh and serialization owners.
@@ -151,6 +157,7 @@ Alpha.25 admits native `subagent/descriptor` v3, already v3 in the retained rc.1
151
157
  - `src/serialize.ts`, `src/sse.ts`, `src/failure.ts`: protocol conversion and bounded error handling.
152
158
  - `src/response-error-body.ts`, `src/request-body-timeout.ts`, `src/request-upload-evidence.ts`: bounded clone-only HTTP error evidence and safe managed upload-timeout guidance. Request-scoped public Node diagnostic events supply numeric local body-write/header/ALPN evidence only after an exact verified `408/user_request_timeout`; absent events, multiple native requests and work limits stay explicit. Always dispose subscriptions when Fetch settles, without changing its arguments, Response/errors, dispatcher, proxy or retry owner. Local body-write completion is not upload duration, kernel ACK, supplier receipt or execution; its absence does not prove incomplete upload. Native failure classification/retry metadata stay unchanged; final JSON bytes are not tokens or a payload limit. A separate explicit opt-in compression setting is default-off and never activated by a 408; never infer overflow, auto-compact, trim history, switch models or add retries from a 408.
153
159
  - `src/responses-request-compression.ts`: asynchronous `node:zlib` gzip at `Z_BEST_SPEED` only for exact account-proven official Copilot HTTPS `/responses` JSON POSTs through the existing public Fetch seam. `github-copilot.responsesRequestCompression` defaults false; enforce the 256 KiB minimum, 32 MiB compression-work bound and both 5%/4 KiB savings thresholds. Skips retain the original request with a fixed reason, and cancellation/account/deadline fences run before dispatch. No custom Fetch, other protocol, explicit `auto`/WebSocket, DNS/proxy/dispatcher changes, context-admission or replay changes, resend after an encoding rejection, or new retry. Gzip is wire encoding, not compaction or proof of supplier receipt.
160
+ - Verified 408 error correlation (#276) adds only validated model/protocol, UTC header-observation time and strictly formatted `x-github-request-id` / `x-request-id` response IDs. Missing/malformed IDs stay unavailable; no other header values or new persisted population. IDs do not prove receipt/execution, and zero/unknown image composition cannot justify image-budget guidance.
154
161
  - `src/request-body-evidence.ts`, `src/request-body-composition.ts`: bounded numeric original-JSON spans for verified 408s and separately consented request observations. Keep replay validation/recovery at 16 MiB; only diagnostic composition may use the 32 MiB cooperative scanner with 64 Ki-character yields, a two-second monotonic deadline and four scan slots. Do not build a full payload object graph or decode image/replay values. Conversation/tool definitions/top-level system/residual partition total bytes; structural image and opaque replay spans are disjoint conversation subsets. Unknown/limited/cancelled evidence stays explicit. Opted-in large scans start after Fetch invocation without delaying ordinary native delivery; retained numeric rows may update after settlement only behind consent/clear/retention/eviction fences. Retain source strings only for bounded in-flight counting, never in storage/logs. Fetch-to-header time excludes analysis and is not upload duration. With gzip, report original JSON and prepared HTTP-body bytes separately; neither establishes delivered bytes. No automatic mitigation, timeout/retry changes or supplier-limit claim.
155
162
  - `src/copilot-stream-liveness.ts`: request-local HTTP/SSE byte-idle observation, paired with the public native adapter's bounded assistant-chunk deadline. Default five-minute byte idle and ten-minute semantic silence; no fake assistant output, private watchdog access, new retry or Core patch. Consumer think time is excluded; explicit WebSocket/auto stays native-only. `chatStreamLiveness: false` restores native-only timing. `chatMaxRequestImageBytes` retains Core's 20 MiB default; smaller explicit settings authorize only native image offload, not hidden history trimming or a guessed supplier limit. Synthetic heartbeat evidence is not production heartbeat proof.
156
163
  - `tests/`: unit and integration evidence; mirror the source area being changed.
package/CHANGELOG.md CHANGED
@@ -1,5 +1,12 @@
1
1
  # Changelog
2
2
 
3
+ ## 0.1.0-alpha.2.dsh.0.2.1.rc.3 (prepared)
4
+
5
+ - Bound account-management metadata and identity reads to fifteen seconds, provide metadata-only Retry after initial failure, and discard late results (#346). Account mutations retain their original locks and settlement; no Host cancellation or automatic retry.
6
+ - Align recovery and context notices with native composer side clearance on narrow and embedded layouts, avoid double-constraining nested disclosures, and distinguish primary Enable from quiet Cancel (#317). Explicit loss consent and native history/compaction ownership remain unchanged.
7
+ - Add validated model/protocol, UTC header-observation time and strictly formatted supplier request IDs to verified 408 diagnostics (#276). Recommend image-offload changes only when recognized image bytes are present. No transport, retry, timeout, account or stored-diagnostic changes; production timeout cause/frequency remains unproven.
8
+ - Retain exact DSH 0.2.1-rc.3 admission and the documented native hot-readd limitation. No Core changes, profile installation, sign-in, paid model probes or restart.
9
+
3
10
  ## 0.1.0-alpha.1.dsh.0.2.1.rc.3 (prepared)
4
11
 
5
12
  - Target exact official DSH 0.2.1-rc.3 at `1f81c047fc48fa190a683e469daa699857e9afe8` (#432, #435). Align engines, public peers, exact reviewer ownership and Windows/Linux tagged-source and published-artifact qualification without Core changes.
package/README.md CHANGED
@@ -8,7 +8,7 @@
8
8
 
9
9
  GitHub Copilot account discovery, contextual Auto routing and hosted search for DSH. The plugin reuses DSH's published native adapter, retaining a profile-wide account default with independent Session next-turn choices; it does not patch Core or maintain a second model catalog.
10
10
 
11
- **Historical stable release: [`0.4.1`](https://github.com/cloga/dsh-github-copilot/releases/tag/v0.4.1); pending DSH rc.3 adaptation: `0.1.0-alpha.1.dsh.0.2.1.rc.3`.** DSH `0.2.1-rc.3` is a prerelease. This plugin line is a compatibility candidate, not a production Core upgrade recommendation; Desktop artifacts/signatures are unverified. Each exact DSH Core version starts an independent plugin sequence at `0.1.0-alpha.1.dsh.<Core>`; same-Core fixes increment `alpha.N`. The suffix normalizes Core `0.2.1-rc.3` to `dsh.0.2.1.rc.3`, but compatibility is validated against explicit metadata, not guessed from the name. Existing published versions/tags remain unchanged. Published, installed and loaded states remain separate.
11
+ **Historical stable release: [`0.4.1`](https://github.com/cloga/dsh-github-copilot/releases/tag/v0.4.1); pending DSH rc.3 update: `0.1.0-alpha.2.dsh.0.2.1.rc.3`.** DSH `0.2.1-rc.3` is a prerelease. This plugin line is a compatibility candidate, not a production Core upgrade recommendation; Desktop artifacts/signatures are unverified. Each exact DSH Core version starts an independent plugin sequence at `0.1.0-alpha.1.dsh.<Core>`; same-Core fixes increment `alpha.N`. The suffix normalizes Core `0.2.1-rc.3` to `dsh.0.2.1.rc.3`, but compatibility is validated against explicit metadata, not guessed from the name. Existing published versions/tags remain unchanged. Published, installed and loaded states remain separate.
12
12
 
13
13
  Select by **exact Core**, never global SemVer maximum or npm `latest`/`alpha`.
14
14
  The read-only `node scripts/select-core-release.mjs 0.2.0-rc.2` command checks
@@ -160,7 +160,7 @@ Supply any launcher patches with repeated `--patch /absolute/file`. Require `sup
160
160
  For a **standalone named profile**:
161
161
 
162
162
  ```sh
163
- dsh plugin --profile web add https://github.com/cloga/dsh-github-copilot/releases/download/v0.1.0-alpha.1.dsh.0.2.1.rc.3/dsh-github-copilot-0.1.0-alpha.1.dsh.0.2.1.rc.3.tgz
163
+ dsh plugin --profile web add https://github.com/cloga/dsh-github-copilot/releases/download/v0.1.0-alpha.2.dsh.0.2.1.rc.3/dsh-github-copilot-0.1.0-alpha.2.dsh.0.2.1.rc.3.tgz
164
164
  ```
165
165
 
166
166
  The command above is a prepared-release example, usable only after publication and required CI qualification; it requires official DSH prerelease `0.2.1-rc.3`. **Do not install this candidate into production Desktop profiles.** Desktop artifacts/signatures and profile peer composition remain unverified; retain the existing compatible plugin on rc.2. The [historical rc.2 bundled-CLI qualification](./docs/npm-distribution.md#desktop-bundled-cli-on-official-rc2) does not qualify rc.3, and a generic/global `dsh` shim is not equivalent. No installation or restart is authorized.
@@ -185,7 +185,9 @@ Completed managed turns show **Account** beside native Usage. It records the req
185
185
 
186
186
  Saved account names can load without activating the account. Names are cached for the Host lifetime, invalidated by credential changes or failed verification, and never prove authorization or model access. A global switch requires fresh identity/model validation and confirmed settings persistence. If switching is blocked, let authorization or pinned work settle and use **Refresh account information**; unknown route/activity evidence remains a blocker. The dropdown, not a button beside each saved account, is the selection control.
187
187
 
188
- **Desktop lifecycle:** disable/remove/upgrade can require a full cold restart for Web service recomposition. If the plugin is Off and the native manager reports only `pending (waiting for service: web)`, do not repeatedly toggle or reinstall. Obtain restart approval and follow [rc.2 lifecycle guidance](./docs/web-lifecycle-rc2.md).
188
+ Account-management metadata and identity reads have a fifteen-second Client deadline instead of indefinite Checking. An initial read failure offers metadata-only **Retry**; late results are ignored. This does not cancel Host work, retry automatically or unlock an unresolved account mutation.
189
+
190
+ **Desktop lifecycle:** the current rc.3 public-Loader fixture preserves active Web consumers on a single-step add, but staged add and remove/re-add can leave the global `web` service unavailable and dependent account integration inactive. No feature-equivalent plugin-only recovery API is currently available; [issue #371](https://github.com/cloga/dsh-github-copilot/issues/371) remains open. An in-place upgrade without native HMR is explicitly `restart-required`; honor that manager result. The synthetic fixture does not justify repeated toggles or a restart when the manager has not requested one. See the [rc.3 lifecycle evidence](./docs/web-lifecycle-rc2.md).
189
191
 
190
192
  ## Auto and model preferences
191
193
 
@@ -266,7 +268,7 @@ Compaction feedback separates **compaction completed** and **subsequent request
266
268
 
267
269
  Running visible-history compaction notices stay visible. Confirmed success disappears eight seconds after first observation; settled failures, cancellation, unavailable status and enable prompts stay until **Close** (or the existing **Cancel**). Closing only hides this Session/operation/status notice, never changes consent, history or native proof, and never sends or retries. A bounded Client registration retains expiry/dismissal across incidental remounts and Session switches, not across teardown or eviction.
268
270
 
269
- For exact verified `408 / user_request_timeout`, diagnostics describe bounded request composition and observable timing, not a proven payload limit or root cause. Image counts include native Responses tool outputs; older stored diagnostics may have counted those images as residual history. Bytes are not tokens; timing is not upload duration. Small, image-free requests can also time out. Follow [request-budget and timeout guidance](./docs/copilot-compaction.md); do not automatically trim history, disable proof, switch models or add retries.
271
+ For exact verified `408 / user_request_timeout`, diagnostics describe bounded request composition and observable timing, not a proven payload limit or root cause. They include the validated model/protocol, UTC response-header observation time and strictly recognized supplier request IDs when available, without other headers or new stored diagnostics. IDs are correlation only, not receipt/execution proof. Image counts include native Responses tool outputs; older stored diagnostics may have counted those images as residual history. Only positive recognized image bytes suggest explicit image offload; zero/unknown image evidence does not. Bytes are not tokens; timing is not upload duration. Small, image-free requests can also time out. Follow [request-budget and timeout guidance](./docs/copilot-compaction.md); do not automatically trim history, disable proof, switch models or add retries.
270
272
 
271
273
  The experimental `github-copilot.responsesRequestCompression` option is **off by default**. When explicitly enabled, it losslessly gzips only eligible managed HTTP Responses requests through the existing native Fetch seam. It starts at 256 KiB, skips compression work above 32 MiB and requires at least 5% and 4 KiB savings; every skip sends the original request. This changes prepared HTTP body bytes, not context/token admission. Custom Fetch, explicit `auto`/WebSocket and other protocols remain native, and a gzip rejection is never automatically resent uncompressed. On a verified 408, diagnostics distinguish original JSON composition from the prepared gzip body size; neither proves delivery or cures every timeout. Installation does not enable the option.
272
274
 
@@ -321,6 +323,8 @@ The name “New Session” describes default inheritance, not a one-message feat
321
323
 
322
324
  Context evidence and Replay recovery use compact, centered notices bounded by the native composer width. Model/item counts and status refresh live in collapsed technical details; loss consent remains explicit. Context sampling warns only for a concrete incident, can be dismissed for that Session/incident, and never asserts the native meter's current value; native statistics stay unchanged. Switching accounts does not make old encrypted reasoning portable. The concise scope error points to explicit recovery or a new conversation; bounded, sanitized dispatch counts stay in Host diagnostics, not the main error. **Authorized** means permission is ready, not that a message was sent or recovery succeeded.
323
325
 
326
+ Notice frames also follow native horizontal clearance on narrow and embedded layouts; nested details do not apply the width limit twice. Recovery uses one primary **Enable** action and a quiet **Cancel**, without changing consent or initiating a retry.
327
+
324
328
  For a failed scheduled/background task, open its original Session to review **Replay recovery**. The latest recorded exact scope rejection keeps this entry available after temporary request diagnostics expire, Host restart or a picker change. Unavailable item/account diagnostics stay unknown; copied fork history does not create an entry. Enablement still requires the loss-disclosed Session policy choice and never resends the task. Check its possible side effects before choosing native Retry; a later native turn clears the old failure notice.
325
329
 
326
330
  ## Ownership and further reading
@@ -362,14 +366,14 @@ Commit attribution uses `Assisted-by` with the actual tool, never the model prov
362
366
  GitHub Releases and npm distribute the same original verified tarball. Pin a version; verify Release SHA-256 or npm `dist.integrity`. Never repack an immutable release or move/reuse its tag.
363
367
 
364
368
  ```sh
365
- curl -LO https://github.com/cloga/dsh-github-copilot/releases/download/v0.1.0-alpha.1.dsh.0.2.1.rc.3/dsh-github-copilot-0.1.0-alpha.1.dsh.0.2.1.rc.3.tgz
366
- curl -LO https://github.com/cloga/dsh-github-copilot/releases/download/v0.1.0-alpha.1.dsh.0.2.1.rc.3/SHA256SUMS
369
+ curl -LO https://github.com/cloga/dsh-github-copilot/releases/download/v0.1.0-alpha.2.dsh.0.2.1.rc.3/dsh-github-copilot-0.1.0-alpha.2.dsh.0.2.1.rc.3.tgz
370
+ curl -LO https://github.com/cloga/dsh-github-copilot/releases/download/v0.1.0-alpha.2.dsh.0.2.1.rc.3/SHA256SUMS
367
371
  sha256sum --check SHA256SUMS
368
372
  ```
369
373
 
370
374
  ```powershell
371
375
  $expected = (Get-Content .\SHA256SUMS).Split()[0]
372
- $actual = (Get-FileHash .\dsh-github-copilot-0.1.0-alpha.1.dsh.0.2.1.rc.3.tgz -Algorithm SHA256).Hash.ToLowerInvariant()
376
+ $actual = (Get-FileHash .\dsh-github-copilot-0.1.0-alpha.2.dsh.0.2.1.rc.3.tgz -Algorithm SHA256).Hash.ToLowerInvariant()
373
377
  if ($actual -cne $expected) { throw 'Release checksum mismatch' }
374
378
  ```
375
379
 
package/README.zh.md CHANGED
@@ -8,7 +8,7 @@
8
8
 
9
9
  为 DSH 提供 GitHub Copilot 账号模型发现、上下文 Auto 选模和 hosted search。插件复用 DSH 公开的原生适配器,保留 profile 全局默认账号,并支持 Session 后续 turn 指定独立账号;不修改 Core,也不维护第二套模型目录。
10
10
 
11
- **历史稳定版:[`0.4.1`](https://github.com/cloga/dsh-github-copilot/releases/tag/v0.4.1);DSH rc.3 适配候选:`0.1.0-alpha.1.dsh.0.2.1.rc.3`。** DSH `0.2.1-rc.3` 是预发布版本。本插件线是兼容性候选,不是生产 Core 升级建议;Desktop 制品/签名尚未核验。每个精确 DSH Core 版本都从独立插件序列 `0.1.0-alpha.1.dsh.<Core>` 开始;同一 Core 内修复递增 `alpha.N`。后缀将 Core `0.2.1-rc.3` 规范化为 `dsh.0.2.1.rc.3`,但兼容性仍须核对明确元数据,不能只猜版本名。既有已发布版本和 tag 不变。已发布、已安装、已加载仍是不同状态。
11
+ **历史稳定版:[`0.4.1`](https://github.com/cloga/dsh-github-copilot/releases/tag/v0.4.1);DSH rc.3 更新候选:`0.1.0-alpha.2.dsh.0.2.1.rc.3`。** DSH `0.2.1-rc.3` 是预发布版本。本插件线是兼容性候选,不是生产 Core 升级建议;Desktop 制品/签名尚未核验。每个精确 DSH Core 版本都从独立插件序列 `0.1.0-alpha.1.dsh.<Core>` 开始;同一 Core 内修复递增 `alpha.N`。后缀将 Core `0.2.1-rc.3` 规范化为 `dsh.0.2.1.rc.3`,但兼容性仍须核对明确元数据,不能只猜版本名。既有已发布版本和 tag 不变。已发布、已安装、已加载仍是不同状态。
12
12
 
13
13
  按**精确 Core**选版本,不按全局 SemVer 最大值或 npm `latest`/`alpha`。
14
14
  只读命令 `node scripts/select-core-release.mjs 0.2.0-rc.2` 先读取
@@ -135,7 +135,7 @@ node package/scripts/check-search-composition.mjs --profile-dir /absolute/profil
135
135
  **独立具名 profile**:
136
136
 
137
137
  ```sh
138
- dsh plugin --profile web add https://github.com/cloga/dsh-github-copilot/releases/download/v0.1.0-alpha.1.dsh.0.2.1.rc.3/dsh-github-copilot-0.1.0-alpha.1.dsh.0.2.1.rc.3.tgz
138
+ dsh plugin --profile web add https://github.com/cloga/dsh-github-copilot/releases/download/v0.1.0-alpha.2.dsh.0.2.1.rc.3/dsh-github-copilot-0.1.0-alpha.2.dsh.0.2.1.rc.3.tgz
139
139
  ```
140
140
 
141
141
  上面的命令是准备发布的示例,仅在发布且所需 CI 通过后可用;目标是官方 DSH 预发布版 `0.2.1-rc.3`。**不要把此候选安装到生产 Desktop profile。** Desktop 制品/签名及 profile peer 组合仍未核验;rc.2 应保留现有兼容插件。[历史 rc.2 随附 CLI 核验](./docs/npm-distribution.md#desktop-bundled-cli-on-official-rc2)不代表 rc.3 验收;全局/普通 `dsh` shim 不等价。本次不授权安装或重启。
@@ -160,7 +160,9 @@ Desktop 原生包管理器和已核验的随附 CLI 都有 profile 边界。
160
160
 
161
161
  读取已保存账号名称不必激活账号。名称在 Host 生命周期内缓存,凭据变更或验证失败会失效,也不证明授权或模型可用。全局切换需要新鲜身份/模型验证及设置持久化确认。切换被阻止时,等待授权或锁定工作结束,再**刷新账号信息**;未知路由/活动证据仍是阻塞。选择入口是下拉菜单,不是每个已保存账号旁的按钮。
162
162
 
163
- **Desktop 生命周期:**停用、移除、升级后的 Web 服务重组可能需要完整冷重启。若插件已 Off,而原生 manager 仅提示 `pending (waiting for service: web)`,不要反复切换或重装。先取得重启许可,遵循[rc.2 生命周期说明](./docs/web-lifecycle-rc2.md)。
163
+ 账号管理的元数据和身份读取使用 15 秒 Client 展示期限,避免无限 Checking。首次读取失败提供只读元数据**重试**;迟到结果不会覆盖新状态。不取消 Host 工作、不自动重试,也不会解锁尚未完成的账号修改操作。
164
+
165
+ **Desktop 生命周期:**当前 rc.3 公共 Loader 测试中,单步添加可保留正在使用的 Web 消费者;但分阶段添加或移除后重新添加,可能导致全局 `web` 服务不可用及依赖它的账号集成无法启动。目前没有功能等价的插件侧恢复 API;[#371](https://github.com/cloga/dsh-github-copilot/issues/371) 仍保持开放。没有原生 HMR 时,原生管理器会明确返回 `restart-required`;应遵循该结果。合成测试本身不构成反复切换或重启的依据。参见 [rc.3 生命周期证据](./docs/web-lifecycle-rc2.md)。
164
166
 
165
167
  ## Auto 与模型偏好
166
168
 
@@ -238,7 +240,7 @@ Copilot 搜索要求当前账号/协议证据及能力 proof。固定/fallba
238
240
 
239
241
  可见历史压缩进行中时提示持续可见。确认成功后从首次观察起八秒自动消失;失败、取消、状态不可用和开启提示保留至手动**关闭**(或原有**取消**)。关闭仅隐藏当前 Session/操作/状态的提示,不改变授权、历史或原生证据,不发送或重试。Client 注册范围内的有界状态使临时重挂载和会话切换不会重置期限;注册销毁或记录淘汰后不保留。
240
242
 
241
- 严格核验的 `408 / user_request_timeout`诊断给出有界请求构成和可观察耗时,不证明供应方 payload 上限或根因。图片统计包括原生 Responses 工具输出中的图片;旧的已存诊断可能把这些图片算作剩余历史。字节不是 tokens,耗时不是上传时长;小型无图请求也可能超时。参见[预算与超时指导](./docs/copilot-compaction.md),不要自动裁剪历史、禁用 proof、切换模型或增加重试。
243
+ 严格核验的 `408 / user_request_timeout`诊断给出有界请求构成和可观察耗时,不证明供应方 payload 上限或根因。还包含经过校验的模型/协议、收到响应头时的 UTC 时间及格式严格受限的供应方请求 ID;不添加其他头信息或新的持久诊断。ID 仅用于关联,不证明接收或执行。图片统计包括原生 Responses 工具输出中的图片;旧的已存诊断可能把这些图片算作剩余历史。只有明确测得图片字节时才提示显式图片 offload;图片为零或未知时不建议缩减图片预算。字节不是 tokens,耗时不是上传时长;小型无图请求也可能超时。参见[预算与超时指导](./docs/copilot-compaction.md),不要自动裁剪历史、禁用 proof、切换模型或增加重试。
242
244
 
243
245
  实验性配置 `github-copilot.responsesRequestCompression` **默认关闭**。显式开启后,仅通过现有原生 Fetch 接口对符合条件的托管 HTTP Responses 请求进行无损 gzip 编码。请求至少 256 KiB;超过 32 MiB 的压缩工作会跳过,且必须同时节省至少 5% 和 4 KiB;任何跳过都会发送原始请求。这只改变准备发送的 HTTP body 字节,不改变 context/token 准入。自定义 Fetch、显式 `auto`/WebSocket 和其他协议维持原生行为;gzip 被拒绝后绝不会自动改成未压缩请求重发。严格核验的 408 诊断会区分原始 JSON 组成字节与准备发送的 gzip body 大小;两者均不证明请求已送达,也不保证消除超时。安装不会启用此选项。
244
246
 
@@ -293,6 +295,8 @@ Credits 账号面板显示当前账号和 **切换**,下拉菜单只列已有
293
295
 
294
296
  上下文证据与回放恢复以紧凑、居中提示显示在输入框上方,宽度遵循原生输入框。模型、项数和状态刷新收进默认折叠的技术详情;有损恢复仍需明确确认。上下文采样只在明确事件时告警,可按 Session/事件关闭,且不会断言原生仪表当前值;原生统计不变。切换账号不会让旧加密推理自动变得可跨账号使用。简短 scope 错误指向显式恢复或新会话;有界、脱敏的请求结构计数留在 Host 诊断中,不挤占主错误。**已授权**只表示授权已准备好,不表示消息已发送或恢复已成功。
295
297
 
298
+ 窄屏和嵌入式布局也遵循原生输入框的横向留白,嵌套详情不会重复限宽。恢复操作突出一个**开启**主按钮,**取消**保持弱化;不改变损失确认或自动发起重试。
299
+
296
300
  定时/后台任务失败后,打开任务原来的 Session 查看**回放恢复**。最近一次已记录的精确 scope 拒绝,在临时请求诊断过期、Host 重启或更换模型选择后仍保留入口。不可用的项数/账号诊断保持未知;复制的 fork 历史不会创建入口。开启仍须用户确认有损 Session 策略,不会重发任务。自行选择原生重试前,请先检查失败任务可能已产生的副作用;后续原生轮次开始时清除旧失败提示。
297
301
 
298
302
  ## 所有权与深入阅读
@@ -334,14 +338,14 @@ Agent 从 `node scripts/agent.mjs describe --json`、`doctor --json`及`plan <ta
334
338
  GitHub Releases 和 npm 分发同一原始已校验 tarball。固定版本并核验 Release SHA-256 或 npm `dist.integrity`;不重打包不可变 Release、不移动/复用 tag。
335
339
 
336
340
  ```sh
337
- curl -LO https://github.com/cloga/dsh-github-copilot/releases/download/v0.1.0-alpha.1.dsh.0.2.1.rc.3/dsh-github-copilot-0.1.0-alpha.1.dsh.0.2.1.rc.3.tgz
338
- curl -LO https://github.com/cloga/dsh-github-copilot/releases/download/v0.1.0-alpha.1.dsh.0.2.1.rc.3/SHA256SUMS
341
+ curl -LO https://github.com/cloga/dsh-github-copilot/releases/download/v0.1.0-alpha.2.dsh.0.2.1.rc.3/dsh-github-copilot-0.1.0-alpha.2.dsh.0.2.1.rc.3.tgz
342
+ curl -LO https://github.com/cloga/dsh-github-copilot/releases/download/v0.1.0-alpha.2.dsh.0.2.1.rc.3/SHA256SUMS
339
343
  sha256sum --check SHA256SUMS
340
344
  ```
341
345
 
342
346
  ```powershell
343
347
  $expected = (Get-Content .\SHA256SUMS).Split()[0]
344
- $actual = (Get-FileHash .\dsh-github-copilot-0.1.0-alpha.1.dsh.0.2.1.rc.3.tgz -Algorithm SHA256).Hash.ToLowerInvariant()
348
+ $actual = (Get-FileHash .\dsh-github-copilot-0.1.0-alpha.2.dsh.0.2.1.rc.3.tgz -Algorithm SHA256).Hash.ToLowerInvariant()
345
349
  if ($actual -cne $expected) { throw 'Release checksum mismatch' }
346
350
  ```
347
351
 
@@ -8,13 +8,13 @@
8
8
  },
9
9
  "package": {
10
10
  "name": "dsh-github-copilot",
11
- "version": "0.1.0-alpha.1.dsh.0.2.1.rc.3"
11
+ "version": "0.1.0-alpha.2.dsh.0.2.1.rc.3"
12
12
  },
13
13
  "releaseLines": [
14
14
  { "core": "0.2.0-rc.2", "version": "0.4.2-alpha.15", "status": "published" },
15
15
  { "core": "0.2.1-alpha.4", "version": "0.4.2-alpha.16", "status": "published" },
16
16
  { "core": "0.2.1-alpha.5", "version": "0.1.0-alpha.2.dsh.0.2.1.alpha.5", "status": "published" },
17
- { "core": "0.2.1-rc.3", "version": "0.1.0-alpha.1.dsh.0.2.1.rc.3", "status": "pending" }
17
+ { "core": "0.2.1-rc.3", "version": "0.1.0-alpha.2.dsh.0.2.1.rc.3", "status": "pending" }
18
18
  ],
19
19
  "evidence": {
20
20
  "kind": "source-and-synthetic-test-inventory",
@@ -425,6 +425,15 @@ diagnostics do not establish the cause of earlier screenshots or prove live
425
425
  supplier health. Account switching, duplicate checks and reauthorization still
426
426
  require fresh authenticated identity validation, not the presentation cache.
427
427
 
428
+ The Models account-management and add-account controls bound each Client metadata
429
+ or identity read to fifteen seconds. A stalled read becomes an explicit read
430
+ failure, not an indefinitely pending Checking state; initial metadata failure
431
+ offers a metadata-only Retry. Late results cannot overwrite a later read, and
432
+ unmount removes the presentation deadline. This does not cancel Host work,
433
+ retry automatically or prove the cause of a previous transport failure.
434
+ Add, cancel, switch, reauthorize and remove mutations retain their existing
435
+ settlement and mutation fences; a read deadline never unlocks a pending mutation.
436
+
428
437
  ## Acceptance gates
429
438
 
430
439
  - Native public authorization and credentials services: independent writes,
@@ -94,7 +94,18 @@ HTTP `408 / user_request_timeout` is separate from input-budget overflow. For th
94
94
 
95
95
  `github-copilot.responsesRequestCompression` is a separate, experimental, default-off upload mitigation. Explicit opt-in gzips only account-proven official Copilot HTTPS `/responses` POSTs with a string JSON body, at the existing plugin-owned Fetch seam after native serialization, replay normalization and context admission. Custom Fetch, other APIs, explicit `auto` and WebSocket remain unchanged. It starts at 256 KiB, skips compression work above 32 MiB, and requires at least 5% and 4 KiB savings; every ineligible, oversized or uneconomic body remains the original native request. The asynchronous work is cancellation/account/deadline fenced before dispatch. No route pinning, hidden trimming, token/admission changes, identity resend after 415, retry or model switch is added.
96
96
 
97
- For a verified 408 after a compressed request, the diagnostic labels the original JSON composition bytes separately from the prepared gzip HTTP-body bytes (excluding transport framing). The compressed size is not confirmed delivered bytes, a token count, a provider size limit or proof of a network cause. A skipped compression may include one fixed reason; request bodies and headers are not retained. Synthetic controls support an opt-in mitigation only, not a universal provider capability or guaranteed 408 cure. Keep it off where endpoint support is unknown; disabling it affects later dispatches and installation never enables it.
97
+ For a verified 408 after a compressed request, the diagnostic labels the original JSON composition bytes separately from the prepared gzip HTTP-body bytes (excluding transport framing). The compressed size is not confirmed delivered bytes, a token count, a provider size limit or proof of a network cause. A skipped compression may include one fixed reason; request bodies and request headers are not retained. Synthetic controls support an opt-in mitigation only, not a universal provider capability or guaranteed 408 cure. Keep it off where endpoint support is unknown; disabling it affects later dispatches and installation never enables it.
98
+
99
+ The verified failure also includes the validated selected model, protocol and
100
+ UTC response-header observation time, captured before diagnostic analysis.
101
+ Only strictly formatted `x-github-request-id` (colon-separated hexadecimal)
102
+ and `x-request-id` (UUID-shaped) response values may appear, at most 128
103
+ characters each; malformed or missing values remain unavailable, not truncated.
104
+ They correlate a failure but do not prove request receipt or execution.
105
+ No other headers, response text or credentials are added, and these fields do
106
+ not enable or extend stored request diagnostics. Image-offload guidance appears
107
+ only when recognized image bytes are present; zero or unavailable image
108
+ composition never becomes a recommendation to lower the image budget.
98
109
 
99
110
  For [#263](https://github.com/cloga/dsh-github-copilot/issues/263), the same public final-body fetch hook additionally captures a monotonic fetch-invocation-to-response-header duration, before clone observation. This is round-trip latency, not measured upload progress, throughput or time spent reading the body. Only a verified exact error triggers numeric composition analysis; successful requests are not analyzed or retained.
100
111
 
@@ -22,7 +22,7 @@ Follow the [plugin-only boundary](../AGENTS.md#plugin-only-implementation-bounda
22
22
  - Cover missing/conflicting endpoints, missing/invalid limits, duplicate conflicting IDs, explicit denial, stale account snapshots, unsupported reasoning labels, unknown fields and hostile extra getters.
23
23
  - Exercise real published adapter/SDK code against local synthetic HTTP for all supported protocols, including tools, public summaries, two-turn opaque replay, images and interruption/retry paths. Synthetic results are not claims of live account availability.
24
24
  - The exact pinned rc.2 source trace must retain the reviewer's frozen `temperature: 0` request with no `purpose`/`sessionId`. Run that unchanged native reviewer through the managed route and real pi-ai serializer: default-off preserves temperature for thinking `true`, `false`, or absent; explicit opt-in omits it for each value without mutating caller input. Cover allow, deny, malformed verdict, HTTP error and cancellation with one wire attempt; only allow may execute the synthetic tool. Qualify the fixture against tagged source and exact published artifacts. Synthetic metadata proves no supplier temperature semantics.
25
- - Verify managed request-body timeout guidance only for the observed HTTP `408`, exact `user_request_timeout` code and request-body message. Bound clone reads to 8 KiB/250 ms, retain the original native response, and expose only fixed guidance plus final string-body UTF-8 bytes. Preserve failure code, retry metadata, cancellation, unchanged retry payloads and independent dispatches. Do not reclassify 408 as overflow, invent a safe byte threshold, change client timeouts, refresh OAuth, compact automatically or promise elimination of upstream failures.
25
+ - Verify managed request-body timeout guidance only for the observed HTTP `408`, exact `user_request_timeout` code and request-body message. Bound clone reads to 8 KiB/250 ms and retain the original native response. Expose bounded composition/timing, a validated selected model/protocol, UTC header-observation time and only strictly formatted `x-github-request-id` / `x-request-id` response correlation IDs; other headers and malformed values must not leak. Zero or unavailable image evidence must not recommend a smaller image budget. Preserve failure code, retry metadata, cancellation, unchanged retry payloads and independent dispatches. Do not reclassify 408 as overflow, invent a safe byte threshold, change client timeouts, refresh OAuth, compact automatically or promise elimination of upstream failures.
26
26
  - Verify byte-aware managed HTTP/SSE liveness through unchanged published and tagged adapters: heartbeat bytes may cross the original semantic deadline before actual output, but endless heartbeat-only output must hit the bounded native deadline. Real header/body stalls retain the original interval and a dispatch-local TIMEOUT; consumer think time, caller/credential cancellation, exact bytes, parser ownership and one native wire attempt remain unchanged. Explicit WebSocket/auto and opt-out retain native-only behavior. Preserve the 20 MiB native image budget by default; explicit smaller budgets must use native offload and retain mapped read-only paths/history, never hidden trimming or a claimed supplier threshold. These synthetic cases do not attest production heartbeat activity or cure HTTP 408.
27
27
  - Run source/test typechecks, complete repository tests, built Host/Client/Remote smoke, archive verification, and relevant unchanged-Core compatibility fixtures. Do not suppress type or test failures to bridge incompatible SDK versions.
28
28
 
@@ -116,6 +116,17 @@ cross-channel pointers and newer versions still fail closed. One channel
116
116
  succeeding is partial delivery.
117
117
  [Read-only reconciliation](./npm-publication-readback.md).
118
118
 
119
+ An unmapped, already-published alpha pointer may retain historical numeric
120
+ numbering such as `0.4.2-alpha.19.dsh.0.2.0.rc.2`. Its exact registry package
121
+ name/version and `engines.dsh` must verify the complete DSH suffix, without
122
+ requiring old bytes to adopt the new target's `0.1.0` numbering. Missing or
123
+ mismatched metadata still fails closed; new target validation and same-Core
124
+ monotonicity are unchanged. For publisher-only recovery changes after an
125
+ immutable release, the existing release plan selects the original annotated
126
+ tag's source SHA. The normal workflow recovers its original archive and uses
127
+ the separately checked-out current publisher only after byte comparison; it
128
+ never binds the immutable tag to the publisher revision or repacks the release.
129
+
119
130
  ## Installation preflight still applies
120
131
 
121
132
  Desktop's native package manager accepts an exact verified npm spec, not a URL
@@ -1,55 +1,51 @@
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.
1
+ # DSH 0.2.1-rc.3 Web lifecycle characterization
2
+
3
+ This keeps the existing rc.2 documentation path for link stability, but updates its contents to the repository's current supported Core, DSH `0.2.1-rc.3`. It exercises the exact published Loader/Web packages and plugin bundle through public APIs. The synthetic fixture makes no network calls and removes its temporary files and Loader fibers. It does not exercise the native Desktop package manager or claim the observed account-status incident was caused by any one internal transition. Earlier rc.2 findings are historical; the rc.3 test results below are authoritative for the current plugin line.
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 checks that `package.json` pins `@deepseek-ai/dsh-app-boot` and `@deepseek-ai/dsh-web` to the currently supported DSH version and uses the pinned public `cordis-plugin-loader`. It loads the built plugin-owned delegate and router through the public Loader, and creates temporary synthetic search/fetch providers and an independent consumer. It makes no network calls.
15
+
16
+ ## Observed transitions
17
+
18
+ The no-overlay control confirms the stock global `ctx.web`, registered synthetic search/fetch providers, and an independent global consumer can use both APIs. A **single-step** hot add of the exact bundle rows also preserves the global service and both active consumers in this fixture. That passing transition narrows the earlier rc.2 finding: it does not establish that every add sequence is safe.
19
+
20
+ For a **staged** first-add, immediately before the bundle is applied, global `ctx.web`, provider search and the independent consumer are active. Reconciliation is then split across three public Loader updates using the exact bundle IDs, enabling the Web delegate and routed rows in turn. The global service becomes unavailable and the consumer becomes pending; the registered provider remains callable through its captured official `WebRuntime`. This is not evidence that a single-step add or cold load fails.
21
+
22
+ For **remove/re-add**, the complete Web-routing rows are loaded at boot and the global service plus independent consumer are verified usable before removal. Removal leaves `ctx.web` unavailable and the consumer pending, although the captured official runtime still serves the synthetic provider. Re-adding the exact rows does not restore the global service. Calling the public `ctx.reflect.notify(['web'])` after re-add also does not recreate it; the consumer remains pending. This is a minimal public-Loader reproduction of the preventable hot-readd failure.
23
+
24
+ The lifecycle test does not call Core internals or mutate a live profile. The plugin's account integration is nested behind `ctx.inject()` for `web` in `src/index.ts`, so an unavailable global Web service can also keep dependent Host account services from activating. This links the reproduced service lifecycle failure to an account-controls availability risk; it does not prove that this was the sole cause of issue #371.
25
+
26
+ These synthetic observations do not reproduce or override the native Desktop manager's package-update contract. In the exact official rc.3 `dsh-plugin-manager` tests, an in-place upgrade without HMR returns `restart-required` and keeps the currently running version active; see [`package-reload.spec.ts`](https://github.com/deepseek-ai/deepseek-harness/blob/dsh-v0.2.1-rc.3/packages/boot/plugin-manager/tests/package-reload.spec.ts). A plugin cannot truthfully promise seamless application of that update. Honor an explicit manager restart requirement. This is separate from a hot remove/re-add transition for which the manager allows runtime reconciliation.
27
+
28
+ ## Historical rc.2 Desktop disable observation
29
+
30
+ The prior rc.2 Desktop investigation observed disable complete with the plugin shown as **Off**, then report 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
+ This native observation predates the current rc.3 package qualification and is not a claim about current Desktop behavior. The plugin cannot change or reclassify that native result after disable because its Client contribution has already been unloaded. Do not treat this historical warning as proof that every disable/remove requires restart, or convert other activation errors, mutation failures, or mixed diagnostics into success.
38
+
39
+ The tests named `known-bug characterization` intentionally pass when the rc.3 fixtures continue to exhibit the documented staged-add and remove/re-add states. They are evidence of a known limitation, not acceptance of the broken transitions.
40
+
41
+ ## Bounded public-API finding
42
+
43
+ In the exact published rc.3 `WebRuntime` declarations, public search/fetch APIs are provider registration plus `search()` and `fetch()`. Provider maps remain private. Although provider-selection configuration is volatile and read at each request, there is no public middleware/interceptor after provider selection, selected-provider lookup/dispatch operation, or service replacement/rebinding contract for active consumers.
44
+
45
+ The public-API test checks additive registration: a configured existing provider continues to win over an added routing provider, while two usable providers without a configured ID produce `WEB_PROVIDER_AMBIGUOUS`. Additive registration 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 `reflect.notify()` refreshes dependents but cannot recreate a missing global service, as the rc.3 re-add fixture demonstrates.
46
+
47
+ The plugin-only fix requires one of these official public capabilities: (1) disposable search-dispatch middleware on the existing `WebRuntime`, invoked after normal provider selection with `(request, signal, next)` so eligible Copilot calls can route while all other requests delegate unchanged; or (2) a Loader-owned service-replacement/recomposition operation that restores the service and rebinds dependents when isolation changes. The Web hook must preserve cancellation, result caps, configured-provider semantics and registration ownership. Neither contract is present in the pinned rc.3 API.
48
+
49
+ Without one of these APIs, a plugin workaround would either leave `ctx.web`/existing consumers stranded or change Web provider selection and routing behavior. A public notification alone is insufficient. No runtime workaround is made, and issue #371 remains open.
50
+
51
+ TLS trust configuration, including request-scoped CA handling for quota reads, does not affect Loader/Web service lifecycle and is not a remedy for this issue.