dsh-github-copilot 0.4.0-alpha.37 → 0.4.0-alpha.38

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
@@ -29,7 +29,7 @@ Use native DSH tools for goals, background jobs and scoped subagents. Use local
29
29
 
30
30
  ## Product and architecture
31
31
 
32
- `dsh-github-copilot` is a companion targeting official DSH `0.1.6-alpha.2`, with retained baselines for DSH `0.1.6-alpha.1`, DSH `0.1.5-rc.2`, DSH `0.1.5-rc.1`, DSH `0.1.5-alpha.2`, DSH `0.1.5-alpha.1`, DSH `0.1.3-alpha.1`, DSH `0.1.2-rc.1`, and the controlled DSH Desktop `0.1.1-rc.2` Core baseline. It does not own a general Copilot chat adapter. DSH's built-in `llm-pi-ai` mount owns the GitHub Copilot provider, catalog, OAuth method and grant format, token exchange, refresh, and normal model transport.
32
+ `dsh-github-copilot` currently admits and targets only official DSH and Windows Desktop `0.2.0-rc.1`. Nine earlier DSH pins remain in `deployment-baseline.json` as historical evidence, not current support or CI release gates. It does not own a general Copilot chat adapter. DSH's built-in `llm-pi-ai` mount owns the GitHub Copilot provider, catalog, OAuth method and grant format, token exchange, refresh, and normal model transport.
33
33
 
34
34
  This repository owns eleven narrow surfaces:
35
35
 
@@ -126,12 +126,13 @@ The retained upstream baselines and current qualification target are:
126
126
  - Official tag `dsh-v0.1.5-rc.2`, commit `fb2c4b9e698e30edb738bca4cf0618587db7d203`.
127
127
  - Official tag `dsh-v0.1.6-alpha.1`, commit `0a15e36e7f82b6ed45af6fa9759f29b40dcd965d`.
128
128
  - Official tag `dsh-v0.1.6-alpha.2`, commit `ddefc45fbc7f8e46dd73185e68295696d1297887`.
129
+ - Official tag `dsh-v0.2.0-rc.1`, commit `4878cdabd87d4041bdaff61d04c966883b9fd07a`; the independently verified Windows Desktop feed also identifies `0.2.0-rc.1`.
129
130
 
130
- The current qualification target is official `0.1.6-alpha.2`; retain all eight earlier pins (nine total) and exact `0.1.2-rc.1` development dependencies. All seven tagged-source targets use unchanged tagged-source runtime fixtures, not standalone npm-artifact certification. The 0.1.6 fixture must await serialized `agent/created`, avoid new synchronous Session-history reads, and verify MCP resource cursors, PTC/workflow names, cancellable Sandbox/Shell preparation, optional-plugin startup policy, attachment cache separation, durable `IMAGE_OFFLOAD_REQUIRED` projection/retry and Team pagination without taking ownership of those services. Compatibility metadata and synthetic tests do not prove live endpoints, installed Desktop bytes, release publication or loaded runtime state. Public Host, Client and Remote seams remain available; this baseline update does not authorize implementation rewrites.
131
+ The release admission, development dependency and CI targets are exact official `0.2.0-rc.1`; the other nine pins remain historical evidence only. CI runs the unchanged tagged-source runtime fixture and an isolated exact published-npm-artifact fixture for `0.2.0-rc.1` on Windows and Linux. The current fixture must await serialized `agent/created`, avoid new synchronous Session-history reads, and verify MCP resource cursors, PTC/workflow names, cancellable Sandbox/Shell preparation, optional-plugin startup policy, attachment cache separation, durable `IMAGE_OFFLOAD_REQUIRED` projection/retry and Team pagination without taking ownership of those services. Compatibility metadata and synthetic tests do not prove live endpoints, a materialized Desktop package set, installed Desktop bytes, release publication or loaded runtime state. Public Host, Client and Remote seams remain available; this baseline update does not authorize implementation rewrites.
131
132
 
132
133
  These pins document compatibility evidence. They do not authorize creating another controlled Core patch or making one a prerequisite for new plugin fixes.
133
134
 
134
- - Models UI: `0.1.2-rc.1`, `0.1.3-alpha.1`, `0.1.5-alpha.1`, `0.1.5-alpha.2`, `0.1.5-rc.1`, `0.1.5-rc.2`, `0.1.6-alpha.1` and `0.1.6-alpha.2` expose `settings.models.provider-card`, keyed by settings namespace `llm-pi-ai`, to embed login/status/Refresh/Manage in a mounted configured canonical `github-copilot` row and suppress the separate footer controller. With no such row mounted, retain footer fallback; rc.2 uses a dedicated `settings.section`. Preserve the shared account-state owner across transfer only while another eligible surface remains mounted. Unmounting the last surface or replacing declarations without overlapping mounts stops polling; a later controller reads status and separately non-forcing ensures missing/idle/stale/error/loading signed-in metadata, without replaying the old forced-login action. Manual Refresh models lives inside Manage; errors expose Retry. Opening Models is no longer guaranteed network-free, but status/details themselves remain pure. This additive slot cannot replace Core Edit/Delete: retain the native editor, while normal plugin discovery needs no manual model definitions. UI integration must not merge/remove actual canonical and `github-copilot-preview` routes or rewrite credentials, configuration, history or selection.
135
+ - Models UI: `0.1.2-rc.1`, `0.1.3-alpha.1`, `0.1.5-alpha.1`, `0.1.5-alpha.2`, `0.1.5-rc.1`, `0.1.5-rc.2`, `0.1.6-alpha.1`, `0.1.6-alpha.2` and `0.2.0-rc.1` expose `settings.models.provider-card`, keyed by settings namespace `llm-pi-ai`, to embed login/status/Refresh/Manage in a mounted configured canonical `github-copilot` row and suppress the separate footer controller. With no such row mounted, retain footer fallback; rc.2 uses a dedicated `settings.section`. Preserve the shared account-state owner across transfer only while another eligible surface remains mounted. Unmounting the last surface or replacing declarations without overlapping mounts stops polling; a later controller reads status and separately non-forcing ensures missing/idle/stale/error/loading signed-in metadata, without replaying the old forced-login action. Manual Refresh models lives inside Manage; errors expose Retry. Opening Models is no longer guaranteed network-free, but status/details themselves remain pure. This additive slot cannot replace Core Edit/Delete: retain the native editor, while normal plugin discovery needs no manual model definitions. UI integration must not merge/remove actual canonical and `github-copilot-preview` routes or rewrite credentials, configuration, history or selection.
135
136
  - Authorization flow key: `llm-pi-ai/github-copilot`.
136
137
  - Authorization verification links recognize the public `window.dshDesktop.protocolVersion === 1` marker and use `_self` so Desktop's existing `will-navigate` handler opens the system browser without popup creation. Other hosts retain `_blank`; display a selectable manual URL in both cases. This does not confirm browser launch or OAuth success. Manage omits the compatibility disclosure but retains actionable legacy diagnostics and explicit repair; migration documentation and backend ownership are unchanged.
137
138
  - Authorization service: rc.1 Core provides it; the rc.2 web/headless profiles rely on this package's runtime dependency and conditional bootstrap.
@@ -187,6 +188,8 @@ Installation agents using the DSH `pwsh` tool must follow these rules:
187
188
 
188
189
  The plugin keeps its managed Copilot route on ordinary JSON-schema tool calling and removes `sandbox_permissions` plus `justification` only from tool schemas assembled for the `github-copilot` provider. Optional schema semantics alone do not stop these models from emitting invalid escalation requests. Other providers retain the native one-shot escalation surface; Copilot sessions must choose sufficient standing permissions before a call that needs wider access. The rules above remain agent-side practice, and the plugin does not rewrite user-global agent instructions.
189
190
 
191
+ Desktop plugin upgrades do not necessarily reconcile profile-local copies of Host peers. Check the actual resolved `@deepseek-ai/dsh-authorization` (and other shared peers) against the Desktop's bundled package set after upgrades: an older profile-local authorization package can shadow the current bundled service, fail peer validation and prevent dependent account plugins from starting. Do not delete or replace live files as part of plugin compatibility work; use a separately authorized repair and verify module resolution.
192
+
190
193
  ## Mechanical verification
191
194
 
192
195
  Run from the repository root:
