dsh-github-copilot 0.4.0-alpha.65 → 0.4.0-alpha.68

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
@@ -236,6 +236,8 @@ Never say GPT-6/search works merely because settings, typecheck or a package imp
236
236
 
237
237
  ## Changing capabilities
238
238
 
239
+ Parent-model following uses the profile-wide `github-copilot.followParentModel` switch (default false), with a single control in the plugin-detail page (#234). Never require per-session enrollment for the ordinary experience. Preserve legacy `parentModelFollow` bindings independently, including when the broad switch is off. `src/parent-model-follow.ts` and the Auto Host integration use public projections and per-turn scoped routing, never descriptor/history/default writes. Child-owned explicit selections win; enabling authorizes replacement of creation-time route snapshots, not removal of later picker history. Only supported native spawn children and managed Copilot parents participate; roots, other providers, fork descriptors and historical dedicated policies remain native. Missing eligible parent evidence fails explicitly. Settings changes preserve admitted turns, and Client saves use one path-level CAS without credentials/discovery. See `docs/parent-model-follow.md` for requirements/mockup and `docs/automatic-model-routing.md` for exact-source evidence.
240
+
239
241
  Model preferences must survive the Client's owned-field projection before strict decoding. `excludedModelIds` is a hidden volatile Config leaf, read via `readInlineConfig`; exercise native SettingsForms CAS, fiber preservation and restart persistence, not only map-backed settings mocks. Missing preference/selection evidence leaves model rows read-only with named diagnostics and status-only Retry. Unknown exclusion state is not an empty exclusion set. Discovery diagnostics stay in a separate Manage disclosure.
240
242
 
241
243
  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`.
package/CHANGELOG.md CHANGED
@@ -1,5 +1,17 @@
1
1
  # Changelog
2
2
 
3
+ ## 0.4.0-alpha.68 (prepared)
4
+
5
+ - Add one **Follow parent model** control in plugin settings. Enable once for existing and new supported Copilot subagents and Team mates; no Session IDs or per-child setup (#234).
6
+ - Preserve active turns, child-owned manual selections and independent child Auto decisions. Keep legacy explicit bindings without hidden migration.
7
+ - Record requirements, implementation plan and a synthetic screenshot of the actual settings component; use narrow settings CAS and preserve unsaved search drafts.
8
+
9
+ ## 0.4.0-alpha.66 (prepared)
10
+
11
+ - Add explicit native child/direct-parent model-follow bindings, disabled by default. Enrolled children follow fixed selections on their next turn or independently resolve the parent's Auto preference against their own context (#229).
12
+ - Preserve in-flight turn routing, explicit child selections, native histories, defaults, credentials and permissions. Unknown lineage, unsupported children and missing parent evidence fail with named diagnostics rather than guessed models.
13
+ - Record exact-source inheritance research, configuration boundaries and validation limits. Native creation labels are not rewritten, and existing children are never automatically enrolled.
14
+
3
15
  ## 0.4.0-alpha.65 (prepared)
4
16
 
5
17
  - Fix Auto input undercount by using Core's public TokenMeter instead of passing Core messages to pi-ai's incompatible estimator and swallowing its errors (#230). Include assistant reasoning/tool history and retain native current-surface/tool-envelope measurement as a conservative floor.
package/README.md CHANGED
@@ -98,7 +98,7 @@ The Host reads GitHub's internal quota endpoint using the existing canonical OAu
98
98
 
99
99
  ## Install and sign in
100
100
 
101
- The commands below target the package version `0.4.0-alpha.65`. 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):
101
+ The commands below target the package version `0.4.0-alpha.68`. 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):
102
102
 
103
103
  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):
104
104
 
@@ -111,10 +111,10 @@ Include any launcher patch files with repeated `--patch /absolute/file` argument
111
111
  For a standalone named profile only, the supported CLI command is:
112
112
 
113
113
  ```sh
114
- dsh plugin --profile web add https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.0-alpha.65/dsh-github-copilot-0.4.0-alpha.65.tgz
114
+ dsh plugin --profile web add https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.0-alpha.68/dsh-github-copilot-0.4.0-alpha.68.tgz
115
115
  ```
116
116
 
117
- For Desktop profiles, use Desktop's native package manager with `dsh-github-copilot@0.4.0-alpha.65` 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.
117
+ For Desktop profiles, use Desktop's native package manager with `dsh-github-copilot@0.4.0-alpha.68` 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.
118
118
 
119
119
  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.
120
120
 
@@ -130,7 +130,9 @@ If preferences cannot be read, available account rows remain visible but read-on
130
130
 
131
131
  ### Auto model routing
132
132
 
133
- 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 after applying exact model exclusions. 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; if exclusions leave no eligible model, Auto fails closed. 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 a non-excluded 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). The nested management disclosure is plugin-owned; Core's picker remains flat.
133
+ **One setting for subagents:** in the plugin configuration page, turn on **Subagent models → Follow parent model** and Save. It applies to existing and new supported Copilot subagents and Team mates, without Session IDs or per-child setup. A fixed parent model takes effect on each child's next turn; Auto inherits the same preference but chooses using each child's own context. Running turns stay unchanged and child-owned manual selections still win. Default Off (`github-copilot.followParentModel: false`). Enabling replaces creation-time model choices; it never clears explicit child selection history. Legacy `parentModelFollow` bindings remain active independently and are not migrated. See [requirements, mockup and boundaries](./docs/parent-model-follow.md). Native Team creation labels are not rewritten.
134
+
135
+ 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 after applying exact model exclusions. 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; if exclusions leave no eligible model, Auto fails closed. 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 a non-excluded 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. Today, native subagents and Team teammates initialize from the parent's latest recorded request route (or creation options before its first request); this is not a live link, and a route snapshot does not prove Auto intent. The requested per-child-turn inheritance behavior and Core/plugin boundary are documented in the [policy](./docs/automatic-model-routing.md#requested-parent-to-child-selection-inheritance). The nested management disclosure is plugin-owned; Core's picker remains flat.
134
136
 
135
137
  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.
136
138
 
@@ -163,7 +165,7 @@ Agents should treat the browser authorization as a human handoff, not as a token
163
165
  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.
164
166
  6. Use **Sign out** only when the user explicitly asks to disconnect the account. It deletes the Copilot credential record but preserves route settings.
165
167
 
166
- 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.65`, 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).
168
+ 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.68`, 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).
167
169
 
168
170
  **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.
169
171
 
@@ -438,8 +440,8 @@ Report the published Release URL, version, tag/commit and verified asset SHA-256
438
440
  `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.
