dsh-github-copilot 0.4.0-alpha.32 → 0.4.0-alpha.34
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 +3 -3
- package/CHANGELOG.md +14 -0
- package/README.md +13 -11
- package/README.zh.md +13 -11
- package/deployment-baseline.json +8 -2
- package/docs/copilot-usage.md +8 -0
- package/docs/dual-model.md +29 -74
- package/docs/official-first-016-alpha2.md +7 -1
- package/lib/client.js +37 -719
- package/lib/client.js.map +1 -1
- package/lib/index.js +28 -160
- package/lib/types/client.d.ts +0 -1
- package/lib/types/dual-model-host.d.ts +1 -2
- package/package.json +1 -1
- package/lib/types/current-workspace.d.ts +0 -10
- package/lib/types/dual-model-card.d.ts +0 -53
- package/lib/types/dual-model-ui.d.ts +0 -5
package/AGENTS.md
CHANGED
|
@@ -41,13 +41,13 @@ This repository owns eleven narrow surfaces:
|
|
|
41
41
|
6. Provider-scoped tool-schema compatibility for Copilot payload behaviors; Core remains the tool and execution owner.
|
|
42
42
|
7. A bounded account-discovery route that supplies validated endpoint/capability metadata to the published native adapter, without maintaining model-ID routing rules or changing Core's catalog.
|
|
43
43
|
8. Optional, provider-scoped Chat presentation for completed empty reasoning disclosures; durable content and encrypted replay metadata remain Core-owned.
|
|
44
|
-
9.
|
|
44
|
+
9. Compatibility-only policy restoration and request recovery for existing dedicated planner/executor Sessions. Model roles UI, settings writes and new dedicated roots are retired (#158); never reintroduce them or migrate histories implicitly.
|
|
45
45
|
10. Managed-route estimated input/output admission, optional exact-request pressure signalling through official compaction recovery, and supported low summary effort only when no effort is already resolved. See [compaction budgets](./docs/copilot-compaction.md). Preserve truthful capacities, requested output caps, native errors/replay and transaction ownership; no hidden history trimming, chunking, new retry loop, competing compaction service or automatic model switch. Preventive guards do not claim recovery of an already oversized manual summary.
|
|
46
46
|
11. Optional account quota reads and a session-scoped composer usage control through public credentials, strict Remotes and additive slots. Keep account billing-cycle credits separate from context tokens and session cost. Missing, pooled, legacy and stale data must retain their real semantics; never infer credits from token estimates or account deltas. See [quota boundaries](./docs/copilot-usage.md).
|
|
47
47
|
|
|
48
|
-
##
|
|
48
|
+
## Retired model-role compatibility boundary (#158)
|
|
49
49
|
|
|
50
|
-
`src/dual-model-host.ts`, `dual-model-types.ts
|
|
50
|
+
`src/dual-model-host.ts`, `dual-model-types.ts` and `dual-model-remote.ts` retain compatibility for existing histories; see `docs/dual-model.md`. Do not restore the removed Client card or either Settings entry. `view` reports read-only retirement without discovery; `save` rejects; `create` can only recover a matching already-created request, never create a new root. The three strict Remote wire contracts and eight authorization/migration descriptors retain their identities. Restore existing captured policy through the namespaced projection without deleting settings, converting history or changing routes/defaults. Unknown recovery evidence remains uncertain, not permission to create with another UUID. Existing dedicated tool restrictions remain workflow controls, not a sandbox against shell code. Ordinary Session/subagent behavior stays Core-owned; the pending native parent-model rules are separate work, not a new dependency or a shipped capability of this plugin.
|
|
51
51
|
|
|
52
52
|
Alpha.25 admits native `subagent/descriptor` v3, already v3 in the retained rc.1 baseline; the old v1 assumption was a plugin/test bug. Projection cache `stateVersion: 2` forces refolding, not history conversion. Unknown/v1/v2 or invalid child descriptors fail closed unmodified; review the original child's work and explicitly create a new child if needed, never relabel or fabricate a descriptor. Strict Remote codecs provide alpha.2 `create()` factories and retain the legacy `schema` bridge to the same strict parser, with no `src-json` downgrade.
|
|
53
53
|
|
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,19 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 0.4.0-alpha.34 (prepared, PR-only)
|
|
4
|
+
|
|
5
|
+
- Retire the Model roles / planner-executor settings, legacy Settings fallback, and dedicated-session creation UI (#158); ordinary Sessions and Core-owned subagents remain the intended workflow.
|
|
6
|
+
- Remove obsolete role Client components and browser fixtures, with negative registration and adjacent account/search/usage regressions.
|
|
7
|
+
- Keep existing dedicated-session policy replay and strict Remote contracts for compatibility; reject role configuration writes and new dedicated roots explicitly, retaining evidence-only recovery of matching existing requests.
|
|
8
|
+
- Do not migrate or delete saved settings, histories, credentials, model choices or global defaults. Native parent-to-child model rules remain separately pending Core work, not a capability supplied by this retirement.
|
|
9
|
+
- Version metadata prepares the required PR release gate only; merge, publication, installation and activation are not part of this PR-only request.
|
|
10
|
+
|
|
11
|
+
## 0.4.0-alpha.33 (prepared)
|
|
12
|
+
|
|
13
|
+
- Fix the account-usage composer component to call the public `useSession(selector)` hook with a selector instead of assuming a no-argument snapshot API (#156).
|
|
14
|
+
- Preserve native Session ownership and select only the open/current/not-removed predicate; no Core patch, credential change, network-policy change or automatic restart is required.
|
|
15
|
+
- Add positive canonical/managed Copilot rendering and required-selector lifecycle regressions. Earlier signed-out absence tests do not establish that the eligible-session control can render.
|
|
16
|
+
|
|
3
17
|
## 0.4.0-alpha.32 (prepared)
|
|
4
18
|
|
|
5
19
|
- Add an optional, Copilot-session-scoped composer usage control without replacing the native Context meter or changing other providers (#153).
|
package/README.md
CHANGED
|
@@ -61,6 +61,8 @@ Source markers, local rc.1-backed focused tests and fifteen scoped exact-source
|
|
|
61
61
|
|
|
62
62
|
## Copilot usage beside the composer
|
|
63
63
|
|
|
64
|
+
Alpha.33 corrects alpha.32's missing selector argument to the public Session hook, which could retire the registered usage entry after a render failure. Positive eligible-Session rendering must be verified separately from installed-version receipts or signed-out absence. The fix is plugin-only; no Core patch or automatic restart is included.
|
|
65
|
+
|
|
64
66
|
For a Session using `github-copilot` or `github-copilot-preview`, an optional **Credits** control shows the signed-in account's reported billing-cycle usage and remaining allocation. It uses the public composer dock, leaves the native Context meter unchanged, and disappears for other providers. Open it for budget, reset time, freshness and refresh details. Unsupported Client slots disable only this optional control.
|
|
65
67
|
|
|
66
68
|
Numbers are not token estimates: legacy accounts show **Premium requests**, a shared organization pool may provide used credits without any individual remaining balance, and absent data is **Unavailable**, never zero or unlimited. Failed refreshes may retain explicitly **last-known** same-account values; authentication/account invalidation removes them. **This session** remains unavailable because the supported native adapter does not expose complete provider-reported credit accounting through the public plugin contract. It is not inferred from account deltas.
|
|
@@ -69,7 +71,7 @@ The Host reads GitHub's internal quota endpoint using the existing canonical OAu
|
|
|
69
71
|
|
|
70
72
|
## Install and sign in
|
|
71
73
|
|
|
72
|
-
The commands below target the package version `0.4.0-alpha.
|
|
74
|
+
The commands below target the package version `0.4.0-alpha.34`. 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):
|
|
73
75
|
|
|
74
76
|
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):
|
|
75
77
|
|
|
@@ -82,7 +84,7 @@ Include any launcher patch files with repeated `--patch /absolute/file` argument
|
|
|
82
84
|
For approved online installation, the supported CLI command is:
|
|
83
85
|
|
|
84
86
|
```sh
|
|
85
|
-
dsh plugin --profile web add https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.0-alpha.
|
|
87
|
+
dsh plugin --profile web add https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.0-alpha.34/dsh-github-copilot-0.4.0-alpha.34.tgz
|
|
86
88
|
```
|
|
87
89
|
|
|
88
90
|
If registry access is blocked or unavailable, do not retry it through another network. Desktop-managed profiles may instead use the [controlled offline CLI procedure](./docs/npm-distribution.md#controlled-offline-cli-maintenance), with an approved, checksum-verified local Release and existing dependency cache (`--offline --ignore-scripts`). All preflight and approval requirements still apply.
|
|
@@ -147,7 +149,7 @@ Agents should treat the browser authorization as a human handoff, not as a token
|
|
|
147
149
|
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.
|
|
148
150
|
6. Use **Sign out** only when the user explicitly asks to disconnect the account. It deletes the Copilot credential record but preserves route settings.
|
|
149
151
|
|
|
150
|
-
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. The native Desktop package manager is preferred when permitted registry access is available; after npm publication is verified it accepts `dsh-github-copilot@0.4.0-alpha.
|
|
152
|
+
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. The native Desktop package manager is preferred when permitted registry access is available; after npm publication is verified it accepts `dsh-github-copilot@0.4.0-alpha.34`, not a URL or file. Desktop-managed profiles also support explicitly approved [controlled offline CLI maintenance](./docs/npm-distribution.md#controlled-offline-cli-maintenance) with a verified local Release and `--offline --ignore-scripts`. 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. Offline installation is not proof that npm networking/publication was repaired. See [distribution and publication requirements](./docs/npm-distribution.md).
|
|
151
153
|
|
|
152
154
|
No `copilot2api` process, external gateway, placeholder API key, pasted GitHub token, or separate `dsh-web-search-provider` installation is required.
|
|
153
155
|
|
|
@@ -162,15 +164,15 @@ No `copilot2api` process, external gateway, placeholder API key, pasted GitHub t
|
|
|
162
164
|
|
|
163
165
|
DSH Core continues to own model selection, sandboxing, tools, attachments, and other providers. `@deepseek-ai/dsh-llm-pi-ai` owns the Copilot adapter, catalog, OAuth method and grant format, token exchange, refresh, and normal model transport. Credentials remain Host-only.
|
|
164
166
|
|
|
165
|
-
##
|
|
167
|
+
## Retired planner / executor experience
|
|
166
168
|
|
|
167
|
-
|
|
169
|
+
The `0.4.0-alpha.34` candidate removes **Model roles**, its legacy **Copilot · Model roles** fallback, the planning/execution selectors and the dedicated-session creation button (#158). Use ordinary Sessions and Core-owned model selection/subagents; this plugin adds no replacement role UI or automatic model mapping.
|
|
168
170
|
|
|
169
|
-
|
|
171
|
+
Parent-model → subagent-model rules and their native settings UI are separate, still-pending work in [Core PR #95](https://github.com/cloga/deepseek-harness/pull/95). Removing this plugin UI does not make those rules available on older or currently installed Core versions, and does not depend on that PR shipping.
|
|
170
172
|
|
|
171
|
-
|
|
173
|
+
Existing dedicated histories and captured policies remain supported through the retained compatibility runtime, without conversion or model substitution. Saved legacy settings are not deleted or migrated. Legacy Remote clients receive `DUAL_MODEL_RETIRED` for settings writes and new roots; recovery of an already-created matching request remains available. See [retirement and compatibility boundaries](./docs/dual-model.md). Publication and runtime activation are separate from this source change.
|
|
172
174
|
|
|
173
|
-
|
|
175
|
+
The plugin's Web search-provider dropdowns use paired application-theme surface/text colors, including unavailable options, so dark mode does not leave pale labels on a white popup. Hosts without those theme tokens use readable system-color fallbacks. Appearance changes do not save or replace search selections; Core owns its model picker.
|
|
174
176
|
|
|
175
177
|
## Shared account, independent sessions (V3)
|
|
176
178
|
|
|
@@ -408,8 +410,8 @@ Report the published Release URL, version, tag/commit and verified asset SHA-256
|
|
|
408
410
|
`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.
|
|
409
411
|
|
|
410
412
|
```sh
|
|
411
|
-
curl -LO https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.0-alpha.
|
|
412
|
-
curl -LO https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.0-alpha.
|
|
413
|
+
curl -LO https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.0-alpha.34/dsh-github-copilot-0.4.0-alpha.34.tgz
|
|
414
|
+
curl -LO https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.0-alpha.34/SHA256SUMS
|
|
413
415
|
sha256sum --check SHA256SUMS
|
|
414
416
|
```
|
|
415
417
|
|
|
@@ -417,7 +419,7 @@ PowerShell can verify the same two downloaded files with:
|
|
|
417
419
|
|
|
418
420
|
```powershell
|
|
419
421
|
$expected = (Get-Content .\SHA256SUMS).Split()[0]
|
|
420
|
-
$actual = (Get-FileHash .\dsh-github-copilot-0.4.0-alpha.
|
|
422
|
+
$actual = (Get-FileHash .\dsh-github-copilot-0.4.0-alpha.34.tgz -Algorithm SHA256).Hash.ToLowerInvariant()
|
|
421
423
|
if ($actual -cne $expected) { throw 'Release checksum mismatch' }
|
|
422
424
|
```
|
|
423
425
|
|
package/README.zh.md
CHANGED
|
@@ -9,7 +9,7 @@
|
|
|
9
9
|
|
|
10
10
|
一个聚焦 GitHub Copilot 登录、通用账号模型发现、Copilot 专用 Tool 兼容与供应方托管搜索的 DSH companion。插件根据供应方返回的端点和能力元数据组装模型,复用公开的 `@deepseek-ai/dsh-llm-pi-ai` adapter 与 pi-ai SDK,不另写一套通用传输/序列化器,也不维护需要逐个添加新模型 ID 的静态目录。
|
|
11
11
|
|
|
12
|
-
> 下文自动维护账号模型元数据与 provider 集成控件描述目标版本 `0.4.0-alpha.
|
|
12
|
+
> 下文自动维护账号模型元数据与 provider 集成控件描述目标版本 `0.4.0-alpha.34`;这不代表已有的两条真实路由被合并或移除。版本化 URL 不表示 Release 已发布或本机已加载;仅在该 Release 与校验和可用后使用安装命令。源码、发布制品、已安装版本和实际加载运行时需分别确认,本地升级和中断会话的重启仍需用户批准。
|
|
13
13
|
|
|
14
14
|
Alpha.24 修复 Web search 卡片缺少精确 Remote 依赖声明的问题。卡片仍位于 **Settings → Models**(`settings.models.footer`,list/root),旧 Core 回退到独立 Web search section,而非 General。搜索子 Fiber 独立等待 routing namespace,不影响账号控件和既有搜索安全检查;实际打包 Desktop 验收仍是独立关卡。
|
|
15
15
|
|
|
@@ -63,6 +63,8 @@ Candidate 追加第九个精确目标:`dsh-v0.1.6-alpha.2`,commit `ddefc45fb
|
|
|
63
63
|
|
|
64
64
|
## 输入框附近的 Copilot 用量
|
|
65
65
|
|
|
66
|
+
Alpha.33 修正 alpha.32 调用公开 Session hook 时遗漏 selector 参数的问题;该错误可能导致已注册的用量入口在渲染失败后被撤下。必须单独验证符合条件会话中的正向显示,不能用已安装版本收据或登出时不显示代替。本修复只修改插件,不包含 Core 补丁或自动重启。
|
|
67
|
+
|
|
66
68
|
当前会话使用 `github-copilot` 或 `github-copilot-preview` 时,可选的 **Credits / 额度** 控件显示已登录账号本计费周期的已用量及服务端明确提供的剩余额度。控件通过公开 composer dock 增补,不修改原生 Context meter;切换其他 provider 后隐藏。展开可查看预算、重置时间、数据新鲜度并刷新。旧 Client 缺少公开插槽时只停用这一可选功能。
|
|
67
69
|
|
|
68
70
|
数字不是 token 费用估算:旧计费账号显示 **Premium requests / 高级请求**;企业共享池可能只有已用 credits,没有个人剩余量。缺失数据显示不可用,不伪装成零或无限。刷新失败可保留明确标注的同账号历史快照;认证失效或账号变化会清除快照。**当前会话**消耗暂时显示不可用,因为受支持的原生 adapter 没有通过公开插件契约提供完整的 credit 计量;不会用账号余额差值推算。
|
|
@@ -84,7 +86,7 @@ node package/scripts/check-search-composition.mjs --profile-dir /absolute/profil
|
|
|
84
86
|
获准且网络可用时,可通过受支持的 CLI 命令安装:
|
|
85
87
|
|
|
86
88
|
```sh
|
|
87
|
-
dsh plugin --profile web add https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.0-alpha.
|
|
89
|
+
dsh plugin --profile web add https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.0-alpha.34/dsh-github-copilot-0.4.0-alpha.34.tgz
|
|
88
90
|
```
|
|
89
91
|
|
|
90
92
|
若 registry 被公司封禁或不可用,不要更换网络绕行。Desktop 管理的 profile 可以改用[受控离线 CLI 流程](./docs/npm-distribution.md#controlled-offline-cli-maintenance):使用来源获准、校验通过的本地 Release 和已有依赖缓存(`--offline --ignore-scripts`)。预检、备份和授权要求仍然适用。
|
|
@@ -149,7 +151,7 @@ Agent 应把浏览器授权视为需要用户完成的 handoff,而不是自行
|
|
|
149
151
|
5. 确认 **Signed in** 并检查自动发现结果,再请用户选择模型。已登录时打开 Models 会自动确保缺失/过期元数据,新鲜 ready 缓存不发请求。错误可使用 **Retry**,有意强制更新时使用 **Manage → Refresh models**,不作为常规设置步骤。状态读取本身不发现;登录、元数据与真实调用成功是独立证据。
|
|
150
152
|
6. 只有用户明确要求断开账号时才使用 **Sign out**;它会删除 Copilot credential record,但保留 route settings。
|
|
151
153
|
|
|
152
|
-
每个新版本默认同时分发到 GitHub Releases 和 npm,两个渠道使用同一份已验证 tarball。应固定版本并核对所用渠道的证据:Release 的 `SHA256SUMS`;从 npm 安装时另核对 `dist.integrity`。在获准且可用的 registry 网络环境中,优先使用原生 Desktop 包管理器;确认 npm 发布后,它接受 `dsh-github-copilot@0.4.0-alpha.
|
|
154
|
+
每个新版本默认同时分发到 GitHub Releases 和 npm,两个渠道使用同一份已验证 tarball。应固定版本并核对所用渠道的证据:Release 的 `SHA256SUMS`;从 npm 安装时另核对 `dist.integrity`。在获准且可用的 registry 网络环境中,优先使用原生 Desktop 包管理器;确认 npm 发布后,它接受 `dsh-github-copilot@0.4.0-alpha.34`,不是 URL 或本地文件。Desktop 管理的 profile 也允许经明确授权的[受控离线 CLI 维护](./docs/npm-distribution.md#controlled-offline-cli-maintenance):使用已验证的本地 Release 和 `--offline --ignore-scripts`,执行必需的组合预检、私密元数据备份、单写入者控制及安装后差异核验。缓存不足或出现权限拒绝时停止,不绕过公司 registry 封禁,不关闭 TLS 校验;重启仍需单独授权。离线安装成功不表示 npm 联网或发布问题已修好。[双渠道发布与 OIDC 要求](./docs/npm-distribution.md)保持不变。
|
|
153
155
|
|
|
154
156
|
不需要运行 `copilot2api`,不需要外部 gateway、placeholder API key、原始 GitHub token 或单独安装 `dsh-web-search-provider`。
|
|
155
157
|
|
|
@@ -166,15 +168,15 @@ Agent 应把浏览器授权视为需要用户完成的 handoff,而不是自行
|
|
|
166
168
|
|
|
167
169
|
DSH Core 继续负责模型选择、sandbox、工具、附件与其它 provider。原生 `github-copilot` 的模型目录和 profile 仍属于 Core/用户;插件不拿自己的 pi 依赖副本改写它们。托管账号路由复用公开 adapter 类、SDK 序列化、OAuth method/grant format、token exchange 和 refresh。普通模型请求使用 SDK `streamSimple`,支持供应方明确公布的 Responses、Chat Completions 和 Anthropic Messages 三种协议。跨 SDK 的高级协议专用 `stream` 接口会明确报 `COPILOT_MANAGED_ADVANCED_STREAM_UNSUPPORTED`,不假装不兼容的底层客户端可互换;这不等于普通流式聊天被禁用。
|
|
168
170
|
|
|
169
|
-
##
|
|
171
|
+
## 已退役的规划/执行专用体验
|
|
170
172
|
|
|
171
|
-
|
|
173
|
+
`0.4.0-alpha.34` candidate 移除 **模型分工(Model roles)**、旧版 **Copilot · Model roles** 设置入口、规划/执行模型选择器和新建专用会话按钮(#158)。今后使用普通 Session 与 Core 自己的模型选择/subagent;插件不新增替代角色页面,也不自动映射模型。
|
|
172
174
|
|
|
173
|
-
|
|
175
|
+
父模型 → subagent 模型规则及其原生设置 UI 属于另一个仍待交付的 [Core PR #95](https://github.com/cloga/deepseek-harness/pull/95)。移除本插件 UI 不代表旧版或当前安装的 Core 已具有规则功能,也不依赖该 PR 先发布。
|
|
174
176
|
|
|
175
|
-
|
|
177
|
+
已有专用会话的历史和创建时捕获的策略继续由兼容运行时支持,不转换历史、不自动换模型。旧设置不删除、不迁移。旧 Remote 客户端尝试保存设置或创建新专用根会话会收到 `DUAL_MODEL_RETIRED`;已经创建且请求身份完全匹配的会话仍可恢复查询。详见[退役与兼容边界](./docs/dual-model.md)。源码修改、发布和当前运行时生效是不同阶段。
|
|
176
178
|
|
|
177
|
-
|
|
179
|
+
插件的 Web 搜索 Provider 下拉控件及不可用选项使用成对的应用主题背景/文字颜色,避免深色模式弹出白底浅字列表;缺少主题 token 的旧环境采用可读的系统颜色回退。配色变化不会保存或替换搜索选择;模型选择器仍由 Core 负责。
|
|
178
180
|
|
|
179
181
|
## 全局账号,多模型与独立会话(V3)
|
|
180
182
|
|
|
@@ -419,8 +421,8 @@ node scripts/agent.mjs attribution "DeepSeek Harness (DSH)"
|
|
|
419
421
|
`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 要求包已存在,不能代替首次建包。不会批量补发历史版本。
|
|
420
422
|
|
|
421
423
|
```sh
|
|
422
|
-
curl -LO https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.0-alpha.
|
|
423
|
-
curl -LO https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.0-alpha.
|
|
424
|
+
curl -LO https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.0-alpha.34/dsh-github-copilot-0.4.0-alpha.34.tgz
|
|
425
|
+
curl -LO https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.0-alpha.34/SHA256SUMS
|
|
424
426
|
sha256sum --check SHA256SUMS
|
|
425
427
|
```
|
|
426
428
|
|
|
@@ -428,7 +430,7 @@ PowerShell 可以对已下载的同一组文件执行:
|
|
|
428
430
|
|
|
429
431
|
```powershell
|
|
430
432
|
$expected = (Get-Content .\SHA256SUMS).Split()[0]
|
|
431
|
-
$actual = (Get-FileHash .\dsh-github-copilot-0.4.0-alpha.
|
|
433
|
+
$actual = (Get-FileHash .\dsh-github-copilot-0.4.0-alpha.34.tgz -Algorithm SHA256).Hash.ToLowerInvariant()
|
|
432
434
|
if ($actual -cne $expected) { throw 'Release checksum mismatch' }
|
|
433
435
|
```
|
|
434
436
|
|
package/deployment-baseline.json
CHANGED
|
@@ -8,7 +8,7 @@
|
|
|
8
8
|
},
|
|
9
9
|
"package": {
|
|
10
10
|
"name": "dsh-github-copilot",
|
|
11
|
-
"version": "0.4.0-alpha.
|
|
11
|
+
"version": "0.4.0-alpha.34"
|
|
12
12
|
},
|
|
13
13
|
"evidence": {
|
|
14
14
|
"kind": "source-and-synthetic-test-inventory",
|
|
@@ -227,12 +227,15 @@
|
|
|
227
227
|
"sourceMarkers": [
|
|
228
228
|
{"file": "src/index.ts", "marker": "ctx.plugin(GitHubCopilotUsageController)"},
|
|
229
229
|
{"file": "src/client.ts", "marker": "registerCopilotUsageUi"},
|
|
230
|
+
{"file": "src/copilot-usage-ui.ts", "marker": "runtime.useSession(session =>"},
|
|
230
231
|
{"file": "src/remote.ts", "marker": "...copilotUsageRemote.descriptors"},
|
|
231
232
|
{"file": "docs/copilot-usage.md", "marker": "Percentage-only data must not create falsely precise absolute amounts"}
|
|
232
233
|
],
|
|
233
234
|
"tests": [
|
|
234
235
|
{"file": "tests/copilot-usage-normalize.spec.ts", "name": "never invents precise amounts from a rounded percentage"},
|
|
235
236
|
{"file": "tests/copilot-usage-ui.spec.ts", "name": "uses real Cordis Remote tracing and reversible public SlotRegistry registration"},
|
|
237
|
+
{"file": "tests/copilot-usage-ui.spec.ts", "name": "renders the usage trigger through a required Session selector for %s"},
|
|
238
|
+
{"file": "tests/fixtures/copilot-usage-selector-core.fixture.ts", "name": "renders and reacts to the owning Session on %s"},
|
|
236
239
|
{"file": "tests/scripts/copilot-usage-gateway.test.mjs", "name": "quota Remote reaches the actual Host gateway without startup or signed-out network requests"},
|
|
237
240
|
{"file": "tests/client-bundle.spec.ts", "name": "mounts strict Host result codecs through the published rc.1 client carrier"},
|
|
238
241
|
{"file": "tests/fixtures/remote-core.fixture.ts", "name": "mounts authorization, role and search-catalog Remotes on the exact target Client gateway"}
|
|
@@ -873,7 +876,10 @@
|
|
|
873
876
|
{"file": "tests/client.spec.ts", "name": "explains the initial model list without inferring a completed discovery from sign-in"},
|
|
874
877
|
{"file": "tests/client.spec.ts", "name": "restores exactly one account fallback when a footer declaration is withdrawn"},
|
|
875
878
|
{"file": "tests/client.spec.ts", "name": "transfers a pending sign-in to an arriving row and back without stale actions or a second poll owner"},
|
|
876
|
-
{"file": "tests/client.spec.ts", "name": "keeps one owner across duplicate row instances and footer/settings competition"}
|
|
879
|
+
{"file": "tests/client.spec.ts", "name": "keeps one owner across duplicate row instances and footer/settings competition"},
|
|
880
|
+
{"file": "tests/client-no-model-roles.spec.ts", "name": "does not export the obsolete role card while preserving search and usage components"},
|
|
881
|
+
{"file": "tests/client-no-model-roles.spec.ts", "name": "never registers role entrypoints (footer=$footer, legacyRemote=$legacyRemote)"},
|
|
882
|
+
{"file": "tests/client-no-model-roles.spec.ts", "name": "does not resurrect a role entry when a retained legacy Remote arrives later"}
|
|
877
883
|
]
|
|
878
884
|
},
|
|
879
885
|
{
|
package/docs/copilot-usage.md
CHANGED
|
@@ -42,6 +42,14 @@ The internal client observes per-turn `copilot_usage.total_nano_aiu`, but existe
|
|
|
42
42
|
|
|
43
43
|
Synthetic tests cover parsing, lifecycle, failure states, strict transport and UI. They do not establish production quota permissions, billing latency, live OAuth/model transport, installed Desktop bytes or loaded plugin state. No real account calls are made merely to generate test evidence.
|
|
44
44
|
|
|
45
|
+
## Session selector correction (alpha.33)
|
|
46
|
+
|
|
47
|
+
Alpha.32 called `useSession()` without the selector required by the public Core hook. A registration can therefore exist while the Slot renderer has retired its crashed entry; installed-version receipts and signed-out absence tests are not proof that the control renders in an eligible Session.
|
|
48
|
+
|
|
49
|
+
The correction consumes the existing `useSession(selector)` contract and selects only a boolean for the current, open, non-removed Session. It does not introduce a compatibility shim, copy Session data, patch Core, substitute model selection, or alter quota requests. The exact official alpha.1/alpha.2 contract is `SnapshotSelectorHook<T>` in `packages/client/store/src/contract.ts`, with the `bindSnapshotSelector` implementation in `packages/client/ui-renderer/src/client/bind.ts`. Model projection remains the public `useProjection('modelSelection')` reader, whose key-only overload is supported.
|
|
50
|
+
|
|
51
|
+
Validation must include positive rendering with actual selector-hook behavior for both canonical and managed Copilot routes, reactive provider/Session changes and disposal. A null/hidden signed-out surface alone is insufficient. Synthetic quota results prove rendering and lifecycle only, not live account permissions or balances. Current-runtime activation must be checked separately after an explicitly authorized upgrade; reloading alpha.32 does not fix its source call.
|
|
52
|
+
|
|
45
53
|
## Official-first retirement
|
|
46
54
|
|
|
47
55
|
Retain this bounded companion feature only while native DSH lacks equivalent public account-usage presentation for the required scope. Migrate to native functionality once equivalent data semantics, account invalidation, session attribution, accessible presentation and supported-version acceptance are verified. Do not require a Core patch or add a parallel model transport to complete this integration.
|
package/docs/dual-model.md
CHANGED
|
@@ -1,97 +1,52 @@
|
|
|
1
|
-
# Copilot model roles
|
|
1
|
+
# Retired Copilot model roles
|
|
2
2
|
|
|
3
|
-
Issue [#127](https://github.com/cloga/dsh-github-copilot/issues/127). This is
|
|
3
|
+
Issue [#158](https://github.com/cloga/dsh-github-copilot/issues/158) retires the planner/executor experience introduced in [#127](https://github.com/cloga/dsh-github-copilot/issues/127). This is a plugin-only removal, not a Core upgrade or a claim that the running Desktop has changed.
|
|
4
4
|
|
|
5
|
-
##
|
|
5
|
+
## Ordinary Sessions instead of dedicated roles
|
|
6
6
|
|
|
7
|
-
|
|
8
|
-
2. Enable dual-model sessions and select a **Planning model** and an **Execution model** from this account's available Copilot models. Model names and IDs come from the existing account-discovery service, never an implementation table.
|
|
9
|
-
3. Save the profile-global configuration; no workspace is required. The revision-checked save affects only this plugin's `github-copilot-dual-model` namespace, not a per-workspace setting. No global model default, credential, other provider or existing session is changed.
|
|
10
|
-
4. Check the read-only current workspace under **New dedicated session**, then choose **Create session with this configuration**. There is no workspace dropdown. If no current workspace can be established, open one in the application first; the plugin never guesses the first or most recent workspace. Return to the application if the host's settings surface remains open, then enter the task in the new conversation.
|
|
11
|
-
5. The planner clarifies the task, reads evidence and performs acceptance review. `copilot_execute` creates a native continuable execution child using the captured execution route. Its result shows the actual delegated provider/model and child ID; acceptance of the prompt is not completion. The original `send_message`, `list_agents` and `interrupt_agent` capabilities continue the child and expose its status.
|
|
7
|
+
The alpha.34 candidate removes the Models-page **Model roles** card, the older **Copilot · Model roles** Settings fallback, both role selectors and the dedicated-session creation action. There is no replacement planner/executor page. Account sign-in, model discovery, ordinary model selection, search routing and the usage control retain their existing owners.
|
|
12
8
|
|
|
13
|
-
|
|
9
|
+
Use ordinary Sessions and native subagents. Automatic parent-model → child-model rules and their native Subagent settings editor are separate work in [Core PR #95](https://github.com/cloga/deepseek-harness/pull/95), not yet delivered by this plugin. The removal does not require that PR to merge, does not enable its feature on an older Core, and does not alter native model-selection permission settings.
|
|
14
10
|
|
|
15
|
-
|
|
11
|
+
## Existing histories remain compatible
|
|
16
12
|
|
|
17
|
-
|
|
13
|
+
- Saved `github-copilot-dual-model` configuration is left intact but no longer writable through the legacy role Remote. No settings migration or namespace deletion runs on mount.
|
|
14
|
+
- Existing dedicated roots and children retain their captured policy, Session history and model routes. Ordinary Sessions are never enrolled. No conversion, replay of work, automatic replacement or silent model substitution occurs.
|
|
15
|
+
- The retained Host projection, route guards and scoped tools exist only for these historical policies. A historical planner can still continue its workflow through `copilot_execute`; that is compatibility for an existing root, not an entry point for creating a new dedicated root.
|
|
16
|
+
- Policy restrictions are workflow controls, not a malicious-code sandbox. Core sandbox/approval ownership remains unchanged. The plugin must remain mounted to enforce those policies; uninstalling it is not a supported migration to ordinary Sessions.
|
|
17
|
+
- Do not change a dedicated role with the ordinary picker: a mismatched route remains `DUAL_MODEL_SELECTION_LOCKED`. Start an ordinary Session for new work rather than creating another dedicated root or editing history to remove its policy.
|
|
18
18
|
|
|
19
|
-
|
|
20
|
-
- Only sessions created through this entry receive the role policy. Saving different defaults, disabling new dual-model sessions, or editing unrelated sessions does not rewrite an existing role policy. Forked histories are not silently enrolled as new dedicated roots.
|
|
21
|
-
- Planner write/shell and alternative delegation tools are unavailable in the dedicated flow. Executors receive an explicit implementation-tool allowlist and cannot recursively delegate through the normal agent tools. These are model-workflow controls, **not a malicious-code sandbox**: an authorized shell can itself execute programs. Core sandbox and approval enforcement remain the authority.
|
|
22
|
-
- No fallback model is selected on account/model failure. The existing native adapter continues to validate account proof and real model requests; merely seeing an ID or passing metadata validation is not proof of a successful model call.
|
|
23
|
-
- The new root carries a session-local initial model selection, not a global-default write. Do not use the ordinary model picker to change a dedicated role: a different effective route is rejected with `DUAL_MODEL_SELECTION_LOCKED`. Create a new dedicated session for another role pair. Core's ordinary picker remains user/Core-owned and can itself save a future global default; this plugin does not intercept or promise to prevent that separate user action.
|
|
24
|
-
- Role declarations are captured in an immutable, namespaced, ignorable seed event before publication, and replayed by a plugin-owned projection. The policy includes its exact root ID so an inherited fork seed cannot impersonate a new role owner. The ordinary model-selection event uses Core's published per-session format.
|
|
25
|
-
- The plugin must remain mounted to enforce and resume the dedicated policy. Removal/update disposes plugin-owned overlays and stops their active work; an ignorable extension is not an enduring security barrier after uninstall. Unsupported public service contracts disable this feature visibly without turning normal account sign-in into a hard dependency failure.
|
|
19
|
+
## Legacy Remotes and uncertain requests
|
|
26
20
|
|
|
27
|
-
|
|
21
|
+
The three strict legacy descriptors retain their identities and wire shapes so stale clients fail explicitly rather than invoking a missing or different endpoint:
|
|
28
22
|
|
|
29
|
-
|
|
23
|
+
- `view()` reports `supported: false`, `writable: false`, and `DUAL_MODEL_RETIRED`, with retained configuration/revision and empty model/workspace choices. It performs no account discovery.
|
|
24
|
+
- `save()` validates its input and rejects with `DUAL_MODEL_RETIRED`; it does not write settings.
|
|
25
|
+
- `create()` validates its input and is recovery-only. The original request UUID, workspace and revision must match an already-created root's durable policy. A new request cannot create a root. Conflicting or uncertain evidence is not treated as absence or permission to retry with a new UUID.
|
|
30
26
|
|
|
31
|
-
|
|
27
|
+
An already-created matching request can recover its original Session identity and complete the existing workspace attachment. Recovery is not a new root, settings write or automatic browser replay. Inspect the Session list for historical work; no role UI is retained solely to initiate fresh requests.
|
|
32
28
|
|
|
33
29
|
## Alpha.25 descriptor and Remote compatibility
|
|
34
30
|
|
|
35
|
-
The
|
|
31
|
+
The retained policy projection admits native `subagent/descriptor` **v3**, already v3 in rc.1. The earlier v1 expectation was a plugin bug, not an upstream history-format migration. Projection `stateVersion: 2` forces refolding, not conversion. Unknown/v1/v2, malformed or conflicting descriptors remain fail-closed and unmodified. Never relabel descriptors or fabricate policy provenance.
|
|
36
32
|
|
|
37
|
-
|
|
33
|
+
Strict Remote `create()` codec factories and the legacy `schema` bridge use the same parser; this is not a `src-json` downgrade. Account authorization, migration, search and usage contracts are unchanged. The [official-first decision record](./official-first-016-alpha2.md) separates historical compatibility from the now-retired product requirement. The old role screenshots/provenance retained in `docs/images` are historical artifacts, not a current settings guide.
|
|
38
34
|
|
|
39
|
-
|
|
35
|
+
## Verification boundaries
|
|
40
36
|
|
|
41
|
-
|
|
37
|
+
- Client registration regressions must prove the role dependency and both slot entries are absent while account/search/usage registrations and cleanup remain.
|
|
38
|
+
- Host and real Gateway regressions cover retired read-only view, rejected saves/new roots, strict input validation and original-request recovery. Historical policy fixtures retain restoration, native-child admission and route/tool controls.
|
|
39
|
+
- Package smoke must reject an exported `DualModelCard` while retaining strict compatibility Remotes.
|
|
40
|
+
- Required Windows/Linux and exact-Core compatibility CI remains mandatory. Source assertions, isolated mocks or a successful build alone do not prove installed Desktop behavior or a real model call.
|
|
42
41
|
|
|
43
|
-
|
|
44
|
-
|
|
45
|
-
**Could not load model roles** is a failed Remote load, not an instruction to change global model defaults. A `githubCopilotDualModel/view` HTTP 404 means the Host did not expose the endpoint; Client descriptors alone cannot register Host methods. The Host uses the public `TypertRemoteService` binding and marks only `view`, `save` and `create` with `@Remote`. A source fix does not change an already running installation.
|
|
46
|
-
|
|
47
|
-
A successful view can still report `DUAL_MODEL_UNSUPPORTED` when optional public capabilities are missing. An off configuration alone does not disable the model selectors. Read-only settings, a missing revision, pending operations, unavailable models and unavailable workspaces retain their existing gates. Reload after an ordinary transient failure; do not repeatedly save or create sessions to diagnose an endpoint failure.
|
|
48
|
-
|
|
49
|
-
Loading a supported view performs non-forcing account discovery and may use the existing OAuth refresh/network lifecycle. It is not guaranteed to be a credential- or network-side-effect-free probe. Regression tests use isolated synthetic services instead of the live profile.
|
|
50
|
-
|
|
51
|
-
## UI verification captures
|
|
52
|
-
|
|
53
|
-
These historical captures show the actual built component with **synthetic** account/workspace responses, not the production Desktop. They predate the current-workspace change and still show the removed destination dropdown; use the current browser fixture for the updated layout. [Capture provenance and artifact hashes](./images/dual-model-provenance.json) identify the exact evidence.
|
|
54
|
-
|
|
55
|
-

|
|
56
|
-
|
|
57
|
-

|
|
58
|
-
|
|
59
|
-
## Native dropdown appearance
|
|
60
|
-
|
|
61
|
-
Model and search-provider selects and their options use the application's surface, primary/secondary text and border tokens. They do not infer the application theme from the operating system. Hosts without the tokens use paired system-color fallbacks. This is presentation only: changing theme does not save settings or replace selections.
|
|
62
|
-
|
|
63
|
-
After building, `node tests/browser/verify-native-selects.mjs --playwright-module /absolute/path/to/existing/playwright-core/index.mjs --channel msedge` runs optional isolated browser checks without installing a browser dependency. It checks computed option/control colors, synthetic contrast, theme switching without remount or writes, 375px layout and enabled-control system fallbacks. The fixtures supply theme tokens rather than global option styling, so fixture CSS cannot hide a missing component style. It also exercises English/Chinese workspace flows: save without a workspace, preserve drafts on destination changes, block unknown destinations, and retry the original uncertain creation after navigation. These run against the built card with synthetic props/Remote responses; mounted public-list wiring is covered separately by the integration tests.
|
|
64
|
-
|
|
65
|
-
Page screenshots do not necessarily contain the OS-owned expanded popup. Check the expanded native menu separately on the target browser, including unavailable/disabled entries and the selected highlight. The automated computed-style checks are not full Windows popup-painting or live Desktop acceptance evidence; historical captures above predate this appearance fix.
|
|
66
|
-
|
|
67
|
-
## Public integration and evidence
|
|
68
|
-
|
|
69
|
-
The feature reuses public settings, account discovery, scope, Agent creation, Session projection/persistence, workspace attachment, tool restrictions/guards and native continuable subagents. It does not access Core private registries, edit prototypes, patch deployed packages, copy grants, install another wire adapter or require a Core change.
|
|
70
|
-
|
|
71
|
-
Missing Host role capabilities yield an unavailable card. Missing Client navigation/list capabilities disable fresh dedicated-session creation, not profile-global configuration. The package's broad compatibility range covers its existing account/search features; it is **not** a promise that this optional flow works on every historical baseline.
|
|
72
|
-
|
|
73
|
-
Current workspace observation uses only the public `sessions.list` and `workspaces.list` snapshot/subscribe faces. On [exact official alpha.2](https://github.com/deepseek-ai/deepseek-harness/blob/ddefc45fbc7f8e46dd73185e68295696d1297887/packages/api/session-controller/src/client/sessions/service.ts), `SessionListState` no longer exposes `current`: the plugin reads the unique `byId` row with positive public `retainedBy.mainView` ownership, matching the source used by [Core's UI Session adapter](https://github.com/deepseek-ai/deepseek-harness/blob/ddefc45fbc7f8e46dd73185e68295696d1297887/packages/client/ui-session/src/client/index.ts). Retained legacy Clients expose `current` directly. Both paths require ready lists and unique workspace membership through `workspaceId` / `sessionIds`. Pending, unavailable or ambiguous selection is not a creation destination. The observer never retains a Session, opens history, reads private navigation state, or calls native new-session navigation. One Remote face per registration owner preserves unsaved edits and uncertain receipts while those lists update.
|
|
74
|
-
|
|
75
|
-
Regression evidence is separated deliberately:
|
|
76
|
-
|
|
77
|
-
- `dual-model-card.spec.ts`: real React DOM/jsdom interaction, bilingual copy, CAS, unavailable models, stale responses and uncertain-create receipt handling.
|
|
78
|
-
- `dual-model-ui.spec.ts`: optional Slot registration, fallback and cleanup.
|
|
79
|
-
- `current-workspace.spec.ts` / `dual-model-workspace-ui.spec.ts`: synthetic public legacy/current-target list shapes, real Cordis dependency tracing and React-mounted Slot callbacks, current-workspace changes without draft loss, optional-service lifetime, and uncertain request retention across navigation and surface remounts. These are not live Desktop navigation certification.
|
|
80
|
-
- `dual-model-remote.spec.ts` / `dual-model-gateway.spec.ts`: strict owned codecs and the actual installed Client Gateway with synthetic RPC. Older Client Gateways do not sanitize successful values or arbitrary nested error details; the Host builds bounded DTOs, and the UI renders only its diagnostic allowlist.
|
|
81
|
-
- `tests/scripts/dual-model-host-gateway.test.mjs`: postbuild Node tests drive the real public Host Connection Fetch handler and Gateway, bypassing Vitest's protocol stub. They cover endpoint exposure, unsupported capabilities, domain input validation, private-method refusal, disposal, and synthetic model/workspace view plus CAS save. SRC JSON fallback does not inherit the Client's strict descriptors; Host validation rejects malformed nested inputs.
|
|
82
|
-
- `dual-model-host.spec.ts`: actual Core Session/projection/scope/tool primitives combined with synthetic Agent, model, persistence and workspace edges. This is not a paid live model run or a full installed Desktop certification.
|
|
83
|
-
- `remote-codec.spec.ts` / `dual-model-projection.spec.ts`: strict factory/legacy-parser bridge, native v3 descriptor admission, cache version/refolding contract, and fail-closed malformed/unknown/v1/v2 histories without mutation.
|
|
84
|
-
- `tests/fixtures/alpha2-contracts-core.fixture.ts`: exact alpha.2 contract fixture run through `scripts/verify-tagged-core.mjs`; the narrow supplemental exact-source run passed, but full official-helper closure qualification remains pending as described above, not implied by local rc.1-backed tests.
|
|
85
|
-
- `tests/browser/serve-dual-model.mjs`: serves the actual built Client component on a separate loopback fixture using synthetic account/workspace responses. Run after `pnpm build`; the printed URL is explicitly **not** the production DSH GUI.
|
|
86
|
-
|
|
87
|
-
Publication, Desktop installation, runtime activation and successful real model calls remain separate checks. Never restart active sessions or claim the installed UI changed merely because the repository build passed.
|
|
42
|
+
This task requests a PR only. Prepared version metadata is not publication. Do not install or restart a running DSH to verify this removal without separate authorization.
|
|
88
43
|
|
|
89
44
|
## 中文摘要
|
|
90
45
|
|
|
91
|
-
|
|
46
|
+
alpha.34 candidate 移除「模型分工」、旧版设置回退入口、规划/执行选择器和新建专用双模型会话按钮。普通 Session 与原生 subagent 是今后的使用方式;父模型到子模型的自动映射及原生 UI 属于另一个仍待交付的 Core PR #95,本插件不会重复实现,也不会假装旧 Core 已支持。
|
|
92
47
|
|
|
93
|
-
|
|
48
|
+
已有专用会话保留历史、固定策略和模型路由,继续由兼容 Host 支持;旧设置不删除、不迁移,普通 Session 不会被自动加入旧流程。已有专用根会话中的执行工具可以继续工作,但不能再通过旧入口新建专用根会话。
|
|
94
49
|
|
|
95
|
-
|
|
50
|
+
旧 Remote 的 view 明确报告已退役且只读,不发现模型;save 拒绝写入;create 只允许凭完全匹配的旧请求身份恢复已创建会话,不创建新根。冲突或未知结果仍保守处理,不通过换 UUID 绕过。不要编辑历史、自动换模型或将插件卸载当作会话迁移。
|
|
96
51
|
|
|
97
|
-
|
|
52
|
+
本次仅提交 PR,版本号为仓库检查预备;发布、安装、生效和真实模型调用均需分别验证,不重启当前 DSH。
|
|
@@ -6,7 +6,13 @@ Candidate plugin **`0.4.0-alpha.25`** adds the ninth exact target: official **`d
|
|
|
6
6
|
|
|
7
7
|
Prefer official implementations when they satisfy the requirement, including configuration/data migration, API behavior, safety and runtime acceptance. **Complete** means the cited official contract covers the named scope, not that a live deployment passed. **Partial** identifies both an official capability and a concrete remaining requirement. **Unverified** means parity has not been established; it does not mean official support is absent. Decisions are **retain**, **migrate**, or **retire**; conditional retirement requires the evidence in the last column and a reviewed change, never automatic removal on a version bump.
|
|
8
8
|
|
|
9
|
-
##
|
|
9
|
+
## Role-experience retirement follow-up (#158)
|
|
10
|
+
|
|
11
|
+
The user no longer requires a dedicated planner/executor experience. Alpha.34 therefore **retires the role card, old Settings fallback, configuration writes and new dedicated roots**, independently of official feature parity or pending [Core PR #95](https://github.com/cloga/deepseek-harness/pull/95). That Core PR is separate parent-to-child default routing with its own native UI, not a shipped dependency of this plugin.
|
|
12
|
+
|
|
13
|
+
The historical role/UI retention decisions below are superseded for new use. **Retain only existing-history policy/route enforcement and exact-request recovery**, with strict compatibility Remotes, until a separately reviewed retirement or migration can preserve those histories safely. Do not silently reinterpret a dedicated history as an ordinary Session. Account/search/usage cards remain unchanged. No new official version or API is adopted by this retirement.
|
|
14
|
+
|
|
15
|
+
## Compact decision matrix (alpha.25 historical comparison)
|
|
10
16
|
|
|
11
17
|
| Custom surface / purpose | Exact official source and support | Decision | Remaining gap / retirement trigger |
|
|
12
18
|
|---|---|---|---|
|