@@ -201,7 +204,7 @@ Then run `pnpm verify:tarball -- artifacts/dsh-github-copilot-<package-version>.
201
204
 
202
205
  `pnpm verify` checks the Agent contract, source and local test types, baseline markers, a clean build, Vitest tests, Node tooling tests, and real built Host import/Client-loader/Remote smoke. `tests/fixtures` are intentionally excluded from local test typecheck because they import source from a separate pinned Core checkout. The checked-in code must pass; never suppress compiler errors or weaken a test to get a green report.
203
206
 
204
- The CI definition targets Windows/Linux against all nine exact Core baselines, with unchanged tagged-source runtime checks for all seven tagged-source targets: `0.1.3-alpha.1`, `0.1.5-alpha.1`, `0.1.5-alpha.2`, `0.1.5-rc.1`, `0.1.5-rc.2`, `0.1.6-alpha.1` and `0.1.6-alpha.2`. Optional native Chat fixtures also cover all seven tagged-source targets and `0.1.2-rc.1`. This is a required gate, not evidence that alpha.25 qualification has executed. `verify:upstream` is static seam-marker evidence. `verify:controlled-core` exclusively installs a temporary config fixture, refuses an existing target, and removes only its own file; it is not full plugin activation. The published rc.2 adapter test covers model materialization, not live provider transport. The release job must wait for the complete reusable CI matrix on the tagged revision, then verify its own packed bytes before publishing.
207
+ The release CI matrix targets only exact official `0.2.0-rc.1` on Windows and Linux; earlier pins are not support gates. It runs the unchanged tagged-source runtime fixture, optional native Chat fixture, and exact published-artifact adapter fixture. This is a required gate, not evidence that a candidate qualification has executed. `verify:upstream` is static seam-marker evidence. `verify:controlled-core` exclusively installs a temporary config fixture, refuses an existing target, and removes only its own file; it is not full plugin activation. Published-artifact synthetic adapter fixtures do not prove live provider transport. The release job must wait for the complete reusable CI matrix on the tagged revision, then verify its own packed bytes before publishing.
205
208
 
206
209
  ### Evidence and side effects
207
210
 
package/CHANGELOG.md CHANGED
@@ -1,5 +1,13 @@
1
1
  # Changelog
2
2
 
3
+ ## 0.4.0-alpha.38 (prepared)
4
+
5
+ - Add official DSH `0.2.0-rc.1` as the current exact compatibility target while retaining the existing baseline pins; use the corresponding public Core packages in development and tagged-source CI.
6
+ - Adapt plugin settings reads/listeners to the current public `SettingsForms` descriptor/event API while retaining legacy Core compatibility. Materialize volatile pi-ai provider profiles through their public getter.
7
+ - Preserve current first-class tool messages, older nested tool results and Core-owned developer history semantics in the plugin's guarded serializers; retain recursive legacy file detection when the Core predicate does not recognize older nested content.
8
+ - Update Remote/Gateway and serialized agent lifecycle regressions to match the published 0.2 contracts, and keep provider routing writes isolated from the Copilot settings namespace.
9
+ - Record the pinned official-first API review and qualification boundaries in `docs/official-first-020-rc1.md`. Local tests do not qualify the packaged Windows Desktop runtime, live OAuth/provider calls, or loaded Desktop activation.
10
+
3
11
  ## 0.4.0-alpha.37 (prepared)
4
12
 
5
13
  - Recognize both observed uncoded Responses scope-401 messages, including `input item does not belong to this connection` without `ID`, so that request-local rejection does not retire shared OAuth proof or abort neighboring calls (#164).
package/README.md CHANGED
@@ -21,9 +21,10 @@ A focused DSH companion for GitHub Copilot sign-in, account-aware model profiles
21
21
  | Official DSH `0.1.5-rc.1` | Tag commit [`183f08e`](https://github.com/deepseek-ai/deepseek-harness/commit/183f08e9c6dde7e36cd2318eaee70b0da08fb35e) | **Settings → Models** provider card |
22
22
  | Official DSH `0.1.5-rc.2` | Tag commit [`fb2c4b9`](https://github.com/deepseek-ai/deepseek-harness/commit/fb2c4b9e698e30edb738bca4cf0618587db7d203) | **Settings → Models** provider card |
23
23
  | Official DSH `0.1.6-alpha.1` | Tag commit [`0a15e36`](https://github.com/deepseek-ai/deepseek-harness/commit/0a15e36e7f82b6ed45af6fa9759f29b40dcd965d) | **Settings → Models** provider card |
24
- | Official DSH `0.1.6-alpha.2` (current qualification target) | Tag `dsh-v0.1.6-alpha.2`, commit [`ddefc45`](https://github.com/deepseek-ai/deepseek-harness/commit/ddefc45fbc7f8e46dd73185e68295696d1297887) | **Settings → Models** provider card |
24
+ | Official DSH `0.1.6-alpha.2` | Tag `dsh-v0.1.6-alpha.2`, commit [`ddefc45`](https://github.com/deepseek-ai/deepseek-harness/commit/ddefc45fbc7f8e46dd73185e68295696d1297887) | **Settings → Models** provider card |
25
+ | Official DSH and Windows Desktop `0.2.0-rc.1` (current qualification target) | Tag `dsh-v0.2.0-rc.1`, commit [`4878cd`](https://github.com/deepseek-ai/deepseek-harness/commit/4878cdabd87d4041bdaff61d04c966883b9fd07a) | **Settings → Models** provider card |
25
26
 
26
- The table retains historical source pins; it does not imply the account-model route has been verified on every baseline. Published-artifact synthetic transport tests use the **rc.1 adapter with pi 0.85.1**; development dependencies remain pinned to `0.1.2-rc.1`. The controlled rc.2 pin is historical regression evidence only. DSH `0.1.3-alpha.1`, official `0.1.5-alpha.1`, `0.1.5-alpha.2`, `0.1.5-rc.1`, `0.1.5-rc.2`, `0.1.6-alpha.1`, and `0.1.6-alpha.2` are unchanged tagged-source targets: CI exercises each through an isolated test resolver, without building or patching Core. These source-runtime checks must pass before claiming compatibility; they do not establish standalone npm-artifact, live endpoint, installed Desktop, or loaded-runtime proof. Existing public Host, Client, and Remote seams are retained. Stock Core model-entry `api` support is not a prerequisite for the plugin-owned route. Package peer and `engines.dsh` ranges are admission declarations, not live compatibility proof. No Core patch is installed by this plugin.
27
+ The table preserves historical source pins; this release admits and gates **only `0.2.0-rc.1`**. The prior pins are not current support claims. The published-artifact synthetic transport fixture and development dependencies target the exact `0.2.0-rc.1` npm artifacts. Its unchanged tagged-source fixture runs without building or patching Core. These checks do not establish live endpoint, installed Desktop package-set, or loaded-runtime proof. Existing public Host, Client, and Remote seams are retained. Stock Core model-entry `api` support is not a prerequisite for the plugin-owned route. The exact peer and `engines.dsh` declarations are admission checks, not live compatibility proof. No Core patch is installed by this plugin.
27
28
 
28
29
  ### Alpha.11 compatibility correction (#105)
29
30
 
@@ -55,10 +56,16 @@ Alpha.24 fixes the Web search card's missing traced Remote dependency. It remain
55
56
 
56
57
  ### Alpha.25 official-first DSH 0.1.6-alpha.2 adaptation
57
58
 
58
- The candidate appends the ninth exact target, `dsh-v0.1.6-alpha.2` at `ddefc45fbc7f8e46dd73185e68295696d1297887`. Strict Remote descriptors now provide alpha.2 `create()` factories while retaining a legacy `schema` bridge to the same strict parser. Dedicated executor projection admission uses native `subagent/descriptor` **v3**, already v3 in rc.1: the old v1 assumption was a plugin bug, not an upstream v1-to-v3 migration. Projection cache **`stateVersion: 2`** forces refolding, not history conversion. Unknown/v1/v2 descriptor histories fail closed and remain unmodified; review the old child and explicitly create a new child if needed, never fake a conversion by relabeling its descriptor.
59
+ The historical baseline inventory includes `dsh-v0.1.6-alpha.2` at `ddefc45fbc7f8e46dd73185e68295696d1297887`; it is not admitted by this release. Strict Remote descriptors now provide alpha.2 `create()` factories while retaining a legacy `schema` bridge to the same strict parser. Dedicated executor projection admission uses native `subagent/descriptor` **v3**, already v3 in rc.1: the old v1 assumption was a plugin bug, not an upstream v1-to-v3 migration. Projection cache **`stateVersion: 2`** forces refolding, not history conversion. Unknown/v1/v2 descriptor histories fail closed and remain unmodified; review the old child and explicitly create a new child if needed, never fake a conversion by relabeling its descriptor.
59
60
 
60
61
  Source markers, local rc.1-backed focused tests and fifteen scoped exact-source runtime tests passed (alpha.2 contracts 8, Remote 1 and Session-context 6). Full local `pnpm verify` passed: 1373 Vitest tests with 2 expected skips, 176 tooling tests, typechecks, build and package smoke; pack/tarball verification also passed. The scoped run used a supplemental resolver with official TypeScript `6.0.3`, declared `mime-types@3.0.2` and `ws@8.21.0`, and shared Zod `^4.4.3`, without source/dependency patches; it is not full official-root-helper qualification. Broad frozen dependency installation remains blocked by the configured mirror returning HTTP 404 for `node-addon-require-builtin@0.1.6`. **CI qualification has not executed.** No published-artifact compatibility, live Desktop activation, OAuth or real model-call success is claimed. The [official-first matrix](./docs/official-first-016-alpha2.md) records exact official sources, support scope, retained gaps and retirement triggers rather than assuming missing parity from feature names.
61
62
 
63
+ ### Alpha.26 official DSH 0.2.0-rc.1 adaptation
64
+
65
+ The current source target is official tag `dsh-v0.2.0-rc.1`, commit `4878cdabd87d4041bdaff61d04c966883b9fd07a`; the independently verified Windows Desktop release feed also reports `0.2.0-rc.1` (SHA-512 `hPdqeajEHTXYEUOkOX7q1FflGU9jyOkRVDNSPxIDWhNihWjiVal0gtuT5zvtBRlX29VhqfHL31q4owGNp4ee6A==`). Development dependencies, peer admission and CI target exactly this release; earlier pins are historical evidence only. The unchanged-source runtime fixture covers the plugin's OAuth credential seam, account-owned model discovery and native adapter, reasoning/streaming/tool behavior, Web search, Remote codecs, Session context and strict schema compatibility; the published npm fixture independently checks package/class identity and synthetic transport. Prior Desktop package graphs are retained only for dependency-ownership audit and do not validate the 0.2.0 Desktop package set. Current package-set materialization, Electron loading, live sign-in and profile upgrade are **not** claimed by these tests.
66
+
67
+ Installation does not reconcile stale profile-local copies of DSH host peers. Before an upgrade, inspect the effective dependency resolution against the Desktop's shipped package versions; an older local `@deepseek-ai/dsh-authorization` can shadow the bundled service, fail Core peer validation and disable authorization-dependent account plugins. This package does not remove or replace such files. Use the separate approved Desktop repair procedure and verify effective module resolution before attributing a startup failure to this plugin. See [the 0.2.0 official-first review](./docs/official-first-020-rc1.md).
68
+
62
69
  ## Copilot usage beside the composer
63
70
 
64
71
  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.
@@ -73,7 +80,7 @@ The Host reads GitHub's internal quota endpoint using the existing canonical OAu
73
80
 
74
81
  ## Install and sign in
75
82
 
76
- The commands below target the package version `0.4.0-alpha.37`. 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):
83
+ The commands below target the package version `0.4.0-alpha.38`. 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):
77
84
 
78
85
  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):
79
86
 
@@ -81,15 +88,15 @@ Before installing/updating, unpack the **checksum-verified** archive into a temp
81
88
  node package/scripts/check-search-composition.mjs --profile-dir /absolute/profile --home /absolute/DSH_HOME --install-anchor /absolute/dsh/package.json
82
89
  ```