439
441
 
440
442
  ```sh
441
- curl -LO https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.0-alpha.65/dsh-github-copilot-0.4.0-alpha.65.tgz
442
- curl -LO https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.0-alpha.65/SHA256SUMS
443
+ curl -LO https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.0-alpha.68/dsh-github-copilot-0.4.0-alpha.68.tgz
444
+ curl -LO https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.0-alpha.68/SHA256SUMS
443
445
  sha256sum --check SHA256SUMS
444
446
  ```
445
447
 
@@ -447,7 +449,7 @@ PowerShell can verify the same two downloaded files with:
447
449
 
448
450
  ```powershell
449
451
  $expected = (Get-Content .\SHA256SUMS).Split()[0]
450
- $actual = (Get-FileHash .\dsh-github-copilot-0.4.0-alpha.65.tgz -Algorithm SHA256).Hash.ToLowerInvariant()
452
+ $actual = (Get-FileHash .\dsh-github-copilot-0.4.0-alpha.68.tgz -Algorithm SHA256).Hash.ToLowerInvariant()
451
453
  if ($actual -cne $expected) { throw 'Release checksum mismatch' }
452
454
  ```
453
455
 
package/README.zh.md CHANGED
@@ -20,7 +20,7 @@
20
20
 
21
21
  截图来自当前构建 Client 的隔离浏览器 fixture,使用合成 Provider。它只证明已发布配置界面的形态,不证明真实凭据、账号权限、搜索成功或当前 Desktop 已加载。
22
22
 
23
- > 当前文档与安装命令对应版本 `0.4.0-alpha.65`。源码、发布制品、已安装版本和实际加载运行时需分别确认;本地升级和中断会话的重启仍需用户批准。
23
+ > 当前文档与安装命令对应版本 `0.4.0-alpha.68`。源码、发布制品、已安装版本和实际加载运行时需分别确认;本地升级和中断会话的重启仍需用户批准。
24
24
 
25
25
  Web search 路由现在优先显示在插件详情页;宿主不支持详情页插槽时才回退到 **设置 → 模型**或独立 Web search section。搜索子 Fiber 仍独立等待 Remote,不影响账号控件和既有搜索安全检查。
26
26
 