83
90
 
84
- Include any launcher patch files with repeated `--patch /absolute/file` arguments. Require `supported: true`; otherwise do not install the routing bundle. The preflight rejects custom, disabled, nested or already-isolated web-service layouts and reserved routing collisions before any mutation. It parses through public Core APIs and never boots plugins, resolves credentials or rewrites configuration. **`dsh plugin add` does not automatically run this preflight.** It is a required installer/operator step, not a universal compatibility guarantee.
91
+ Include any launcher patch files with repeated `--patch /absolute/file` arguments. Require `supported: true`; otherwise do not install the routing bundle. The preflight rejects custom, disabled, nested or already-isolated web-service layouts, reserved routing collisions, and a nonempty disposable `cordis.yml` root before any mutation. It parses through public Core APIs and never boots plugins, resolves credentials or rewrites configuration. DSH 0.2's normal `composeProfile()` also rewrites that root to `[]`, including on Desktop's resolved-profile path; preserve and resolve any nonempty root before attempting install/startup. **`dsh plugin add` does not automatically run this preflight.** It is a required installer/operator step, not a universal compatibility guarantee. Also check that effective profile dependency resolution does not let a stale profile-local DSH peer shadow the host's bundled `0.2.0-rc.1` service; the plugin installer does not reconcile old host modules.
85
92
 
86
- For approved online installation, the supported CLI command is:
93
+ For a standalone named profile only, the supported CLI command is:
87
94
 
88
95
  ```sh
89
- dsh plugin --profile web add https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.0-alpha.37/dsh-github-copilot-0.4.0-alpha.37.tgz
96
+ dsh plugin --profile web add https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.0-alpha.38/dsh-github-copilot-0.4.0-alpha.38.tgz
90
97
  ```
91
98
 
92
- 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.
99
+ For Desktop profiles, use Desktop's native package manager with `dsh-github-copilot@0.4.0-alpha.38` 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.
93
100
 
94
101
  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.
95
102
 
@@ -151,7 +158,7 @@ Agents should treat the browser authorization as a human handoff, not as a token
151
158
  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.
152
159
  6. Use **Sign out** only when the user explicitly asks to disconnect the account. It deletes the Copilot credential record but preserves route settings.
153
160
 
154
- 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.37`, 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).
161
+ 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.38`, 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).
155
162
 
156
163
  No `copilot2api` process, external gateway, placeholder API key, pasted GitHub token, or separate `dsh-web-search-provider` installation is required.
157
164
 
@@ -381,9 +388,9 @@ pnpm verify
381
388
  pnpm pack --pack-destination artifacts
382
389
  ```
383
390
 
384
- Use Node 24 LTS for development and the pinned pnpm version; runtime dependencies require Node >=22.19.0. `pnpm verify` runs the Agent contract check, source and local test typechecking, baseline markers, clean build, Vitest and Node tooling tests, and a real built Host import plus Client/Remote smoke. After packing, run `pnpm verify:tarball -- artifacts/dsh-github-copilot-<package-version>.tgz` to verify archive exports, media, allowed contents and equality to that build. The CI definition targets all nine exact Core sources/config fixtures on Windows and Linux: controlled `0.1.1-rc.2`, `0.1.2-rc.1`, `0.1.3-alpha.1`, official `0.1.5-alpha.1`, `0.1.5-alpha.2`, `0.1.5-rc.1`, `0.1.5-rc.2`, `0.1.6-alpha.1`, and `0.1.6-alpha.2`. All seven tagged-source targets are gated by unchanged tagged-source runtime fixtures; release publication depends on that full matrix. This candidate's CI qualification has not executed; see the alpha.25 evidence limits above.
391
+ Use Node 24 LTS for development and the pinned pnpm version; runtime dependencies require Node >=22.19.0. `pnpm verify` runs the Agent contract check, source and local test typechecking, baseline markers, clean build, Vitest and Node tooling tests, and a real built Host import plus Client/Remote smoke. After packing, run `pnpm verify:tarball -- artifacts/dsh-github-copilot-<package-version>.tgz` to verify archive exports, media, allowed contents and equality to that build. CI gates only exact DSH `0.2.0-rc.1` on Windows and Linux, using its unchanged source runtime and published npm artifacts; the nine earlier pins are retained historical evidence, not release gates. Release publication depends on this exact-target matrix. This candidate's CI qualification has not executed; see the alpha.25 and alpha.26 evidence limits above.
385
392
 
386
- For the optional reasoning UI integration, `pnpm verify:reasoning-ui -- <Core checkout>` runs a synthetic native-renderer, Slot registry and history-assembly fixture against a clean pinned `0.1.2-rc.1`, `0.1.3-alpha.1`, `0.1.5-alpha.1`, `0.1.5-alpha.2`, `0.1.5-rc.1`, `0.1.5-rc.2`, `0.1.6-alpha.1`, or `0.1.6-alpha.2` checkout with its Chat dependencies installed. It exclusively creates one temporary test file and removes it only if unchanged. This is local integration/static-render evidence, not a live browser or Copilot API test; the CI definition covers all eight supported Chat baselines, without implying this candidate's qualification has run.
393
+ For the optional reasoning UI integration, `pnpm verify:reasoning-ui -- <Core checkout>` runs a synthetic native-renderer, Slot registry and history-assembly fixture against a clean pinned `0.2.0-rc.1` checkout with its Chat dependencies installed. It exclusively creates one temporary test file and removes it only if unchanged. This is local integration/static-render evidence, not a live browser or Copilot API test; the CI definition covers only the current target, without implying this candidate's qualification has run.
387
394
 
388
395
  ### Agent-driven development
389
396
 
@@ -415,8 +422,8 @@ Report the published Release URL, version, tag/commit and verified asset SHA-256
415
422
  `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.
416
423
 
417
424
  ```sh
418
- curl -LO https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.0-alpha.37/dsh-github-copilot-0.4.0-alpha.37.tgz
419
- curl -LO https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.0-alpha.37/SHA256SUMS
425
+ curl -LO https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.0-alpha.38/dsh-github-copilot-0.4.0-alpha.38.tgz
426
+ curl -LO https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.0-alpha.38/SHA256SUMS
420
427
  sha256sum --check SHA256SUMS
421
428
  ```
422
429
 
@@ -424,7 +431,7 @@ PowerShell can verify the same two downloaded files with:
424
431
 
425
432
  ```powershell
426
433
  $expected = (Get-Content .\SHA256SUMS).Split()[0]
427
- $actual = (Get-FileHash .\dsh-github-copilot-0.4.0-alpha.37.tgz -Algorithm SHA256).Hash.ToLowerInvariant()
434
+ $actual = (Get-FileHash .\dsh-github-copilot-0.4.0-alpha.38.tgz -Algorithm SHA256).Hash.ToLowerInvariant()
428
435
  if ($actual -cne $expected) { throw 'Release checksum mismatch' }
429
436
  ```
430
437
 
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.37`;这不代表已有的两条真实路由被合并或移除。版本化 URL 不表示 Release 已发布或本机已加载;仅在该 Release 与校验和可用后使用安装命令。源码、发布制品、已安装版本和实际加载运行时需分别确认,本地升级和中断会话的重启仍需用户批准。
12
+ > 下文自动维护账号模型元数据与 provider 集成控件描述目标版本 `0.4.0-alpha.38`;这不代表已有的两条真实路由被合并或移除。版本化 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
 
@@ -25,9 +25,10 @@ Alpha.24 修复 Web search 卡片缺少精确 Remote 依赖声明的问题。卡
25
25
  | 官方 DSH `0.1.5-rc.1` | Tag commit [`183f08e`](https://github.com/deepseek-ai/deepseek-harness/commit/183f08e9c6dde7e36cd2318eaee70b0da08fb35e) | **Settings → Models** provider card |
26
26
  | 官方 DSH `0.1.5-rc.2` | Tag commit [`fb2c4b9`](https://github.com/deepseek-ai/deepseek-harness/commit/fb2c4b9e698e30edb738bca4cf0618587db7d203) | **Settings → Models** provider card |
27
27
  | 官方 DSH `0.1.6-alpha.1` | Tag commit [`0a15e36`](https://github.com/deepseek-ai/deepseek-harness/commit/0a15e36e7f82b6ed45af6fa9759f29b40dcd965d) | **Settings → Models** provider card |
28
- | 官方 DSH `0.1.6-alpha.2`(当前待验收目标) | Tag `dsh-v0.1.6-alpha.2`,commit [`ddefc45`](https://github.com/deepseek-ai/deepseek-harness/commit/ddefc45fbc7f8e46dd73185e68295696d1297887) | **Settings → Models** provider card |
28
+ | 官方 DSH `0.1.6-alpha.2` | Tag `dsh-v0.1.6-alpha.2`,commit [`ddefc45`](https://github.com/deepseek-ai/deepseek-harness/commit/ddefc45fbc7f8e46dd73185e68295696d1297887) | **Settings → Models** provider card |
29
+ | 官方 DSH 与 Windows Desktop `0.2.0-rc.1`(当前待验收目标) | Tag `dsh-v0.2.0-rc.1`,commit [`4878cd`](https://github.com/deepseek-ai/deepseek-harness/commit/4878cdabd87d4041bdaff61d04c966883b9fd07a) | **Settings → Models** provider card |
29
30
 
30
- 上表保留历史源码 pin,不表示账号模型路由在所有基线上都已验收。已发布制品的合成 transport 测试使用 **rc.1 adapter 与 pi `0.85.1`**,开发依赖继续精确固定为 `0.1.2-rc.1`;受控 rc.2 仅为历史回归证据。`0.1.3-alpha.1`、官方 `0.1.5-alpha.1`、`0.1.5-alpha.2`、`0.1.5-rc.1`、`0.1.5-rc.2`、`0.1.6-alpha.1` 与 `0.1.6-alpha.2` 均作为未修改的标签源码目标,由 CI 使用隔离测试解析器运行,不构建或给 Core 打补丁。对应源码运行检查通过前不宣称兼容性已验收;这些检查不是独立 npm 制品、真实端点、已安装 Desktop 或已加载运行时的证明。已有公开 Host、Client 与 Remote 接口保留。Peer range 与 `engines.dsh` 只声明包准入,不是真实兼容性证明;插件不安装 Core 补丁。
31
+ 上表保留历史源码 pin;本版本**仅准入并 gate 精确的 `0.2.0-rc.1`**,旧 pin 不代表当前支持。已发布制品的合成 transport fixture 与开发依赖均精确针对 `0.2.0-rc.1` npm 制品。未修改标签源码 fixture 不构建或给 Core 打补丁。这些检查不证明真实端点、已安装 Desktop package-set 或已加载运行时。已有公开 Host、Client 与 Remote 接口保留。精确 peer 与 `engines.dsh` 只声明包准入,不是真实兼容性证明;插件不安装 Core 补丁。
31
32
 
32
33
  ### Alpha.11 兼容修复(#105)
33
34
 
@@ -57,10 +58,16 @@ Candidate manifest 将 `@deepseek-ai/dsh-authorization` 与 `@deepseek-ai/schema
57
58
 
58
59
  ### Alpha.25 官方优先的 DSH 0.1.6-alpha.2 适配
59
60
 
60
- Candidate 追加第九个精确目标:`dsh-v0.1.6-alpha.2`,commit `ddefc45fbc7f8e46dd73185e68295696d1297887`。严格 Remote descriptor 提供 alpha.2 所需的 `create()` factory,同时保留旧 Gateway 的 `schema` bridge;两者使用同一个严格 parser,不降级为 `src-json`。执行子代理的 projection 接受原生 `subagent/descriptor` **v3**;rc.1 已经是 v3,旧版 v1 假设属于插件错误,不是本次上游从 v1 升到 v3。插件 projection cache 提升到 **`stateVersion: 2`**,强制从事件重新折叠,不转换历史。未知/v1/v2 descriptor 历史保守拒绝且保持原样;需要继续工作时先审核旧子代理,再显式新建子代理,不能改版本号伪造转换。
61
+ 历史基线清单包含 `dsh-v0.1.6-alpha.2`,commit `ddefc45fbc7f8e46dd73185e68295696d1297887`;本版本不再准入此版本。严格 Remote descriptor 提供 alpha.2 所需的 `create()` factory,同时保留旧 Gateway 的 `schema` bridge;两者使用同一个严格 parser,不降级为 `src-json`。执行子代理的 projection 接受原生 `subagent/descriptor` **v3**;rc.1 已经是 v3,旧版 v1 假设属于插件错误,不是本次上游从 v1 升到 v3。插件 projection cache 提升到 **`stateVersion: 2`**,强制从事件重新折叠,不转换历史。未知/v1/v2 descriptor 历史保守拒绝且保持原样;需要继续工作时先审核旧子代理,再显式新建子代理,不能改版本号伪造转换。
61
62
 
62
63
  源码 marker、本地基于 rc.1 的定向测试,以及十五个限定范围精确源码运行时测试(alpha.2 contracts 8、Remote 1、Session-context 6)已通过。完整本地 `pnpm verify` 通过:1373 个 Vitest 测试、2 个预期跳过、176 个 tooling 测试,以及类型检查、构建和 package smoke;pack/tarball 验证也通过。限定范围运行使用补充 resolver、官方 TypeScript `6.0.3`、声明的 `mime-types@3.0.2` 与 `ws@8.21.0` 和共享 Zod `^4.4.3`,不修改源码或依赖制品,不等于完整 official-root-helper 验收。完整 frozen 依赖安装仍被配置 mirror 对 `node-addon-require-builtin@0.1.6` 返回 HTTP 404 阻塞。**CI 验收尚未执行**;不宣称已发布制品兼容、真实 Desktop 激活、OAuth 或模型调用成功。[官方优先矩阵](./docs/official-first-016-alpha2.md) 记录精确官方源码、支持范围、保留差距与移除条件,不因未验证同等能力就断言官方没有该功能。
63
64
 