@@ -113,10 +113,10 @@ node package/scripts/check-search-composition.mjs --profile-dir /absolute/profil
113
113
  仅对独立的具名 profile,获准且网络可用时,可通过受支持的 CLI 命令安装:
114
114
 
115
115
  ```sh
116
- dsh plugin --profile web add https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.0-alpha.65/dsh-github-copilot-0.4.0-alpha.65.tgz
116
+ dsh plugin --profile web add https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.0-alpha.68/dsh-github-copilot-0.4.0-alpha.68.tgz
117
117
  ```
118
118
 
119
- Desktop profile 请在完成同样的预检后,使用 Desktop 原生包管理器安装 `dsh-github-copilot@0.4.0-alpha.65`。Desktop 保留 `desktop` profile,CLI 不负责管理。若 registry 被公司封禁或不可用,不要更换网络绕行或使用离线 CLI;请停止。[受控离线 CLI 流程](./docs/npm-distribution.md#controlled-offline-cli-maintenance-for-standalone-profiles)仅适用于独立具名 profile,不适用于 Desktop。
119
+ Desktop profile 请在完成同样的预检后,使用 Desktop 原生包管理器安装 `dsh-github-copilot@0.4.0-alpha.68`。Desktop 保留 `desktop` profile,CLI 不负责管理。若 registry 被公司封禁或不可用,不要更换网络绕行或使用离线 CLI;请停止。[受控离线 CLI 流程](./docs/npm-distribution.md#controlled-offline-cli-maintenance-for-standalone-profiles)仅适用于独立具名 profile,不适用于 Desktop。
120
120
 
121
121
  随后打开上表对应的 Models UI,找到 **GitHub Copilot**,点击 **Sign in** 并完成 GitHub device-code 流程。安装会修改指定 profile;是否立即激活取决于该 profile 的常规 reload/restart 策略。
122
122
 
@@ -132,7 +132,9 @@ Desktop profile 请在完成同样的预检后,使用 Desktop 原生包管理
132
132
 
133
133
  ### Auto 模型路由
134
134
 
135
- 托管 GitHub Copilot 分组提供三个平铺的虚拟选择:**Auto · Balance**(均衡)、**Auto · Efficiency**(效率)和 **Auto · Intelligence**(智能)。三档先应用精确模型排除,再共用当前账号验证过的合格模型池。在应用偏好前,路由会根据候选模型的硬输入预算计算输入余量,剔除无法容纳当前消息的候选。软偏好通过确定性内存种子在候选区间(上段/下段/中段)内分布,避免单一顶配模型跨 Session 被垄断。若所有候选均超限,Auto 会选择输入容量最大的模型并对可压缩历史触发 compaction pressure;若排除后没有任何合格模型,则 Auto 关闭式失败。Auto 在每个 Core turn 只解析一次;同轮工具步骤、重试和自动 compact 恢复使用同一真实模型,新轮次可重新选择。图片轮次必须有未被排除且已验证的图片候选。新轮次保留 Core 的真实模型/用量信息,不追加不兼容的插件事件。搜索仍由独立策略管理;原生子代理与 Team 队友继承 Core 的具体模型,不被重新标为 Auto。详见[策略与 mockup](./docs/automatic-model-routing.md)。嵌套管理折叠区由插件提供;Core picker 仍保持平铺。
135
+ **子代理只需设置一次:** 在插件配置页打开 **Subagent models → Follow parent model** 并保存,即应用于已有和新创建的受支持 Copilot 子代理及 Team mate,无需填写 Session ID 或逐个登记。父会话为固定模型时,子会话从下一轮跟随;父会话为 Auto 时,继承相同偏好并按各自上下文独立选模。正在执行的轮次不变,子会话自己的手动选择仍优先。默认关闭(`github-copilot.followParentModel: false`)。开启意味着接管创建时保存的模型选择,但不清除子会话的显式选择历史。旧 `parentModelFollow` 绑定独立保留,不自动迁移。参见[需求、mockup 与边界](./docs/parent-model-follow.md)。原生 Team 的创建时模型标签不会被改写。
136
+
137
+ 托管 GitHub Copilot 分组提供三个平铺的虚拟选择:**Auto · Balance**(均衡)、**Auto · Efficiency**(效率)和 **Auto · Intelligence**(智能)。三档先应用精确模型排除,再共用当前账号验证过的合格模型池。在应用偏好前,路由会根据候选模型的硬输入预算计算输入余量,剔除无法容纳当前消息的候选。软偏好通过确定性内存种子在候选区间(上段/下段/中段)内分布,避免单一顶配模型跨 Session 被垄断。若所有候选均超限,Auto 会选择输入容量最大的模型并对可压缩历史触发 compaction pressure;若排除后没有任何合格模型,则 Auto 关闭式失败。Auto 在每个 Core turn 只解析一次;同轮工具步骤、重试和自动 compact 恢复使用同一真实模型,新轮次可重新选择。图片轮次必须有未被排除且已验证的图片候选。新轮次保留 Core 的真实模型/用量信息,不追加不兼容的插件事件。搜索仍由独立策略管理。目前原生子代理与 Team 队友会以 master 最近记录的请求 route 初始化(master 尚未发出请求时回退到创建配置);这不是随 master 后续选择自动变化的动态关联,route 快照也不能证明 Auto 意图已继承。每轮跟随 master 固定模型、或让子代理按自身上下文独立执行 Auto 的目标行为及 Core/插件边界,见[设计记录](./docs/automatic-model-routing.md#requested-parent-to-child-selection-inheritance)。嵌套管理折叠区由插件提供;Core picker 仍保持平铺。
136
138
 
137
139
  已完成的 Copilot 回复在原生 Usage/时间后显示 **Auto(偏好)**,点信息按钮查看本轮记录的选择原因;只有捕获到明确固定选择才显示**手动**。缺记录显示**选择方式未知**,不借当前 picker 推断历史。不重复模型名、不另设 Model details 按钮:实际模型仍由原生 Usage 显示,其缺失归属行为未改变。新选择记录仅限当前 Host 内存且有容量上限,重启、释放 Agent 或淘汰后会丢失;兼容历史 Auto 记录仍可读取。公开 assistant-actions slot 只允许插件内部换行,不能改变原生固定高度尾栏。
138
140
 
@@ -165,7 +167,7 @@ Agent 应把浏览器授权视为需要用户完成的 handoff,而不是自行
165
167
  5. 确认 **Signed in** 并检查自动发现结果,再请用户选择模型。已登录时打开 Models 会自动确保缺失/过期元数据,新鲜 ready 缓存不发请求。错误可使用 **Retry**,有意强制更新时使用 **Manage → Refresh models**,不作为常规设置步骤。状态读取本身不发现;登录、元数据与真实调用成功是独立证据。
166
168
  6. 只有用户明确要求断开账号时才使用 **Sign out**;它会删除 Copilot credential record,但保留 route settings。
167
169
 
168
- 每个新版本默认同时分发到 GitHub Releases 和 npm,两个渠道使用同一份已验证 tarball。应固定版本并核对所用渠道的证据:Release 的 `SHA256SUMS`;从 npm 安装时另核对 `dist.integrity`。Desktop profile 只能通过原生 Desktop 包管理器安装;获准且 registry 可用时输入 `dsh-github-copilot@0.4.0-alpha.65`,不是 URL 或本地文件。Desktop 保留 `desktop` profile,不能通过 DSH CLI 管理。受控离线 CLI 维护仅适用于独立具名 profile,不得作为 Desktop 安装绕行方案。[双渠道发布与 OIDC 要求](./docs/npm-distribution.md)保持不变。
170
+ 每个新版本默认同时分发到 GitHub Releases 和 npm,两个渠道使用同一份已验证 tarball。应固定版本并核对所用渠道的证据:Release 的 `SHA256SUMS`;从 npm 安装时另核对 `dist.integrity`。Desktop profile 只能通过原生 Desktop 包管理器安装;获准且 registry 可用时输入 `dsh-github-copilot@0.4.0-alpha.68`,不是 URL 或本地文件。Desktop 保留 `desktop` profile,不能通过 DSH CLI 管理。受控离线 CLI 维护仅适用于独立具名 profile,不得作为 Desktop 安装绕行方案。[双渠道发布与 OIDC 要求](./docs/npm-distribution.md)保持不变。
169
171
 
170
172
  **Desktop package 更新与 Web 生命周期边界:**原生 manager 对已安装 package 原位升级返回的 `restart-required` 是权威结果,与移除/重加 plugin bundle 的行为是两个不同问题。涉及服务重编排补丁(`cordis.patch.yml`,如本插件所采用的隔离路由 Web 搜索层)的停用、移除或升级,可能让依赖条目保持 pending,直到完全退出并冷重启 Desktop。若原生 manager 只报告类似 `pending (waiting for service: web)` 的条目,同时本插件已经显示 **Off**,说明请求的停用状态已经落盘;请冷重启 Desktop,不要反复切换或重装插件。其它错误不属于此提示范围,仍需单独排查。
171
173
 
@@ -449,8 +451,8 @@ node scripts/agent.mjs attribution "DeepSeek Harness (DSH)"
449
451
  `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 要求包已存在,不能代替首次建包。不会批量补发历史版本。
450
452
 
451
453
  ```sh
452
- curl -LO https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.0-alpha.65/dsh-github-copilot-0.4.0-alpha.65.tgz
453
- curl -LO https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.0-alpha.65/SHA256SUMS
454
+ curl -LO https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.0-alpha.68/dsh-github-copilot-0.4.0-alpha.68.tgz
455
+ curl -LO https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.0-alpha.68/SHA256SUMS
454
456
  sha256sum --check SHA256SUMS
455
457
  ```
456
458
 
@@ -458,7 +460,7 @@ PowerShell 可以对已下载的同一组文件执行:
458
460
 
459
461
  ```powershell
460
462
  $expected = (Get-Content .\SHA256SUMS).Split()[0]
461
- $actual = (Get-FileHash .\dsh-github-copilot-0.4.0-alpha.65.tgz -Algorithm SHA256).Hash.ToLowerInvariant()
463
+ $actual = (Get-FileHash .\dsh-github-copilot-0.4.0-alpha.68.tgz -Algorithm SHA256).Hash.ToLowerInvariant()
462
464
  if ($actual -cne $expected) { throw 'Release checksum mismatch' }
463
465
  ```
464
466
 
@@ -8,7 +8,7 @@
8
8
  },
9
9
  "package": {
10
10
  "name": "dsh-github-copilot",
11
- "version": "0.4.0-alpha.65"
11
+ "version": "0.4.0-alpha.68"
12
12
  },
13
13
  "evidence": {
14
14
  "kind": "source-and-synthetic-test-inventory",
@@ -998,6 +998,10 @@
998
998
  "sourceMarkers": [
999
999
  {"file": "src/preview-route.ts", "marker": "GITHUB_COPILOT_AUTO_MODEL_ID"},
1000
1000
  {"file": "src/auto-model-host.ts", "marker": "keep attribution out of the log"},
1001
+ {"file": "src/parent-model-follow.ts", "marker": "resolveParentModel"},
1002
+ {"file": "src/config.ts", "marker": "parentModelFollow"},
1003
+ {"file": "src/config.ts", "marker": "followParentModel"},
1004
+ {"file": "src/parent-model-follow-card.ts", "marker": "Follow parent model"},
1001
1005
  {"file": "src/auto-model-host.ts", "marker": "COPILOT_AUTO_TOKEN_METER_UNAVAILABLE"},
1002
1006
  {"file": "src/auto-model-presentation.ts", "marker": "conversation.chat.assistant-actions"},
1003
1007
  {"file": "src/auto-model-presentation.ts", "marker": "turnModelProvenanceDefinition"},
@@ -1007,6 +1011,8 @@
1007
1011
  {"file": "docs/automatic-model-routing.md", "marker": "plugin-only"}
1008
1012
  ],
1009
1013
  "tests": [
1014
+ {"file": "tests/auto-model-host.spec.ts", "name": "follows fixed and Auto parents using %s without writing child selections"},
1015
+ {"file": "tests/scripts/parent-model-follow.test.mjs", "name": "explicit same-model and different-model child selections both win"},
1010
1016
  {"file": "tests/auto-model-routing.spec.ts", "name": "classifies only the latest user turn and selects a deterministic capacity tier"},
1011
1017
  {"file": "tests/auto-model-routing.spec.ts", "name": "does not discard a complete Core assistant message when it contains reasoning"},
1012
1018
  {"file": "tests/auto-model-routing.spec.ts", "name": "retains the native current-surface and tool-envelope measurement as an input floor"},
@@ -140,16 +140,139 @@ The compressed output keeps the header in its own first zstd frame, as required
140
140
 
141
141
  General native subagent Auto inheritance is **not** in the base MVP.
142
142
 
143
- In official DSH 0.2.0-rc.2, `TeamRoster.spawn` calls `ctx.subagents.startContinuable` without `request.agentOptions`. Core's `resolveChildAgentOptions` snapshots the parent's resolved concrete route into the teammate's options and durable descriptor. Public Core evidence cannot distinguish an inherited concrete snapshot from an explicit concrete override. The plugin must not relabel that concrete child route as Auto or write a fabricated child selection.
143
+ In official DSH 0.2.0-rc.2, `TeamRoster.spawn` calls `ctx.subagents.startContinuable` without `request.agentOptions`. Core initializes the child from the parent's latest recorded request route, falling back to the parent's creation options before it has made a request, and records the resulting child options in its descriptor. This is creation-time inheritance, not a live link to the parent's selection. A recorded concrete route alone does not establish whether it came from an inherited selection or an explicit child override, and a resolved route does not prove the parent had no pending Auto intent. The plugin must not relabel a child route as Auto or write fabricated selection history.
144
144
 
145
- The implementation preserves native behavior:
145
+ With `followParentModel` off and no legacy `parentModelFollow` enrollment, the plugin preserves native child routing behavior:
146
146
 
147
147
  - a child with an explicit model override uses that model;
148
- - a child or Team teammate without an override inherits Core's resolved concrete route;
148
+ - a new child or Team mate without an override starts with Core's parent-route snapshot and fallback behavior;
149
+ - later parent changes do not retarget an existing child through the native continuation path;
149
150
  - the child UI shows the real model truthfully;
150
151
  - no plugin code claims independent child Auto classification.
151
152
 
152
- A later plugin-owned delegation entry may carry explicit Auto intent in its own public descriptor and let each child classify independently, but only after cold-resume and override precedence are proven without Core changes.
153
+ ## Requested parent-to-child selection inheritance
154
+
155
+ The desired behavior is for native subagents and Team mates to follow the master's **effective selection on each new child turn**, not only snapshot the route that was effective when the child was created:
156
+
157
+ - An explicit child model override takes precedence over inheritance.
158
+ - At child creation, an enrolled child starts from the parent's effective selection. On each later child turn, the follow-policy resolver reads its direct parent's current effective selection unless the child has an explicit override.
159
+ - If the parent is fixed to a model, the next child turn follows that provider/model. If the parent is Auto, the child retains Auto intent and independently resolves a model for its own turn; it must not be pinned to the parent's concrete model for that turn.
160
+ - A route is stable within a turn: changing the parent while a child turn is running does not hot-swap an in-flight request. The new parent selection applies when the child begins its next turn.
161
+ - The implementation must retain provenance that distinguishes inherited Auto, inherited fixed selection, and an explicit child override across child creation, message delivery, and cold resume. A concrete model ID alone cannot prove Auto intent.
162
+
163
+ ### Implementation sketch and boundary
164
+
165
+ This is a requested product direction, not current behavior. A native implementation would carry an explicit inheritance mode and parent/override provenance, then resolve the parent's current effective selection at the start of each new child turn. For Auto, the child must invoke its own per-turn Auto resolution against its own messages and capabilities. Explicit child selection remains authoritative. The resolver must use the live parent's selected/requested model state, not the global default, and must fail visibly when parent evidence is missing rather than guess from a stale concrete child route. The open [Core PR #95](https://github.com/cloga/deepseek-harness/pull/95) proposes creation-time route rules for new children; its design preserves existing children on later messages and does not establish per-turn parent-following or inherited Auto intent.
166
+
167
+ The plugin uses public request-selection middleware for supported native `spawn` children. The profile-wide switch explicitly authorizes overriding creation-time snapshots without inferring their original intent; legacy per-child bindings remain compatible. This is opt-in policy, not a change to native defaults. Actual request routes remain authoritative; native Team labels are not rewritten.
168
+
169
+ ### October 2 investigation: routing is possible; automatic enrollment is ambiguous
170
+
171
+ Tracking: [#229](https://github.com/cloga/dsh-github-copilot/issues/229).
172
+ The target remains unchanged official `0.2.0-rc.2`, commit
173
+ `639ed015397290b3745d163aafe02ffee4aa3f84`, not the proposed Core branch.
174
+
175
+ | Exact source | Finding |
176
+ | --- | --- |
177
+ | [child-agent.ts](https://github.com/deepseek-ai/deepseek-harness/blob/639ed015397290b3745d163aafe02ffee4aa3f84/packages/subagent/subagent/src/child-agent.ts) | `parentAgentOptionsForDelegation` reads the latest request header before creation options. `resolveChildAgentOptions` merges overrides and discards whether an equal route was explicit. |
178
+ | [continuation.ts](https://github.com/deepseek-ai/deepseek-harness/blob/639ed015397290b3745d163aafe02ffee4aa3f84/packages/subagent/subagent/src/continuation.ts) | Creation snapshots resolved options; cold resume reconstructs them from the descriptor. No next-turn parent-model recapture is performed here. |
179
+ | [descriptor.ts](https://github.com/deepseek-ai/deepseek-harness/blob/639ed015397290b3745d163aafe02ffee4aa3f84/packages/subagent/subagent/src/descriptor.ts) | Descriptor v3 stores resolved route/effort, not follow/override provenance, and rejects unknown fields. |
180
+ | [model-selection.ts](https://github.com/deepseek-ai/deepseek-harness/blob/639ed015397290b3745d163aafe02ffee4aa3f84/packages/core/agent/src/model-selection.ts) | Public `installModelSelection` couples scoped prompt assembly and request routing, clears inherited effort, and supports disposal. Its snapshot boundary is a step, so a follow policy must additionally freeze selection for a whole child turn. |
181
+ | [subagent index.ts](https://github.com/deepseek-ai/deepseek-harness/blob/639ed015397290b3745d163aafe02ffee4aa3f84/packages/subagent/subagent/src/index.ts) and [lifecycle.ts](https://github.com/deepseek-ai/deepseek-harness/blob/639ed015397290b3745d163aafe02ffee4aa3f84/packages/subagent/subagent/src/lifecycle.ts) | Public start/end notifications describe published runs; they are not a before-create interceptor exposing original override intent. The activation observer is package-private. |
182
+
183
+ An isolated Node 24 experiment executed the unchanged child-option resolver,
184
+ descriptor functions, and public selection middleware from that commit. Each
185
+ downloaded file's Git blob SHA was checked against the GitHub contents response
186
+ before execution. TypeScript was stripped with Node's compiler; depth, JSON
187
+ snapshot, message constructors, and the event context were synthetic dependencies.
188
+ Six assertions passed:
189
+
190
+ 1. Omitted overrides and an explicit provider/model equal to the parent produce identical resolved options and identical durable descriptors.
191
+ 2. Changing the parent's recorded route changes a newly resolved child, not the previously captured descriptor.
192
+ 3. A concrete parent request header takes precedence over Auto creation options.
193
+ 4. Before the first parent request, Auto survives the creation-options fallback.
194
+ 5. Adding an invented `followParent` descriptor field is rejected by the official reader.
195
+ 6. Public model-selection middleware applies a fixed route, forwards virtual Auto on subsequent assembly, clears inherited effort, and removes its listeners on disposal.
196
+
197
+ These are exact-function experiments, not full Core activation, real Team turns,
198
+ cold-resume integration, or model transport evidence. In particular, forwarding
199
+ an Auto ID does not by itself prove child-specific Auto resolution.
200
+
201
+ The first result is a counterexample to automatic override detection: two
202
+ different user intentions yield the same observable child state. Comparing
203
+ parent/child model IDs, inspecting only `Agent.options`, or treating a missing
204
+ child picker event as inheritance cannot implement the stated precedence for
205
+ every existing child. Request middleware does not recover the lost information.
206
+
207
+ ### One-switch policy and legacy per-child bindings
208
+
209
+ The ordinary UI is now one profile-wide **Follow parent model** switch in the
210
+ plugin configuration page. See [requirements, design and mockup](parent-model-follow.md).
211
+ It defaults to Off and does not ask users to manage child IDs. Explicitly
212
+ enabling this broad policy authorizes replacing creation-time snapshots;
213
+ child-owned manual selection events still win. The per-child binding mechanism
214
+ below remains for alpha.66 compatibility, not as the ordinary user workflow.
215
+
216
+ **Legacy opt-in bindings; preserved independently of the broad switch.**
217
+ Do not silently enroll all existing children or treat a new setting as proof of
218
+ their original creation intent. `github-copilot.parentModelFollow` defaults to
219
+ an empty array. The standard plugin configuration accepts explicit bindings:
220
+
221
+ ```json
222
+ {
223
+ "parentModelFollow": [
224
+ { "childSessionId": "<native-child-session-id>", "parentSessionId": "<direct-parent-session-id>" }
225
+ ]
226
+ }
227
+ ```
228
+
229
+ These are native DSH Session IDs, not role names, model IDs, or Copilot App
230
+ session handles. A binding authorizes replacement of the child's captured
231
+ creation route. No binding is added by installation or discovery. Existing
232
+ child-owned `model/selection` events take precedence, even for a same-model
233
+ selection; enrollment does not clear them. Remove the binding to return to
234
+ native routing at the next turn. Settings changes during an already captured
235
+ turn do not interrupt or change its route.
236
+
237
+ - A user explicitly enrolls a child Session through the native plugin configuration and its path-level settings writes, or leaves it under native selection. Bindings live only in this plugin's configuration. Do not add descriptor fields or new Session history events.
238
+ - A pure Host-only projection folds existing child-owned selection events, turn starts, and native descriptor evidence, excluding inherited seed events. A later explicit child selection suspends following from its next turn, including a same-model reselection. Once present, a child-owned selection is not cleared by toggling enrollment.
239
+ - Read the direct parent's pending selected intent first, then its proven effective route. Preserve the exact Auto preference. Do not borrow the global default, another Session, or a stale request header when a newer pending choice exists.
240
+ - Freeze one selection before the child's first prompt assembly in a new turn. Reuse it for every subsequent step/retry/compaction attempt in that turn. Integrate it with the existing per-Agent Auto resolver so Auto evaluates the child's admitted messages and capacity requirements, not the parent's chosen model.
241
+ - Reuse normal managed adapter admission for fixed-model availability and exclusions, and the existing validated candidate pool for Auto. Clear inherited reasoning effort while retaining output caps. Missing parent/selection evidence yields a named `COPILOT_PARENT_MODEL_*` diagnostic, never a guessed model or silent fallback.
242
+ - Restore policy from plugin-owned settings on cold activation and inspect only public projections. Do not call public `session.selectModel` for propagation: it also writes the future global default. Do not convert historical provenance or alter native permissions.
243
+ - Keep scope to verified native `spawn` children and managed Copilot parent routes. Dedicated historical role policies, fork-provider descriptors and externally managed providers are rejected when enrolled. Nested enrollment follows verified direct-parent links until an explicit selection or non-following parent supplies the intent; cycles and missing parents fail visibly.
244
+ - Verify native Team model labels separately: a roster label may describe a creation snapshot rather than the next request. Do not claim accurate live UI simply because request routing changes.
245
+
246
+ Release gates combine policy, Host/configuration and unchanged-Core regressions:
247
+ fixed A to B, fixed to Auto and Auto to fixed, every Auto preference, independent
248
+ sibling inputs, turn freezing, explicit child overrides, fork seed boundaries,
249
+ strict history reading/refolding, unavailable parents, normal model exclusions,
250
+ live binding changes and disposal. The native AgentLoop fixture reconstructs a
251
+ child from its own strict-reader-validated history and verifies the next turn;
252
+ it does not exercise disk-backed resume or the native Team orchestrator.
253
+ The native creation path cannot recover original equal-route override intent.
254
+ Legacy bindings authorize individual children; the new switch authorizes this
255
+ tradeoff once for the profile. Neither mechanism fabricates provenance or clears
256
+ child-owned selection events.
257
+
258
+ Local full validation is blocked: `pnpm exec vitest --version` triggered pnpm's
259
+ dependency reconciliation, which failed with HTTP 404 for
260
+ `https://packagefeedproxy.microsoft.io/npm/@deepseek-ai/dsh-llm/-/dsh-llm-0.2.0-rc.2.tgz`.
261
+ No registry restriction was bypassed. The isolated experiment above does not
262
+ replace the complete repository and exact-Core compatibility gates.
263
+
264
+ Implemented files are `src/parent-model-follow.ts`, `src/auto-model-host.ts`,
265
+ `src/config.ts` and `src/preview-route.ts`. Nine dependency-free policy tests
266
+ passed with `node --test tests/scripts/parent-model-follow.test.mjs`, and the
267
+ policy module passed a focused TypeScript check. An actual-plugin-source VM
268
+ experiment passed fixed/Auto turn freezing, config removal, explicit child
269
+ override, reinstallation/refolding and no-history-write assertions with synthetic
270
+ Context/LLM/token-estimator dependencies. Focused Vitest Host/config tests and
271
+ the real Session projection/AgentLoop fixtures run in the required Windows/Linux
272
+ CI matrix; the incomplete local dependency installation cannot run those gates.
273
+ The AgentLoop fixture uses the actual TokenMeter and a synthetic public adapter,
274
+ not a live model endpoint. Native Team end-to-end behavior, disk persistence,
275
+ Desktop activation and transport remain separate, unclaimed evidence layers.
153
276
 
154
277
  ## Public API implementation
155
278