65
+ ### Alpha.26 官方 DSH 0.2.0-rc.1 适配
66
+
67
+ 当前源码目标为官方 tag `dsh-v0.2.0-rc.1`,commit `4878cdabd87d4041bdaff61d04c966883b9fd07a`;独立核实的 Windows Desktop 发布 feed 也报告 `0.2.0-rc.1`(SHA-512 `hPdqeajEHTXYEUOkOX7q1FflGU9jyOkRVDNSPxIDWhNihWjiVal0gtuT5zvtBRlX29VhqfHL31q4owGNp4ee6A==`)。开发依赖、peer 准入与 CI 仅针对此版本,旧 pin 仅作历史证据。未修改源码 fixture 覆盖插件 OAuth 凭据接口、账号模型发现与原生 adapter、reasoning/stream/tool、Web 搜索、Remote codec、Session context 与严格 schema 兼容;另以发布 npm 制品 fixture 验证包/类身份和合成传输。既有 Desktop package graph 仅用于依赖所有权审计,不验证 0.2.0 Desktop package-set。当前 package-set 物化、Electron 加载、真实登录或 profile 升级均**未**由这些测试证明。
68
+
69
+ 安装不会协调旧 profile 内的 DSH Host peer 副本。升级前请检查实际依赖解析,确认 Desktop 解析到随附的 Host 模块版本;旧的 profile-local `@deepseek-ai/dsh-authorization` 可能遮蔽随 Desktop 捆绑的服务,因 Core peer 校验失败而禁用 authorization 及其依赖的账号插件。本包不会删除或替换这些文件。请遵循单独获批的 Desktop 修复流程,并先验证实际模块解析,再将启动故障归因于本插件。详见[0.2.0 官方优先审查](./docs/official-first-020-rc1.md)。
70
+
64
71
  ## 输入框附近的 Copilot 用量
65
72
 
66
73
  Alpha.33 修正 alpha.32 调用公开 Session hook 时遗漏 selector 参数的问题;该错误可能导致已注册的用量入口在渲染失败后被撤下。必须单独验证符合条件会话中的正向显示,不能用已安装版本收据或登出时不显示代替。本修复只修改插件,不包含 Core 补丁或自动重启。
@@ -83,15 +90,15 @@ Host 使用现有 canonical OAuth grant 有界读取 GitHub 内部额度端点
83
90
  node package/scripts/check-search-composition.mjs --profile-dir /absolute/profile --home /absolute/DSH_HOME --install-anchor /absolute/dsh/package.json
84
91
  ```
85
92
 
86
- 若启动时还有额外 patch,用重复的 `--patch /absolute/file` 参数一并提供。必须得到 `supported: true` 才继续安装;自定义、已禁用、嵌套、已有隔离映射的 web 服务或路由保留名称冲突会在修改前拒绝。预检只用 Core 公开解析接口,不启动插件、不读取认证凭据、不改配置。**`dsh plugin add` 不会自动执行这项预检**;这是安装者必做步骤,不是对任意第三方组合的兼容保证。
93
+ 若启动时还有额外 patch,用重复的 `--patch /absolute/file` 参数一并提供。必须得到 `supported: true` 才继续安装;自定义、已禁用、嵌套、已有隔离映射的 web 服务、路由保留名称冲突或非空的 disposable `cordis.yml` root 都会在修改前拒绝。预检只用 Core 公开解析接口,不启动插件、不读取认证凭据、不改配置。DSH 0.2 的正常 `composeProfile()` 也会把该 root 重写为 `[]`,包括 Desktop 已解析 profile 的启动路径;如 root 非空,必须先保存数据并解决该问题。**`dsh plugin add` 不会自动执行这项预检**;这是安装者必做步骤,不是对任意第三方组合的兼容保证。还应检查实际依赖解析不会让旧 profile-local DSH peer 遮蔽 Desktop 随附的 `0.2.0-rc.1` 服务;插件安装器不会协调旧 Host 模块。
87
94
 
88
- 获准且网络可用时,可通过受支持的 CLI 命令安装:
95
+ 仅对独立的具名 profile,获准且网络可用时,可通过受支持的 CLI 命令安装:
89
96
 
90
97
  ```sh
91
- dsh plugin --profile web add https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.0-alpha.37/dsh-github-copilot-0.4.0-alpha.37.tgz
98
+ dsh plugin --profile web add https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.0-alpha.38/dsh-github-copilot-0.4.0-alpha.38.tgz
92
99
  ```
93
100
 
94
- 若 registry 被公司封禁或不可用,不要更换网络绕行。Desktop 管理的 profile 可以改用[受控离线 CLI 流程](./docs/npm-distribution.md#controlled-offline-cli-maintenance):使用来源获准、校验通过的本地 Release 和已有依赖缓存(`--offline --ignore-scripts`)。预检、备份和授权要求仍然适用。
101
+ Desktop profile 请在完成同样的预检后,使用 Desktop 原生包管理器安装 `dsh-github-copilot@0.4.0-alpha.38`。Desktop 保留 `desktop` profile,CLI 不负责管理。若 registry 被公司封禁或不可用,不要更换网络绕行或使用离线 CLI;请停止。[受控离线 CLI 流程](./docs/npm-distribution.md#controlled-offline-cli-maintenance-for-standalone-profiles)仅适用于独立具名 profile,不适用于 Desktop。
95
102
 
96
103
  随后打开上表对应的 Models UI,找到 **GitHub Copilot**,点击 **Sign in** 并完成 GitHub device-code 流程。安装会修改指定 profile;是否立即激活取决于该 profile 的常规 reload/restart 策略。
97
104
 
@@ -153,7 +160,7 @@ Agent 应把浏览器授权视为需要用户完成的 handoff,而不是自行
153
160
  5. 确认 **Signed in** 并检查自动发现结果,再请用户选择模型。已登录时打开 Models 会自动确保缺失/过期元数据,新鲜 ready 缓存不发请求。错误可使用 **Retry**,有意强制更新时使用 **Manage → Refresh models**,不作为常规设置步骤。状态读取本身不发现;登录、元数据与真实调用成功是独立证据。
154
161
  6. 只有用户明确要求断开账号时才使用 **Sign out**;它会删除 Copilot credential record,但保留 route settings。
155
162
 
156
- 每个新版本默认同时分发到 GitHub Releases 和 npm,两个渠道使用同一份已验证 tarball。应固定版本并核对所用渠道的证据:Release 的 `SHA256SUMS`;从 npm 安装时另核对 `dist.integrity`。在获准且可用的 registry 网络环境中,优先使用原生 Desktop 包管理器;确认 npm 发布后,它接受 `dsh-github-copilot@0.4.0-alpha.37`,不是 URL 或本地文件。Desktop 管理的 profile 也允许经明确授权的[受控离线 CLI 维护](./docs/npm-distribution.md#controlled-offline-cli-maintenance):使用已验证的本地 Release 和 `--offline --ignore-scripts`,执行必需的组合预检、私密元数据备份、单写入者控制及安装后差异核验。缓存不足或出现权限拒绝时停止,不绕过公司 registry 封禁,不关闭 TLS 校验;重启仍需单独授权。离线安装成功不表示 npm 联网或发布问题已修好。[双渠道发布与 OIDC 要求](./docs/npm-distribution.md)保持不变。
163
+ 每个新版本默认同时分发到 GitHub Releases 和 npm,两个渠道使用同一份已验证 tarball。应固定版本并核对所用渠道的证据:Release 的 `SHA256SUMS`;从 npm 安装时另核对 `dist.integrity`。Desktop profile 只能通过原生 Desktop 包管理器安装;获准且 registry 可用时输入 `dsh-github-copilot@0.4.0-alpha.38`,不是 URL 或本地文件。Desktop 保留 `desktop` profile,不能通过 DSH CLI 管理。受控离线 CLI 维护仅适用于独立具名 profile,不得作为 Desktop 安装绕行方案。[双渠道发布与 OIDC 要求](./docs/npm-distribution.md)保持不变。
157
164
 
158
165
  不需要运行 `copilot2api`,不需要外部 gateway、placeholder API key、原始 GitHub token 或单独安装 `dsh-web-search-provider`。
159
166
 
@@ -392,9 +399,9 @@ pnpm verify
392
399
  pnpm pack --pack-destination artifacts
393
400
  ```
394
401
 
395
- 开发建议使用 Node 24 LTS 和固定的 pnpm 版本;运行时依赖要求 Node >=22.19.0。`pnpm verify` 检查 Agent contract、源码与本地测试类型、baseline marker、干净构建、Vitest 与 Node 工具测试,以及真实构建 Host 导入和 Client/Remote smoke。打包后执行 `pnpm verify:tarball -- artifacts/dsh-github-copilot-<package-version>.tgz`,检查归档 export、图片、允许的文件以及与本次构建的一致性。CI 定义在 Windows/Linux 上覆盖九个精确 Core 源码与配置 fixture:受控 `0.1.1-rc.2`、`0.1.2-rc.1`、`0.1.3-alpha.1`、官方 `0.1.5-alpha.1`、`0.1.5-alpha.2`、`0.1.5-rc.1`、`0.1.5-rc.2`、`0.1.6-alpha.1` 与 `0.1.6-alpha.2`;全部七个标签源码目标还需通过未修改的标签源码运行时 fixture。发布必须等待完整矩阵通过;本 candidate 的 CI 验收尚未执行,证据限制见上文 alpha.25 说明。
402
+ 开发建议使用 Node 24 LTS 和固定的 pnpm 版本;运行时依赖要求 Node >=22.19.0。`pnpm verify` 检查 Agent contract、源码与本地测试类型、baseline marker、干净构建、Vitest 与 Node 工具测试,以及真实构建 Host 导入和 Client/Remote smoke。打包后执行 `pnpm verify:tarball -- artifacts/dsh-github-copilot-<package-version>.tgz`,检查归档 export、图片、允许的文件以及与本次构建的一致性。CI 仅在 Windows/Linux 上 gate 精确 DSH `0.2.0-rc.1`,使用未修改源码 runtime 与发布 npm 制品;其余九个 pin 仅为历史证据,不是发布 gate。发布必须等待此精确目标矩阵通过;本 candidate 的 CI 验收尚未执行,证据限制见上文 alpha.25 与 alpha.26 说明。
396
403
 
397
- 对于可选的思考显示集成,`pnpm verify:reasoning-ui -- <Core checkout>` 会在已安装 Chat 依赖的干净、精确 pin 的 `0.1.2-rc.1`、`0.1.3-alpha.1`、`0.1.5-alpha.1`、`0.1.5-alpha.2`、`0.1.5-rc.1`、`0.1.5-rc.2`、`0.1.6-alpha.1` 或 `0.1.6-alpha.2` checkout 中,执行合成的原生渲染器、Slot 注册器与历史组装 fixture。它只会独占创建一个临时测试文件,并仅在文件未被修改时清理。这是本地集成/静态渲染证据,不是真实浏览器或 Copilot API 测试;CI 定义覆盖八个支持该 Chat 接口的基线,不表示本 candidate 已执行验收。
404
+ 对于可选的思考显示集成,`pnpm verify:reasoning-ui -- <Core checkout>` 会在已安装 Chat 依赖的干净、精确 pin 的 `0.2.0-rc.1` checkout 中,执行合成的原生渲染器、Slot 注册器与历史组装 fixture。它只会独占创建一个临时测试文件,并仅在文件未被修改时清理。这是本地集成/静态渲染证据,不是真实浏览器或 Copilot API 测试;CI 仅覆盖当前目标,不表示本 candidate 已执行验收。
398
405
 
399
406
  ### Agent 驱动开发
400
407
 
@@ -426,8 +433,8 @@ node scripts/agent.mjs attribution "DeepSeek Harness (DSH)"
426
433
  `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 要求包已存在,不能代替首次建包。不会批量补发历史版本。
427
434
 
428
435
  ```sh
429
- curl -LO https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.0-alpha.37/dsh-github-copilot-0.4.0-alpha.37.tgz
430
- curl -LO https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.0-alpha.37/SHA256SUMS
436
+ curl -LO https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.0-alpha.38/dsh-github-copilot-0.4.0-alpha.38.tgz
437
+ curl -LO https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.0-alpha.38/SHA256SUMS
431
438
  sha256sum --check SHA256SUMS
432
439
  ```
433
440
 
@@ -435,7 +442,7 @@ PowerShell 可以对已下载的同一组文件执行:
435
442
 
436
443
  ```powershell
437
444
  $expected = (Get-Content .\SHA256SUMS).Split()[0]
438
- $actual = (Get-FileHash .\dsh-github-copilot-0.4.0-alpha.37.tgz -Algorithm SHA256).Hash.ToLowerInvariant()
445
+ $actual = (Get-FileHash .\dsh-github-copilot-0.4.0-alpha.38.tgz -Algorithm SHA256).Hash.ToLowerInvariant()
439
446
  if ($actual -cne $expected) { throw 'Release checksum mismatch' }
440
447
  ```
441
448
 
@@ -8,7 +8,7 @@
8
8
  },
9
9
  "package": {
10
10
  "name": "dsh-github-copilot",
11
- "version": "0.4.0-alpha.37"
11
+ "version": "0.4.0-alpha.38"
12
12
  },
13
13
  "evidence": {
14
14
  "kind": "source-and-synthetic-test-inventory",
@@ -19,11 +19,12 @@
19
19
  "platforms": ["windows", "linux"],
20
20
  "node": ">=22.19.0",
21
21
  "dsh": {
22
- "release": "0.1.6-alpha.2",
23
- "tag": "dsh-v0.1.6-alpha.2",
24
- "commit": "ddefc45fbc7f8e46dd73185e68295696d1297887",
25
- "developmentRelease": "0.1.2-rc.1",
26
- "peerRange": "0.1.1-rc.2 || 0.1.2-rc.1 || 0.1.3-alpha.1 || 0.1.5-alpha.1 || 0.1.5-alpha.2 || 0.1.5-rc.1 || 0.1.5-rc.2 || 0.1.6-alpha.1 || 0.1.6-alpha.2",
22
+ "release": "0.2.0-rc.1",
23
+ "tag": "dsh-v0.2.0-rc.1",
24
+ "commit": "4878cdabd87d4041bdaff61d04c966883b9fd07a",
25
+ "developmentRelease": "0.2.0-rc.1",
26
+ "admittedReleases": ["0.2.0-rc.1"],
27
+ "peerRange": "0.2.0-rc.1",
27
28
  "baselines": [
28
29
  {
29
30
  "release": "0.1.1-rc.2",
@@ -168,6 +169,32 @@
168
169
  "managedProviderValidation": "synthetic-tagged-source-runtime",
169
170
  "resolvedProfileDiagnostics": "plugin-owned-empty-modelErrors",
170
171
  "runtimeTests": ["tests/preview-route.spec.ts", "tests/published-core.spec.ts", "tests/single-route.spec.ts", "tests/search-routing.spec.ts", "tests/routed-web.spec.ts", "tests/deepseek-search-fallback.spec.ts", "tests/tool-schema-compat.spec.ts", "tests/fixtures/alpha2-contracts-core.fixture.ts", "tests/fixtures/compaction-pressure-core.fixture.ts", "tests/remote-codec.spec.ts", "tests/dual-model-projection.spec.ts", "tests/fixtures/session-context-core.fixture.ts", "tests/fixtures/remote-core.fixture.ts"]
172
+ },
173
+ {
174
+ "release": "0.2.0-rc.1",
175
+ "tag": "dsh-v0.2.0-rc.1",
176
+ "commit": "4878cdabd87d4041bdaff61d04c966883b9fd07a",
177
+ "source": "https://github.com/deepseek-ai/deepseek-harness",
178
+ "desktopRelease": "0.2.0-rc.1",
179
+ "modelsUi": "provider-card",
180
+ "providerHeaders": "fetch-validated-discovery",
181
+ "strictModeCompat": "route-switch",
182
+ "fileContentHelper": "contentHasFile",
183
+ "agentCreation": "awaited-serial-agent-created",
184
+ "sessionHistory": "request-header-and-projections-no-new-sync-history",
185
+ "sessionFormatVersion": 4,
186
+ "strictRemoteCodecs": "create-factories-with-legacy-schema-bridge",
187
+ "roleChildDescriptorVersion": 3,
188
+ "roleChildCacheVersion": 2,
189
+ "roleChildHistory": "unknown-legacy-history-fail-closed",
190
+ "runtimeDependencies": "public-resolution-and-unload",
191
+ "clientSessionContext": "multiple-session-owner-isolation",
192
+ "evidenceScope": "unchanged-tagged-source-target",
193
+ "standaloneNpmArtifacts": "tested",
194
+ "desktopPackageSet": "not-materialized",
195
+ "managedProviderValidation": "synthetic-tagged-source-runtime",
196
+ "resolvedProfileDiagnostics": "plugin-owned-empty-modelErrors",
197
+ "runtimeTests": ["tests/preview-route.spec.ts", "tests/published-core.spec.ts", "tests/single-route.spec.ts", "tests/search-routing.spec.ts", "tests/routed-web.spec.ts", "tests/deepseek-search-fallback.spec.ts", "tests/tool-schema-compat.spec.ts", "tests/fixtures/alpha2-contracts-core.fixture.ts", "tests/fixtures/compaction-pressure-core.fixture.ts", "tests/remote-codec.spec.ts", "tests/dual-model-projection.spec.ts", "tests/fixtures/session-context-core.fixture.ts", "tests/fixtures/remote-core.fixture.ts"]
171
198
  }
172
199
  ],
173
200
  "packages": [
@@ -195,7 +222,7 @@
195
222
  "zod": "^4.4.3"
196
223
  },
197
224
  "sharedPeerDependencies": {
198
- "@deepseek-ai/dsh-authorization": "0.1.1-rc.2 || 0.1.2-rc.1 || 0.1.3-alpha.1 || 0.1.5-alpha.1 || 0.1.5-alpha.2 || 0.1.5-rc.1 || 0.1.5-rc.2 || 0.1.6-alpha.1 || 0.1.6-alpha.2",
225
+ "@deepseek-ai/dsh-authorization": "0.2.0-rc.1",
199
226
  "@deepseek-ai/schemastery": "^3.18.2"
200
227
  },
201
228
  "clientExternals": {
@@ -209,12 +236,14 @@
209
236
  {
210
237
  "id": "desktop-0.1.5-rc.2-installed-runtime",
211
238
  "sourceSha256": "210cacaf3842643ef6c124fd23cb3b67caf7008e97868c733550b56ba7a1e836",
212
- "packageCount": 241
239
+ "packageCount": 241,
240
+ "scope": "historical-ownership-only-not-current-compatibility"
213
241
  },
214
242
  {
215
243
  "id": "desktop-0.1.6-alpha.1-generated-package-set",
216
244
  "sourceSha256": "51b25ad67e6b0198edca0ec9baf8ebd06d26217dd33d1a2a4cce7e881382e6ea",
217
245
  "packageCount": 246,
246
+ "scope": "historical-ownership-only-not-current-compatibility",
218
247
  "descriptorStatus": "not-materialized"
219
248
  }
220
249
  ]
@@ -248,7 +277,7 @@
248
277
  {
249
278
  "id": "desktop-shared-package-ownership",
250
279
  "required": true,
251
- "evidenceScope": "packed-manifest-required-peer-and-client-external-closure-against-actual-0.1.5-and-generated-0.1.6-contracts",
280
+ "evidenceScope": "historical-shared-package-ownership-audit-plus-synthetic-current-contract; no-current-desktop-package-set-proof",
252
281
  "sourceMarkers": [
253
282
  {"file": "scripts/verify-desktop-package-graph.mjs", "marker": "verifyDesktopPackageGraph"},
254
283
  {"file": "scripts/verify-tarball.mjs", "marker": "desktopSharedGraphs"},
@@ -257,7 +286,7 @@
257
286
  {"file": "package.json", "marker": "\"external\": ["}
258
287
  ],
259
288
  "tests": [
260
- {"file": "tests/scripts/desktop-package-graph.test.mjs", "name": "packed manifest composes with the actual 0.1.5 and generated 0.1.6 Desktop shared graphs"},
289
+ {"file": "tests/scripts/desktop-package-graph.test.mjs", "name": "retains old Desktop shared graphs as ownership evidence, not current compatibility claims"},
261
290
  {"file": "tests/scripts/desktop-package-graph.test.mjs", "name": "shared graph gate rejects bundled, optional, incompatible, or unaudited host ownership"},
262
291
  {"file": "tests/scripts/desktop-package-graph.test.mjs", "name": "client externals stay outside the strict Node peer graph"}
263
292
  ]
@@ -274,7 +303,7 @@
274
303
  "tests": [
275
304
  {"file": "tests/scripts/search-composition.test.mjs", "name": "admits a stock top-level official service without mutating or exposing its config"},
276
305
  {"file": "tests/scripts/search-composition.test.mjs", "name": "includes home and launcher layers instead of ignoring a late web override"},
277
- {"file": "tests/scripts/search-composition.test.mjs", "name": "CLI rejects disposable root-only web without initialization, normalization or secret output"},
306
+ {"file": "tests/scripts/search-composition.test.mjs", "name": "preflight refuses nonempty profile root without initialization, normalization or secret output"},
278
307
  {"file": "tests/scripts/search-composition.test.mjs", "name": "real public parsers validate candidate layers and preserve every input file"},
279
308
  {"file": "tests/scripts/search-composition.test.mjs", "name": "rejects a web bundle ordered after the Copilot guard"}
280
309
  ]
@@ -876,12 +905,11 @@
876
905
  "id": "dsh-supported-baselines-fail-loud-guard",
877
906
  "required": true,
878
907
  "sourceMarkers": [
879
- {"file": "src/compatibility.ts", "marker": "peerRange: '0.1.1-rc.2 || 0.1.2-rc.1 || 0.1.3-alpha.1 || 0.1.5-alpha.1 || 0.1.5-alpha.2 || 0.1.5-rc.1 || 0.1.5-rc.2 || 0.1.6-alpha.1 || 0.1.6-alpha.2'"}
908
+ {"file": "src/compatibility.ts", "marker": "peerRange: '0.2.0-rc.1'"}
880
909
  ],
881
910
  "tests": [
882
- {"file": "tests/compatibility.spec.ts", "name": "retains the original three compatibility baselines"},
883
- {"file": "tests/compatibility.spec.ts", "name": "adds 0.1.6-alpha.2 without dropping earlier baselines or advancing development dependencies"},
884
- {"file": "tests/compatibility.spec.ts", "name": "declares exact alpha2 contract targets without claiming live or artifact validation"},
911
+ {"file": "tests/compatibility.spec.ts", "name": "admits only the exact current official release"},
912
+ {"file": "tests/compatibility.spec.ts", "name": "declares the current and retained exact contract targets without claiming live Desktop validation"},
885
913
  {"file": "tests/compatibility.spec.ts", "name": "accepts the supported DSH service contract"},
886
914
  {"file": "tests/compatibility.spec.ts", "name": "fails before startup when a required API is absent"}
887
915
  ]
@@ -921,7 +949,7 @@
921
949
  "tests": [
922
950
  {"file": "tests/single-route.spec.ts", "name": "keeps the native login flow while exposing only the account-driven provider"},
923
951
  {"file": "tests/single-route.spec.ts", "name": "discovers new IDs and reasoning metadata without a canonical model profile"},
924
- {"file": "tests/single-route.spec.ts", "name": "honors an explicit legacy-profile removal without deleting OAuth or rebuilding the route"},
952
+ {"file": "tests/single-route.spec.ts", "name": "honors explicit legacy-profile removal from settings without deleting OAuth"},
925
953
  {"file": "tests/authorization-controller.spec.ts", "name": "does not recreate an absent canonical profile during status or startup and auth reconciliation helpers"},
926
954
  {"file": "tests/authorization-controller.spec.ts", "name": "keeps absent-profile legacy journal conflicts visible instead of bypassing ownership review"}
927
955
  ]
@@ -118,28 +118,37 @@ There is no historical bulk backfill and no silent npm opt-out.
118
118
 
119
119
  ## Installation preflight still applies
120
120
 
121
- The native Desktop package manager remains the preferred interactive entry
122
- point when its registry access is permitted and available. After npm publication
123
- is verified, it accepts the exact `dsh-github-copilot@<version>` npm spec, not a
124
- Release URL or local tarball in that UI. This UI input restriction is not a
125
- blanket prohibition on maintaining the same profile through the supported CLI.
126
- Controlled CLI maintenance is also supported for Desktop-managed profiles under
127
- the checklist below. Neither entry point replaces the package's required
128
- `scripts/check-search-composition.mjs` preflight. A package lookup, preflight or
129
- successful installation is not proof of runtime activation or a model call.
130
-
131
- ## Controlled offline CLI maintenance
121
+ Desktop profiles must be managed through Desktop's native package manager.
122
+ The reserved `desktop` profile is not supported by DSH CLI plugin commands.
123
+ After npm publication is verified, the native manager accepts the exact
124
+ `dsh-github-copilot@<version>` npm spec, not a Release URL or local tarball.
125
+ The CLI procedure below applies only to standalone named profiles and is not a
126
+ Desktop fallback when registry access is blocked.
127
+
128
+ Neither entry point replaces the package's required
129
+ `scripts/check-search-composition.mjs` preflight. The official DSH 0.2
130
+ `composeProfile()` path writes the empty `cordis.yml` root before normal launch,
131
+ including when Desktop supplies an already resolved profile. Therefore the
132
+ preflight refuses a nonempty root as `NONEMPTY_DISPOSABLE_PROFILE_ROOT`; do not
133
+ install or start/restart that profile until the data has been preserved and an
134
+ officially supported migration has been established. A package lookup,
135
+ preflight or successful installation is not proof of runtime activation or a
136
+ model call.
137
+
138
+ ## Controlled offline CLI maintenance for standalone profiles
132
139
 
133
140
  This path installs this package's prebuilt, verified Release without requiring
134
141
  access to a blocked npm registry. It is not permission to bypass organizational registry restrictions:
135
142
  use only artifacts obtained through organizationally approved sources and
136
143
  already available dependency caches. A registry ban remains in force; offline
137
144
  installation does not repair TLS or prove that npm publication is healthy. The
138
- dual-channel **publication** policy above is unchanged.
145
+ dual-channel **publication** policy above is unchanged. **Do not use this path
146
+ for a Desktop-managed/reserved profile.**
139
147
 
140
148
  1. Obtain explicit installation approval for the exact version and profile.
141
- Resolve the actual DSH CLI, install anchor, `DSH_HOME` and profile directory;
142
- do not assume a shell shim points to the Desktop's current installation.
149
+ Resolve the standalone DSH CLI, install anchor, `DSH_HOME` and profile
150
+ directory; do not target Desktop's reserved `desktop` profile or assume a
151
+ shell shim points to the intended installation.
143
152
  2. Verify the original Release tarball with an independently trusted SHA-256,
144
153
  its package name/version and safe archive layout. Do not substitute a local
145
154
  build or repack an existing immutable Release. Extract only the verified
@@ -148,8 +157,8 @@ dual-channel **publication** policy above is unchanged.
148
157
  and install anchor, including any extra startup patches. Require
149
158
  `supported: true`; unknown, conflicting or unsupported composition is a stop,
150
159
  not permission to remove guards or rewrite the profile.
151
- 4. Keep one writer: do not run Desktop package updates and CLI installation
152
- concurrently. Take a private backup of installation metadata (package.json,
160
+ 4. Keep one writer: do not run concurrent package/profile updates. Take a
161
+ private backup of installation metadata (package.json,
153
162
  lockfile, bundle/patch configuration and relevant package-manager settings),
154
163
  record the current version, and retain a verified rollback artifact.
155
164
  Do not copy credential stores, `.env` files or browser storage. If ensuring
@@ -184,5 +193,6 @@ dual-channel **publication** policy above is unchanged.
184
193
  If installation fails, inspect the actual installed state before retrying or
185
194
  rolling back; a failed command is not proof that nothing changed. A rollback
186
195
  also needs reviewed, narrowly scoped metadata/dependency restoration. This
187
- documentation change does not rewrite installed or published historical docs,
188
- change machine-wide registry policy, or grant blanket approval for future updates.
196
+ procedure does not authorize Desktop profile management, rewrite installed or
197
+ published historical docs, change machine-wide registry policy, or grant blanket
198
+ approval for future updates.
@@ -0,0 +1,28 @@
1
+ # Official-first review: DSH 0.2.0-rc.1
2
+
3
+ ## Target and evidence boundary
4
+
5
+ Candidate plugin **`0.4.0-alpha.38`** adds official Core **`0.2.0-rc.1`**, tag commit [`4878cdabd87d4041bdaff61d04c966883b9fd07a`](https://github.com/deepseek-ai/deepseek-harness/commit/4878cdabd87d4041bdaff61d04c966883b9fd07a), as the current target while retaining every earlier compatibility pin. The independently observed Windows Desktop feed also identifies `0.2.0-rc.1`; its Desktop package set is not materialized in this checkout. Source/API qualification, npm package fixtures, and Desktop installation/runtime qualification are separate evidence.
6
+
7
+ This review inspected only the exact official tag and unchanged installed package artifacts. **Complete** means the cited public contract supports the named behavior, not that Desktop or a live service was qualified. **Partial** identifies both the official capability and the gap. **Unverified** means parity was not established, not that official support is absent. Decisions are **retain**, **migrate**, or **retire**. A retirement trigger is evidence for a separately reviewed change, never permission for automatic removal on a version bump.
8
+
9
+ ## Compatibility decisions
10
+
11
+ | Surface | Exact official contract and support | Decision | Remaining gap / retirement trigger |
12
+ |---|---|---|---|
13
+ | Copilot OAuth, credentials, catalog and ordinary model transport | The unchanged official [`llm-pi-ai` login/auth exports](https://github.com/deepseek-ai/deepseek-harness/tree/4878cdabd87d4041bdaff61d04c966883b9fd07a/packages/llm/llm-pi-ai/src) continue to own provider registration, OAuth grants, refresh and normal transport. | **Retain** the narrow public credential bridge and account-scoped route; do not add a second adapter or catalog. | The official path does not establish the companion's strict grant normalization, conditional authorization bootstrap, or authenticated per-account endpoint/capability metadata. Retire those bridges only after public official behavior and runtime acceptance preserve the same data and safety contracts. |
14
+ | Core settings access and invalidation | [`SettingsForms`](https://github.com/deepseek-ai/deepseek-harness/blob/4878cdabd87d4041bdaff61d04c966883b9fd07a/packages/settings/settings/src/index.ts) and its public [types](https://github.com/deepseek-ai/deepseek-harness/blob/4878cdabd87d4041bdaff61d04c966883b9fd07a/packages/settings/settings/src/types.ts) expose current descriptor/mutation APIs and the `settings/document-updated` event. | **Migrate** readers to the public descriptor path where legacy `get` is absent; **retain** a narrow legacy branch for older supported releases. | Retire the compatibility reader/listener only when the corresponding older Core pins are removed through an explicit support-policy change and the current namespace/redaction guarantees remain intact. |
15
+ | Volatile provider configuration | The public [`PiAiConfig` provider view](https://github.com/deepseek-ai/deepseek-harness/blob/4878cdabd87d4041bdaff61d04c966883b9fd07a/packages/llm/llm-pi-ai/src/config.ts) wraps provider storage; callers materialize it through `.get()` rather than object indexing. | **Migrate** the plugin's route builder to `.get()` and **retain** object support for older native layouts. | Do not infer registration from an empty volatile wrapper. Retire the legacy object branch only with removal of the older baselines and matching fixture evidence. |
16
+ | Tool results and message history | The current [`Message` contract](https://github.com/deepseek-ai/deepseek-harness/blob/4878cdabd87d4041bdaff61d04c966883b9fd07a/packages/llm/llm/src/message.ts) includes first-class `role: 'tool'` messages; older history can still contain nested tool-result blocks. | **Migrate** serialization to recognize both current and retained forms without rewriting source history. | Do not collapse tool messages into assistant text or change replay ownership. Retire legacy handling only after old stored histories are outside the declared support scope. |
17
+ | Agent creation and existing role-history restoration | The public [Agent lifecycle](https://github.com/deepseek-ai/deepseek-harness/blob/4878cdabd87d4041bdaff61d04c966883b9fd07a/packages/core/agent/src/index.ts) serializes and awaits `agent/created`; the event carries a creation source. | **Retain** compatibility-only projection restoration and test it through the awaited public lifecycle. | Retired role UI/settings/new-root behavior stays retired. Runtime policy enforcement and old-history recovery remain plugin-owned; never infer permission from a missing or malformed descriptor. |
18
+ | Remote and Client Gateway validation | Current [Typert codecs](https://github.com/deepseek-ai/deepseek-harness/blob/4878cdabd87d4041bdaff61d04c966883b9fd07a/packages/typert/protocol/src/types.ts) expose `create()` factories. The [Client Gateway](https://github.com/deepseek-ai/deepseek-harness/blob/4878cdabd87d4041bdaff61d04c966883b9fd07a/packages/api/gateway/src/client/index.ts) forwards parameter payloads without local parsing; strict input validation belongs at the registered Host boundary. Strict result codecs decode only when the descriptor publishes a decoder. | **Migrate** descriptor tests to current `create()` factories; **retain** the same strict Host codecs and legacy `.schema` helper bridge. | Client-side tests must not claim pre-transport input filtering or result validation the current Gateway does not promise. The exact-source Host fixture must continue to prove strict registered-boundary parsing. Retire the legacy bridge only after old Core consumers leave support. |
19
+ | Models UI and additive contribution | The official [Models Client](https://github.com/deepseek-ai/deepseek-harness/blob/4878cdabd87d4041bdaff61d04c966883b9fd07a/packages/client/ui-settings-models/src/client/index.ts) declares keyed `settings.models.provider-card` and list `settings.models.footer` slots. | **Retain** additive account/search controls and native model editing. | Slot existence is not account-management or search-policy parity. Retire a control only after equivalent official workflow, accessibility, ownership and lifecycle behavior pass Client/Desktop acceptance. |
20
+ | Web routing and search | Official Web exposes registered provider dispatch; the plugin's public facade captures an exact registered provider before routed search. | **Retain** fail-closed captured-registration dispatch and the explicit missing-seam diagnostic. | Never replace captured identity with an ID-only lookup, global model default or another Session's selection. Desktop/runtime and live provider behavior remain unverified. |
21
+ | Plugin installation and Desktop injection | The official Windows Desktop feed identifies release `0.2.0-rc.1`, but no installed Desktop package set or loaded runtime is present here. | **Retain** package entry-point/peer checks and document the independent Desktop boundary. | Do not claim successful injection, install, activation, authentication, model calls or UI behavior from Core source or npm package tests alone. |
22
+
23
+ ## Qualification ledger
24
+
25
+ - The release/tag and public source contracts above are pinned; the Core tree and installed dependencies were not modified.
26
+ - Local source build, focused tests, repository verifiers, exact-tag runtime fixtures and the complete gate must be reported separately after execution. Package-version metadata is not semantic or runtime proof.
27
+ - No real Copilot OAuth, model, search, live-profile change, Desktop install/restart, publication, push or pull request is part of this adaptation.
28
+ - Desktop package hashes/contents, packaged Electron activation, and loaded-version equivalence are **not verified** in this checkout. The observed feed release is not a materialized Desktop artifact.