dsh-github-copilot 0.1.0-alpha.17.dsh.0.2.2.rc.3 → 0.1.0-alpha.18.dsh.0.2.2.rc.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/AGENTS.md CHANGED
@@ -162,15 +162,15 @@ add model-ID routing rules, patch Core, or claim untested parity.
162
162
  When any later legacy detail in this guide conflicts with this confirmed scope,
163
163
  follow this section and the current acceptance criteria in #455/#456.
164
164
 
165
- The user clarified that the ordinary route should be DSH's native
166
- `github-copilot` provider, with only useful plugin enhancements through public
167
- APIs. Retire the separate managed route when native-route acceptance is met;
168
- do not preserve it solely to continue old conversations or create a history
165
+ The user clarified that the ordinary route is DSH's native
166
+ `github-copilot` provider, with useful plugin enhancements attached only through
167
+ public APIs. The production package registers no `github-copilot-preview`
168
+ provider; do not restore it to preserve old selections or create a history
169
169
  migration. Existing stored conversations, credentials and settings are not
170
- authorized for deletion or rewriting. Explicitly document that old managed
170
+ authorized for deletion or rewriting. Explicitly document that old preview
171
171
  route selections may become unavailable. Native model selection and actual
172
172
  subagent invocation must be verified on `github-copilot`, not inferred from
173
- managed-route tests. Record enhancements that cannot safely attach to native
173
+ legacy-route tests. Record enhancements that cannot safely attach to native
174
174
  APIs rather than patching Core or misrepresenting support.
175
175
 
176
176
  For official DSH `0.2.2-rc.3`, plugin `0.1.0-alpha.14.dsh.0.2.2.rc.3`
@@ -271,13 +271,13 @@ Refresh remains owned by native pi-ai `Models.getAuth()` and DSH
271
271
  If selection and canonical credential diverge after an external native sign-in,
272
272
  show an actionable mismatch and require explicit recovery; never auto-migrate.
273
273
 
274
- Keep the native UI and its canonical quota/search attribution. Existing
275
- `github-copilot-preview` behavior and Session account overrides remain
276
- separately plugin-owned legacy behavior; they are not required for native
277
- switching. Disposal removes only plugin registrations. Native model selections
278
- remain native; plugin-only model selections and explicit
279
- `web.searchProvider=github-copilot-hosted` need user-selected
280
- replacements before uninstall; missing configured Web backends return
274
+ Keep the native UI and its canonical quota/search attribution. The
275
+ `github-copilot-preview` adapter remains compatibility code but is not
276
+ registered by the production package entry. Session account overrides are not
277
+ evidence of native-provider behavior or a reason to register a second model
278
+ provider. Disposal removes only plugin registrations. Native model selections
279
+ remain native; explicit `web.searchProvider=github-copilot-hosted` needs a
280
+ user-selected replacement before uninstall. Missing configured Web backends return
281
281
  `WEB_PROVIDER_CONFIGURED_MISSING`, not automatic fallback. Uninstall leaves the
282
282
  last selected grant in the native canonical record. No automatic
283
283
  Settings/history migration or sign-out.
@@ -304,7 +304,7 @@ Additional plugin-owned `github-copilot/account-<opaque-id>` records are written
304
304
 
305
305
  Settings store only the opaque global account selector and explicit `sessionAccounts` rows. Missing/invalid selectors or records fail explicitly, without another-account fallback. Models manages account authorization and the global default; Credits may select an already authorized managed-route account for this Session's subsequent turns or restore global inheritance (#305/#318). An explicit choice equal to the default remains explicit. Freeze account ownership before request admission, holding mutation fences until native `turn/end`/disposal; later Session/default changes never redirect running steps, retries or search. Account-local credentials, metadata, quota, proof cancellation and native adapter composition must remain isolated. Keep one public adapter/controller registration, with no second wire/catalog or Core changes. Reauthorization/removal of a pinned record stays blocked; global-default selection may continue independently.
306
306
 
307
- Account selection shows the current account and a compact Switch dropdown with no account search, never a flat unbounded account list. Mark the current choice and scroll long lists internally; Add and saved-account reauthorization/removal remain in Models, not Credits. One Models Manage disclosure contains account management and cross-account exact-ID model preferences. Continuation settings belong beside account controls. Persist the initial default-on epoch and later global changes with path-level CAS; only unseeded Sessions born after a known epoch inherit it, never retroactively enroll existing/unknown/forked histories. Normal Client continuation uses only the persistent Session policy; no next-turn-only or temporary-recovery duration choices. Explicit-off account changes require persistent-enable/keep-off/cancel choices, then fresh account revision readback before CAS. Exact replay failures offer loss-disclosed persistent Enable/Cancel when off, diagnostics without repeated authorization when on. Missing policy evidence fails explicitly, never a temporary authorization fallback. Retain old next-turn/recovery strict Remote contracts and Host admission for compatibility; failure-evidence expiry does not disable the persistent policy. No automatic send/retry, history writes, private Settings navigation or inferred encrypted account origin. The approved synthetic mock and current navigation limit are documented in [account management](./docs/account-management-experience.md).
307
+ Account selection shows the current account and a compact Switch dropdown with no account search, never a flat unbounded account list. Mark the current choice and scroll long lists internally; Add and saved-account reauthorization/removal remain in Models, not Credits. One Models Manage disclosure contains account management and cross-account exact-ID model preferences. The former new-Session continuation default is not shown now that the managed route is retired; preserve existing settings and compatibility contracts. The historical default-on epoch and later changes use path-level CAS; only unseeded Sessions born after a known epoch inherit it, never retroactively enroll existing/unknown/forked histories. Normal Client continuation uses only the persistent Session policy; no next-turn-only or temporary-recovery duration choices. Explicit-off account changes require persistent-enable/keep-off/cancel choices, then fresh account revision readback before CAS. Exact replay failures offer loss-disclosed persistent Enable/Cancel when off, diagnostics without repeated authorization when on. Missing policy evidence fails explicitly, never a temporary authorization fallback. Retain old next-turn/recovery strict Remote contracts and Host admission for compatibility; failure-evidence expiry does not disable the persistent policy. No automatic send/retry, history writes, private Settings navigation or inferred encrypted account origin. The approved synthetic mock and current navigation limit are documented in [account management](./docs/account-management-experience.md).
308
308
 
309
309
  Use hidden volatile `sessionAccounts` with path-level SettingsForms CAS, readback and restart evidence. Session account Remotes use explicit viewed IDs, native Agent lookup and strict codecs, never automatic Client scope. Credits uses that Session's account for identity/quota, rejecting mismatched or late results. Historical Account is an additive assistant-actions disclosure beside native Usage, captured only after a real ordinary native chunk; bounded Host-lifetime evidence becomes unknown after restart/eviction and is never reconstructed from today's settings. No new durable events, history/default/model/Usage writes, automatic account fallback, replay deletion or message retry. See [the requirements and acceptance gates](./docs/copilot-accounts.md).
310
310
 
@@ -438,7 +438,7 @@ to remove the native provider or migrate settings.
438
438
  - Capabilities are `agentsList`, `sessionProjections`, `settingsCas`, `providerRegistry`, `defaultSelection`; `complete.sessions/defaultSelection/routes` describes evidence completeness, not migration approval. Effective selection uses pending projection, request-header config, then default only for genuinely empty Sessions with known projection state. Running `activeRequestSelection` is the latest recorded header, not proven in-flight LLM work. Native effective configuration and native/managed registration are separate flags.
439
439
  - This read invokes no auth status/model discovery, credentials or network and mutates no settings/Sessions. No normal UI/global current-model/search card is added. Nine ordinary authorization/model-preference Remotes retain their codec; the tenth migration Remote uses a separate strict `GitHubCopilotMigrationStatus` codec.
440
440
  - `historyScope: live-agents-only` excludes cold stored histories. Require operator acknowledgement that older conversations may need a new explicit selection later. Loaded version/structural capability self-reports are not full Desktop/Core byte attestation or an atomic cross-namespace guarantee; recheck immediately before CAS.
441
- - The planned `cloga/dsh-windows-ops` command `tools/migrate-copilot-managed-route.ps1` is separate config-only maintenance after release. V1 performs no automated Session/default writes, cold-history scan, plugin install, restart or full Desktop-baseline acceptance. Resolve selection blockers separately with explicit approval; never report this planned command or live migration as published/installed/completed without evidence.
441
+ - The earlier planned `cloga/dsh-windows-ops` command `tools/migrate-copilot-managed-route.ps1` is superseded: production no longer registers the managed model route, so provider-profile removal is not required. Never claim that this historical command or a live migration was published/installed/completed without evidence.
442
442
 
443
443
  ## Supported DSH seams
444
444
 
@@ -483,7 +483,7 @@ These pins document compatibility evidence. They do not authorize creating anoth
483
483
  - Authorization service: rc.1 Core provides it; the rc.2 web/headless profiles rely on this package's runtime dependency and conditional bootstrap.
484
484
  - Credentials: use record description/read/modify/delete APIs on the Host. Never read records in the browser.
485
485
  - Copilot grant schema: `type: oauth`, non-empty `refresh`/`access`, finite `expires`, optional non-empty `enterpriseUrl`, and optional deduplicated non-empty-string `availableModelIds`.
486
- - Settings: never recreate a missing `providers.github-copilot` profile. Existing native profiles remain user/Core-owned and require explicit migration before only the account-discovered route is listed.
486
+ - Settings: never recreate a missing `providers.github-copilot` profile. Existing native profiles remain user/Core-owned; production does not register a second account-discovered model route. Native model sync is an explicit, reviewed operation on an existing canonical profile.
487
487
  - Per-model API: do not assume stock Core honors a configured model.api. Verify the existing published behavior; where it cannot serve a model, use a plugin-local, exact-model alternative or report the limitation rather than patching Core.
488
488
  - Route activation: the dormant `llm-pi-ai` mount observes the profile and registers the route.
489
489
  - Client activation: package metadata injects DSH remotes and Models UI; `./client` mounts `./remote`.
@@ -516,13 +516,45 @@ For historical alpha.25, source markers, local rc.1-backed focused tests and fif
516
516
 
517
517
  ## Important-update release delivery
518
518
 
519
- - User-requested important updates include user-visible features, behavior fixes, compatibility fixes, and security or stability fixes. Their default delivery includes publication after a reviewed merge and green required CI; do not stop at a merged PR or ask a second time whether to release.
520
- - Explicit user restrictions such as code-only, review-only or do-not-release take precedence. Pure documentation and internal-only changes are not automatically release-bearing; they need an explicit release request if publication is desired. A task plan is not permission for an unrelated release.
519
+ - User-requested important plugin updates include user-visible features, behavior fixes, compatibility fixes, and security or stability fixes for plugin consumers. Their default delivery includes publication after a reviewed merge and green required CI; do not stop at a merged PR or ask a second time whether to release. Repository engineering features are not plugin features merely because they improve the project.
520
+ - Explicit user restrictions such as code-only, review-only or do-not-release take precedence. Pure documentation and internal-only changes are not automatically release-bearing; distributing them as plugin artifacts requires an explicit request for that artifact, not a generic delivery instruction. A task plan is not permission for an unrelated release.
521
521
  - Plan version alignment with the implementation PR whenever possible. If the prepared version/tag is unused and aligned, release it; otherwise prepare the next appropriate SemVer version through the normal PR path. Preserve the prerelease channel unless promotion is explicitly requested. Any additional version PR follows the same required review/CI and branch protection, without a separate merge-approval prompt.
522
522
  - Check all required CI, tag rules and package/archive checks. Create a fresh annotated tag only on the verified merged revision, let the protected Release workflow publish, and verify the non-draft Release, intended prerelease flag, tag/commit, assets and SHA-256. Never bypass failing CI, move a tag or substitute an unverified local archive.
523
523
  - A release-bearing update is not fully delivered until the published Release URL, verified version/commit/assets/checksum and npm version/SRI are reported. If CI, permissions or network prevents either channel, report partial delivery and the exact pending step; never describe merged-only or GitHub-only work as fully delivered.
524
524
  - This standing release authorization does not authorize profile installation, sign-out, worktree checkout or interruption of running Sessions. Keep published, installed-on-disk and loaded-runtime status separate; a session-interrupting restart still requires explicit acknowledgement.
525
525
 
526
+ ### Classify delivery before packaging (#502)
527
+
528
+ Choose the task's consumer impact before editing versions, installation URLs or
529
+ package contents. Record the classification and concrete rationale in the PR's
530
+ `Release delivery` section:
531
+
532
+ | Classification | Completion and artifact boundary |
533
+ | --- | --- |
534
+ | `repository-only` | Agent guidance, CI, tests, documentation governance and unshipped development tools complete at reviewed merge and green required CI. Keep the plugin version and package whitelist unchanged; no plugin release or local upgrade is needed. |
535
+ | `plugin-update` | An actual plugin runtime, compatibility or release-significant consumer-package change follows the important-update release gates above. A version/baseline/whitelist edit alone is not evidence of such a change. |
536
+ | `explicit-plugin-artifact` | An explicit request to distribute an engineering artifact as a plugin package may authorize that separate delivery. Record the actual artifact-specific request under `Authorization`; generic "deliver/publish" instructions or release-status questions are not that authorization. A version-only follow-through PR may instead cite the already reviewed and authorized plugin update; it needs no second approval. |
537
+ | `release-recovery` | Repair publication infrastructure or reconcile an already authorized version without a new version or changed consumer payload. Verify that existing release's outcome; do not describe reconciliation as a new plugin upgrade. |
538
+
539
+ Never add repository tools, fixtures or guides to `package.json.files`, or bump a
540
+ version, merely to make an engineering task releasable. If an intended change
541
+ touches an already shipped executable or other release-significant file, preserve the existing release-policy gate:
542
+ separate/defer that artifact change or establish its real consumer release scope,
543
+ never relabel it repository-only to bypass the gate. Preserve historical releases,
544
+ tags and package contents; this rule does not authorize unpublishing or repacking.
545
+ Documentation-only source edits, including packaged guides, may wait for the next
546
+ independently justified version without changing any already published bytes.
547
+
548
+ The existing PR `documentation-impact` check also checks this declaration against
549
+ the actual base/head manifests and important-file diff. It rejects repository-only
550
+ package changes and metadata-only manufactured plugin updates, and requires a
551
+ reviewable artifact-specific authorization statement for the explicit exception.
552
+ These are consistency checks, not proof of semantic impact or user consent; an
553
+ agent or human must review the rationale and actual request without adding a new
554
+ human-only approval gate. Report repository delivery, plugin publication,
555
+ installed-on-disk and loaded-runtime status separately. No runtime benefit means
556
+ no recommendation to install or restart merely because a new package exists.
557
+
526
558
  ## Installation-agent PowerShell practice
527
559
 
528
560
  Installation agents using the DSH `pwsh` tool must follow these rules:
package/CHANGELOG.md CHANGED
@@ -5,6 +5,13 @@ release tags do not update this file after publication. Check the exact
5
5
  [GitHub Release](https://github.com/cloga/dsh-github-copilot/releases) and npm
6
6
  version separately rather than treating an old `prepared` label as current status.
7
7
 
8
+ ## 0.1.0-alpha.18.dsh.0.2.2.rc.3 (prepared)
9
+
10
+ - Stop registering the separate `github-copilot-preview` model provider while retaining account metadata for explicitly confirmed native model sync (#500).
11
+ - Keep native provider settings, account grants and conversation history unchanged. Existing preview-route selections may require an explicit native model selection.
12
+ - If no native Copilot provider is configured, add one in DSH Models; the plugin does not create its profile.
13
+ - Remove the retired route's new-Session continuation default from Models without rewriting saved settings.
14
+
8
15
  ## 0.1.0-alpha.17.dsh.0.2.2.rc.3 (prepared)
9
16
 
10
17
  - Remove Local diagnostics collection, controls, storage access, Remotes and the offline analyzer (#499).
package/CONTRIBUTING.md CHANGED
@@ -57,6 +57,18 @@ GitHub Releases and npm are the default distribution channels for every new vers
57
57
 
58
58
  Important user-requested features, behavior fixes, compatibility fixes, and security or stability fixes include release follow-through by default after a reviewed merge and green required CI. Do not stop at the merged PR or ask for a second release confirmation. User instructions limiting delivery to code/review or forbidding publication take precedence; documentation-only, internal-only and unrelated releases are not implicitly authorized. Follow the [important-update delivery rule](./AGENTS.md#important-update-release-delivery).
59
59
 
60
+ First classify actual plugin-consumer impact in the PR's `Release delivery`
61
+ section. Repository engineering (agent guidance, CI, tests and unshipped tools)
62
+ completes at reviewed merge and green CI, without a plugin version or local
63
+ upgrade. Do not expand the package whitelist merely to manufacture a release.
64
+ An engineering artifact needs an explicit plugin-artifact distribution request,
65
+ not a generic "publish" instruction or status question. Existing shipped-file
66
+ gates still apply to executables and other release-significant files;
67
+ documentation-only source edits may wait for the next justified release.
68
+ Version-only follow-through of an already authorized plugin update can cite that
69
+ reviewed update under `explicit-plugin-artifact` without another approval prompt.
70
+ See [delivery classification](./AGENTS.md#classify-delivery-before-packaging-502).
71
+
60
72
  Prepare version alignment in the implementation PR. Important runtime or delivery changes fail the `release-ready` PR check unless `package.json` is strictly newer than the base and `deployment-baseline.json` plus both README install URLs agree. Retain the current prerelease channel unless promotion is requested. Docs/tests-only changes may keep the current version. Never move or reuse a tag. Local installation, sign-out and worktree checkout still need explicit approval; restarting active Sessions requires acknowledgement of the interruption.
61
73
 
62
74
  After the release-ready PR merges, the successful main CI run calls the reusable Release workflow on that exact SHA. It creates or reconciles the annotated version tag and a draft-first Release, rebuilds and verifies the package, writes and verifies `SHA256SUMS`, checks remote asset digests, and only then publishes an immutable Release. Identical reruns reconcile safely; conflicting tags, releases or bytes fail closed. A tag created by `GITHUB_TOKEN` does not trigger a second workflow, so publication occurs in the gated main workflow rather than depending on recursive tag events. Do not hand-upload a replacement or bypass failed CI.
package/README.md CHANGED
@@ -73,31 +73,33 @@ After the exact compatible release is available and verified, download its
73
73
  original asset and checksum in an empty directory:
74
74
 
75
75
  ```sh
76
- curl -fLO https://github.com/cloga/dsh-github-copilot/releases/download/v0.1.0-alpha.17.dsh.0.2.2.rc.3/dsh-github-copilot-0.1.0-alpha.17.dsh.0.2.2.rc.3.tgz
77
- curl -fLO https://github.com/cloga/dsh-github-copilot/releases/download/v0.1.0-alpha.17.dsh.0.2.2.rc.3/SHA256SUMS
76
+ curl -fLO https://github.com/cloga/dsh-github-copilot/releases/download/v0.1.0-alpha.18.dsh.0.2.2.rc.3/dsh-github-copilot-0.1.0-alpha.18.dsh.0.2.2.rc.3.tgz
77
+ curl -fLO https://github.com/cloga/dsh-github-copilot/releases/download/v0.1.0-alpha.18.dsh.0.2.2.rc.3/SHA256SUMS
78
78
  sha256sum --check SHA256SUMS
79
79
  ```
80
80
 
81
81
  For the `web` profile, install the same Release asset:
82
82
 
83
83
  ```sh
84
- dsh plugin --profile web add https://github.com/cloga/dsh-github-copilot/releases/download/v0.1.0-alpha.17.dsh.0.2.2.rc.3/dsh-github-copilot-0.1.0-alpha.17.dsh.0.2.2.rc.3.tgz
84
+ dsh plugin --profile web add https://github.com/cloga/dsh-github-copilot/releases/download/v0.1.0-alpha.18.dsh.0.2.2.rc.3/dsh-github-copilot-0.1.0-alpha.18.dsh.0.2.2.rc.3.tgz
85
85
  ```
86
86
 
87
87
  Choose the intended profile explicitly. Then:
88
88
 
89
- 1. In **Settings → Models → GitHub Copilot**, sign in with GitHub.
90
- 2. Choose an account-available Copilot model in the native DSH model picker.
91
- 3. For subagents, use the native DSH model selection flow. Compatibility is
89
+ 1. In **Settings → Models**, add the native GitHub Copilot provider if it is
90
+ not already configured; the plugin does not create that profile.
91
+ 2. Use the GitHub Copilot account panel to sign in with GitHub.
92
+ 3. Choose an account-available Copilot model in the native DSH model picker.
93
+ 4. For subagents, use the native DSH model selection flow. Compatibility is
92
94
  limited to account-advertised and tested protocol capabilities.
93
95
 
94
96
  No manually defined Copilot model, pasted token, external gateway, or
95
97
  `copilot2api` service is required. Account and model availability are separate:
96
98
  successful sign-in does not guarantee every model or capability is available.
97
- The plugin's account-discovered models and capabilities apply to the
98
- `github-copilot-preview` route. DSH's native `github-copilot` route uses its
99
- own bundled or configured catalog; the two routes do not automatically share
100
- model discovery.
99
+ The plugin does not register a second `github-copilot-preview` model provider.
100
+ Account-discovered model metadata is available for an explicitly reviewed sync
101
+ into the native `github-copilot` model list; discovery alone does not change the
102
+ native catalog or model selection.
101
103
 
102
104
  To copy enabled models from the verified account used by the native provider into an existing
103
105
  native provider, open **Manage → Model preferences**, review the displayed
@@ -107,11 +109,9 @@ account snapshot without forcing discovery; if it is unavailable, use
107
109
  **Refresh models**. This one-time snapshot replaces only
108
110
  `llm-pi-ai.providers.github-copilot.models` with Settings CAS and readback.
109
111
  The nonempty saved list replaces the native built-in catalog and remains after
110
- the plugin is unloaded or uninstalled. Copying model settings does not transfer
111
- the managed route's permission-field filtering to native requests, nor prove
112
- that supplier calls will succeed. Neither route checks the projected image MIME
113
- against the account model's format list before dispatch.
114
- The managed route also uses the native Goal update schema without rewriting it.
112
+ the plugin is unloaded or uninstalled. Copying model settings does not change
113
+ the native adapter's request behavior or prove that supplier calls will
114
+ succeed. Native requests retain DSH's provider-owned transport and semantics.
115
115
  Models with unproven or incompatible native catalog protocols, unknown or
116
116
  narrower server input caps, unknown context or vision support, or unknown or
117
117
  unsupported reasoning controls are skipped rather than guessed.
@@ -136,8 +136,12 @@ OAuth grant as a saved account. In-progress requests are not redirected, and
136
136
  the operation does not change model selections, provider settings or history.
137
137
  Account switching does not change the native provider's bundled/configured
138
138
  model catalog, which is not guaranteed to filter models by account entitlement.
139
- The existing `github-copilot-preview` route remains a separate plugin-owned
140
- model route; it is not required for native account switching.
139
+ The plugin does not add a separate Copilot model route. Existing
140
+ `github-copilot-preview` selections are not migrated and may become unavailable;
141
+ stored settings and conversation history remain unchanged. Legacy
142
+ preview-only Session account overrides and continuation controls do not apply
143
+ to native model calls. The old new-Session continuation default is no longer
144
+ shown; existing settings are preserved.
141
145
  Starting the plugin or completing sign-in does not automatically repair the
142
146
  native provider's settings.
143
147
  The plugin registers optional `github-copilot-hosted` search in DSH's existing
@@ -207,11 +211,11 @@ applied to the canonical credential slot. Removing the plugin is not signing
207
211
  out; explicit sign-out or removal of that authorization is a different action
208
212
  and can affect native login.
209
213
 
210
- Plugin-only model selections do not become native automatically. Before removal,
211
- explicitly select native models for Sessions/defaults using
212
- `github-copilot-preview`. If Web is set to `github-copilot-hosted`, select another
213
- available backend in native Web settings first. Removing the plugin does not
214
- rewrite Web settings: a retained missing backend produces
214
+ Existing `github-copilot-preview` model selections are not migrated and may
215
+ become unavailable; explicitly select a native model where needed. If Web is
216
+ set to `github-copilot-hosted`, select another available backend in native Web
217
+ settings before removing the plugin. Removing the plugin does not rewrite Web
218
+ settings: a retained missing backend produces
215
219
  `WEB_PROVIDER_CONFIGURED_MISSING`, not an automatic fallback. Additional-account
216
220
  management and plugin-specific search require the plugin; the last selected
217
221
  native OAuth grant remains in DSH's canonical credential record.
package/README.zh.md CHANGED
@@ -61,37 +61,39 @@ node scripts/select-core-release.mjs 0.2.2-rc.3
61
61
  精确兼容版本发布且通过验证后,在空目录下载原始制品并校验:
62
62
 
63
63
  ```sh
64
- curl -fLO https://github.com/cloga/dsh-github-copilot/releases/download/v0.1.0-alpha.17.dsh.0.2.2.rc.3/dsh-github-copilot-0.1.0-alpha.17.dsh.0.2.2.rc.3.tgz
65
- curl -fLO https://github.com/cloga/dsh-github-copilot/releases/download/v0.1.0-alpha.17.dsh.0.2.2.rc.3/SHA256SUMS
64
+ curl -fLO https://github.com/cloga/dsh-github-copilot/releases/download/v0.1.0-alpha.18.dsh.0.2.2.rc.3/dsh-github-copilot-0.1.0-alpha.18.dsh.0.2.2.rc.3.tgz
65
+ curl -fLO https://github.com/cloga/dsh-github-copilot/releases/download/v0.1.0-alpha.18.dsh.0.2.2.rc.3/SHA256SUMS
66
66
  sha256sum --check SHA256SUMS
67
67
  ```
68
68
 
69
69
  例如安装到 `web` profile:
70
70
 
71
71
  ```sh
72
- dsh plugin --profile web add https://github.com/cloga/dsh-github-copilot/releases/download/v0.1.0-alpha.17.dsh.0.2.2.rc.3/dsh-github-copilot-0.1.0-alpha.17.dsh.0.2.2.rc.3.tgz
72
+ dsh plugin --profile web add https://github.com/cloga/dsh-github-copilot/releases/download/v0.1.0-alpha.18.dsh.0.2.2.rc.3/dsh-github-copilot-0.1.0-alpha.18.dsh.0.2.2.rc.3.tgz
73
73
  ```
74
74
 
75
75
  请明确选择目标 profile,然后:
76
76
 
77
- 1. 打开**设置 → 模型 → GitHub Copilot**,使用 GitHub 登录。
78
- 2. 在 DSH 原生模型选择器中选择该账号实际可用的 Copilot 模型。
79
- 3. 子代理使用 DSH 原生模型选择流程;兼容范围以账号公布且经过测试的协议能力为准。
77
+ 1. 打开**设置 → 模型**;如果尚未配置原生 GitHub Copilot provider,请先添加。
78
+ 插件不会自动创建此 profile。
79
+ 2. 在 GitHub Copilot 账号面板中使用 GitHub 登录。
80
+ 3. 在 DSH 原生模型选择器中选择该账号实际可用的 Copilot 模型。
81
+ 4. 子代理使用 DSH 原生模型选择流程;兼容范围以账号公布且经过测试的协议能力为准。
80
82
 
81
83
  无需手工定义 Copilot 模型、粘贴 token、使用外部网关或安装
82
84
  `copilot2api`。账号登录成功不代表所有模型及其能力都可用。
83
- 插件自动发现的账号模型及能力适用于 `github-copilot-preview` 路线;DSH 原生
84
- `github-copilot` 路线使用自己的内置或用户配置目录,两条路线不会自动共享模型发现结果。
85
+ 插件不再注册第二个 `github-copilot-preview` 模型 provider。
86
+ 自动发现的账号模型元数据可用于显式审核后同步到原生 `github-copilot` 模型列表;
87
+ 仅发现元数据不会更改原生目录或模型选择。
85
88
 
86
89
  如需将原生 provider 所用的已验证账号的启用模型复制到已配置的原生 provider,请打开
87
90
  **Manage → Model preferences**,查看显示的新增、更新、移除、跳过项和每次请求的输出
88
91
  默认值,然后选择 **Sync models**。页面使用当前已验证的账号快照准备这些信息,不强制
89
92
  重新发现;如果快照不可用,请使用 **Refresh models**。此显式单次快照只通过
90
93
  Settings CAS 和回读替换 `llm-pi-ai.providers.github-copilot.models`。原生 profile
91
- 中保存的非空列表会替代原生内置目录,卸载或停用插件后仍然保留。复制模型设置不会将
92
- 托管路线的权限参数过滤迁移到原生请求,也不能证明供应商调用成功。两条路线均不会在
93
- 发送前将实际投影的图片 MIME 与账号模型的格式清单进行对照检查。
94
- 托管路线也直接使用原生 Goal 更新 schema,不再改写。
94
+ 中保存的非空列表会替代原生内置目录,卸载或停用插件后仍然保留。复制模型设置不会
95
+ 更改原生适配器的请求行为,也不能证明供应商调用成功。原生请求仍由 DSH provider
96
+ 拥有传输和请求语义。
95
97
  无法证明或与原生目录不兼容的协议、未知或更窄的服务端输入上限、未知上下文或图像支持,
96
98
  以及未知或不支持的推理控制会被跳过,不会猜测。缺少原生目录兼容性基线的新 Completions 和
97
99
  Anthropic 模型也会被跳过;已有目录模型保留原生兼容性。只有账号明确支持 PNG、JPEG、WebP、GIF 四种原生请求图像格式时,
@@ -106,8 +108,10 @@ Anthropic 模型也会被跳过;已有目录模型保留原生兼容性。只
106
108
  会将该账号应用到 DSH canonical 凭据槽 `llm-pi-ai/github-copilot`,供此 profile
107
109
  后续的原生请求使用。首次切换会将原有原生 OAuth 授权保留为已保存账号。
108
110
  切换不会重定向正在进行的请求,也不会更改模型选择、provider 设置或历史。
109
- 原生 provider 的内置/配置模型目录不会因此按账号权限过滤。现有
110
- `github-copilot-preview` 仍是独立的插件模型路线,但原生账号切换不依赖它。
111
+ 原生 provider 的内置/配置模型目录不会因此按账号权限过滤。插件不再添加单独的 Copilot
112
+ 模型路线。已有的 `github-copilot-preview` 选择不会自动迁移,可能变为不可用;已保存的设置和
113
+ 对话历史保持不变。旧 preview 路线专用的 Session 账号覆盖和续接控件不适用于原生模型请求;
114
+ 旧的“新 Session 续接默认项”不再显示,已有设置会保留。
111
115
  启动插件或完成登录时,不会自动修复原生 provider 设置。
112
116
  插件在 DSH 现有 Web 服务中注册可选的 `github-copilot-hosted` 搜索后端。
113
117
  请在原生 Web 设置中明确选择,并按需启用原生搜索工具;安装不会改变默认后端。
@@ -160,9 +164,9 @@ Local diagnostics 已移除;现有诊断数据和设置均不改动。若旧
160
164
  原生 **GitHub Copilot** 继续使用最近一次明确应用到 canonical 凭据槽的账号。卸载不是退出登录;
161
165
  显式退出或移除原始授权是另一项操作,会影响原生登录。
162
166
 
163
- 依赖插件的选择不会自动变成原生选择。卸载前,请明确将使用 `github-copilot-preview`
164
- 的 Session/默认模型切回原生模型。如果 Web 选中了 `github-copilot-hosted`,
165
- 请先在原生 Web 设置中选择其他可用后端。卸载不会改写 Web 设置;
167
+ 已有的 `github-copilot-preview` 模型选择不会自动迁移,可能变为不可用;需要时请显式选择原生模型。
168
+ 如果 Web 选中了 `github-copilot-hosted`,请先在原生 Web 设置中选择其他可用后端。
169
+ 卸载不会改写 Web 设置;
166
170
  保留已缺失的后端会返回 `WEB_PROVIDER_CONFIGURED_MISSING`,不会自动回退。
167
171
  附加账号管理和插件专属搜索仍然依赖插件;最近选中的原生 OAuth 授权会保留在 DSH canonical 凭据记录中。
168
172
 
@@ -8,14 +8,14 @@
8
8
  },
9
9
  "package": {
10
10
  "name": "dsh-github-copilot",
11
- "version": "0.1.0-alpha.17.dsh.0.2.2.rc.3"
11
+ "version": "0.1.0-alpha.18.dsh.0.2.2.rc.3"
12
12
  },
13
13
  "releaseLines": [
14
14
  { "core": "0.2.0-rc.2", "version": "0.4.2-alpha.15", "status": "published" },
15
15
  { "core": "0.2.1-alpha.4", "version": "0.4.2-alpha.16", "status": "published" },
16
16
  { "core": "0.2.1-alpha.5", "version": "0.1.0-alpha.2.dsh.0.2.1.alpha.5", "status": "published" },
17
17
  { "core": "0.2.1-rc.3", "version": "0.1.0-alpha.5.dsh.0.2.1.rc.3", "status": "published" },
18
- { "core": "0.2.2-rc.3", "version": "0.1.0-alpha.17.dsh.0.2.2.rc.3", "status": "pending" }
18
+ { "core": "0.2.2-rc.3", "version": "0.1.0-alpha.18.dsh.0.2.2.rc.3", "status": "pending" }
19
19
  ],
20
20
  "evidence": {
21
21
  "kind": "source-and-synthetic-test-inventory",
@@ -647,18 +647,19 @@
647
647
  {
648
648
  "id": "native-subagent-copilot-invocation",
649
649
  "required": true,
650
- "evidenceScope": "synthetic-two-account-tagged-source-production-host-child-invocation-with-default-switch-not-live-or-explicit-child-account-policy",
650
+ "evidenceScope": "synthetic-two-account-tagged-source-native-provider-child-invocation-with-default-switch-and-explicit-model-configuration-not-live-or-session-account-policy",
651
651
  "sourceMarkers": [
652
652
  {"file": "scripts/verify-tagged-core.mjs", "marker": "tests/fixtures/subagent-copilot-core.fixture.ts"},
653
653
  {"file": ".github/workflows/ci.yml", "marker": "['subagent-copilot-core.fixture.ts',1],['native-subagent-copilot-core.fixture.ts',3]"},
654
654
  {"file": ".github/workflows/ci.yml", "marker": "s.assertionResults.some(t=>t.status!=='passed')"},
655
655
  {"file": "tests/fixtures/native-subagent-copilot-core.fixture.ts", "marker": "it.each(['absent', 'enabled', 'disposed'] as const)"},
656
656
  {"file": "tests/fixtures/subagent-copilot-core.fixture.ts", "marker": "await ctx.plugin(GitHubCopilotPlugin,"},
657
- {"file": "tests/fixtures/subagent-copilot-core.fixture.ts", "marker": "accounts.turns.current(child.session)"},
657
+ {"file": "tests/fixtures/subagent-copilot-core.fixture.ts", "marker": "COPILOT_ACCOUNTS_BUSY"},
658
658
  {"file": "src/session-accounts-host.ts", "marker": "class SessionAccountsHost"}
659
659
  ],
660
660
  "tests": [
661
- {"file": "tests/fixtures/subagent-copilot-core.fixture.ts", "name": "routes concurrently authorized native children to their selected Copilot models and efforts"},
661
+ {"file": "tests/fixtures/subagent-copilot-core.fixture.ts", "name": "routes native Copilot children across a confirmed account switch"},
662
+ {"file": "tests/fixtures/native-subagent-copilot-core.fixture.ts", "name": "selects and concurrently dispatches native Copilot subagents with the plugin %s"},
662
663
  {"file": "tests/session-accounts-host.spec.ts", "name": "freezes a running turn while allowing later Session/default choices independently"},
663
664
  {"file": "tests/session-accounts-host.spec.ts", "name": "rejects stale CAS and missing accounts instead of persisting a fallback"}
664
665
  ]
@@ -1449,17 +1450,19 @@
1449
1450
  ]
1450
1451
  },
1451
1452
  {
1452
- "id": "single-managed-route-native-oauth",
1453
+ "id": "native-route-account-metadata",
1453
1454
  "required": true,
1454
1455
  "sourceMarkers": [
1455
1456
  {"file": "src/authorization-controller.ts", "marker": "current !== undefined && providerSupportsStrictMode(current) !== false"},
1456
- {"file": "src/preview-route.ts", "marker": "displayName: 'GitHub Copilot (multi-account)'"},
1457
+ {"file": "src/index.ts", "marker": "registerLegacyProvider: false"},
1458
+ {"file": "src/preview-route.ts", "marker": "registerLegacyProvider = false"},
1457
1459
  {"file": "src/client.ts", "marker": "GitHubCopilotAccountSurface"}
1458
1460
  ],
1459
1461
  "tests": [
1460
- {"file": "tests/single-route.spec.ts", "name": "keeps the native login flow while exposing only the account-driven provider"},
1461
- {"file": "tests/single-route.spec.ts", "name": "discovers new IDs and reasoning metadata without a canonical model profile"},
1462
- {"file": "tests/single-route.spec.ts", "name": "honors explicit legacy-profile removal from settings without deleting OAuth"},
1462
+ {"file": "tests/single-route.spec.ts", "name": "keeps the native login flow without registering a second model provider"},
1463
+ {"file": "tests/single-route.spec.ts", "name": "discovers account model metadata without registering a model provider"},
1464
+ {"file": "tests/single-route.spec.ts", "name": "handles model preference updates without registering a legacy provider"},
1465
+ {"file": "tests/single-route.spec.ts", "name": "does not replace a removed native profile with the retired provider"},
1463
1466
  {"file": "tests/authorization-controller.spec.ts", "name": "does not recreate an absent canonical profile during status or explicit reconciliation"},
1464
1467
  {"file": "tests/authorization-controller.spec.ts", "name": "keeps absent-profile legacy journal conflicts visible instead of bypassing ownership review"}
1465
1468
  ]
@@ -1,5 +1,10 @@
1
1
  # Copilot account management and continuation experience
2
2
 
3
+ > The managed `github-copilot-preview` route and its continuation controls are
4
+ > retired in production. The historical Models new-Session default is no longer
5
+ > shown; existing settings and histories are preserved. Native account
6
+ > switching is profile-wide.
7
+
3
8
  Approved account switching reference: [dropdown mock](./mockups/copilot-account-dropdown.html).
4
9
  The [Chat account selection mock](./mockups/copilot-chat-account-selection.html)
5
10
  supersedes its Chat menu: only configured accounts appear in the list, with
@@ -59,8 +64,8 @@ retried by enabling it.
59
64
  See the [synthetic composer capture](./images/copilot-session-continuation.png);
60
65
  it shows the control's appearance, not a live Session or policy read.
61
66
 
62
- The separate **New Session continuation default** is managed in Models under
63
- GitHub Copilot → Manage. Full account management belongs in Models; show a
67
+ Earlier releases placed the separate **New Session continuation default** in
68
+ Models; it is no longer shown. Full account management belongs in Models; show a
64
69
  "Manage accounts and models" entry only with a working public navigation
65
70
  callback. Do not show a disabled link or unavailable-navigation paragraph.
66
71
  Opening and closing Settings must not discard the composer draft or change the
@@ -75,7 +80,7 @@ Copilot contribution shows current default identity, model status, cache age and
75
80
  one Manage button. Manage expands:
76
81
 
77
82
  - Account management: current default account, Switch dropdown/add, identity
78
- refresh, reauthorization, guarded removal, and new-Session continuation default.
83
+ refresh, reauthorization, and guarded removal.
79
84
  - Model preferences: cross-account shared exclusions, model search and filters,
80
85
  account-specific availability, discovery diagnostics and model refresh.
81
86
 
@@ -4,6 +4,12 @@
4
4
  > at the time, not current setup requirements or release status. Start with
5
5
  > [AGENTS.md](../AGENTS.md), the [current README](../README.md) and
6
6
  > [model compatibility acceptance](./model-compatibility-acceptance.md).
7
+ >
8
+ > **Route update:** the later confirmed native-only product scope supersedes
9
+ > the #93/#99/#101 managed-route migration plan below. Production adds no second
10
+ > model provider; no profile cleanup or settings/history migration is required.
11
+ > Existing `github-copilot-preview` selections may be unavailable and are not
12
+ > rewritten. See [retiring the duplicate route](./single-route-migration.md).
7
13
 
8
14
  ## Current documentation-impact follow-up
9
15
 
@@ -21,6 +27,27 @@ whether the chosen documents are relevant, correct or complete. Reviewers must
21
27
  compare source behavior, limitations and evidence with every affected document.
22
28
  Retain explicitly labeled historical records rather than rewriting old results.
23
29
 
30
+ ## Current delivery-classification follow-up
31
+
32
+ Repository engineering delivery is distinct from plugin publication and local
33
+ installation. For the same assessed PR paths, `documentation-impact` also reads
34
+ `## Release delivery`: choose `repository-only`, `plugin-update`,
35
+ `explicit-plugin-artifact` or `release-recovery`, with `Details` of at least 20
36
+ characters. Repository-only and recovery declarations reject important-file or
37
+ manifest changes. Plugin-update declarations require more than version, baseline
38
+ and package-whitelist edits. An explicit artifact declaration additionally needs
39
+ an `Authorization` statement identifying the artifact-specific request, or the
40
+ already reviewed/authorized plugin update for version-only follow-through.
41
+ The latter preserves standing release permission without a new approval prompt.
42
+
43
+ The gate reads actual base/head manifests even when documentation behavior is
44
+ declared unchanged. It preserves the existing shipped-file/version policy and
45
+ does not infer runtime benefit, authenticate consent or prove the justification.
46
+ Review those semantics against the user's request. Repository-only work ends at
47
+ reviewed merge and required CI: no new plugin version, installation or restart.
48
+ Existing released artifacts remain immutable; do not remove old packaged tools
49
+ as an incidental cleanup. See [the delivery rules](../AGENTS.md#classify-delivery-before-packaging-502).
50
+
24
51
  Tracking: [#73](https://github.com/cloga/dsh-github-copilot/issues/73). Audited baseline: `d9d0954` (2026-09-05). This is an evidence inventory, not a blanket certification of live Copilot behavior.
25
52
 
26
53
  ## Scope and method
@@ -77,7 +104,7 @@ The provider integration introduced in `0.4.0-alpha.5` replaces the older indepe
77
104
  - **Discovery triggers (#95):** successful explicit UI **Start sign-in**/account switch forces one bounded discovery after immediate or polled completion. Opening Models separately calls non-forcing `ensureModels()` once for missing/idle/stale/error/loading signed-in metadata; error re-entry retries only after shared cooldown with no same-mount loop; loading joins the existing Host flight to observe completion without extra network. Fresh ready cache needs no request, and true unavailable/empty models do not auto-retry. Status/details remain network-free, not the entire opening flow. Background credential/reset events clear Client state and read status, not force discovery on every token event; next open/use ensures metadata.
78
105
  - **Freshness and authority (#95):** `github-copilot` settings default to `accountModelTtlMs: 86400000` (24h maximum reuse) and `accountModelFailureCooldownMs: 300000` (5min failure cooldown). One shared Host flight serves callers; no periodic metadata polling timer (the timestamp's display-only timer is separate). Last same-account metadata may display during TTL refresh/loading/error but never authorize requests. Credential/account/permission invalidation or proof expiry revokes request evidence immediately; the TTL does not extend tokens. Definitive `UNKNOWN_MODEL` triggers one bounded metadata refresh without message replay/model switching; generic HTTP/network errors are not guessed into that category.
79
106
  - **Last-success display (#97):** `snapshot.discoveredAt` appears beside the model count outside **Manage**, without a duplicate inside. Past times use English relative text; the tooltip and accessible semantic `time` expose the full local date, time and time zone. Missing/invalid timestamps or no account hide it; future times use an absolute label. One mounted 60-second display-only timer updates the relative text without RPC/status/discovery, and is disposed when the timestamp disappears or the view unmounts. Pending/failed refresh keeps the last success time; successful refresh replaces it and sign-out clears it. Cache/discovery and authorization rules are unchanged.
80
- - **Honest integration limit:** the published provider-card slot is additive and cannot replace Core **Edit/Delete**. Normal plugin discovery needs no manual model definitions, but the native editor stays available. Embedding account controls does not merge/remove canonical `github-copilot` and managed `github-copilot-preview`, or automatically copy credentials, rewrite configuration/history or migrate selection. The later explicit native account switch is the only credential-projection exception; see [account ownership](./copilot-accounts.md). Any optional real route removal still requires the [separate reviewed migration](./single-route-migration.md).
107
+ - **Honest integration limit:** the published provider-card slot is additive and cannot replace Core **Edit/Delete**. Normal plugin discovery needs no manual model definitions, but the native editor stays available. Embedding account controls does not merge/remove configured profiles, copy credentials, rewrite configuration/history or migrate selection. Production adds no second model provider; the legacy migration procedure below is superseded and no profile removal is needed. The later explicit native account switch is the only credential-projection exception; see [account ownership](./copilot-accounts.md).
81
108
  - **Acceptance still required:** test missing/idle/stale/error/loading open-time ensure versus fresh-cache no-request, shared Host flight, TTL/cooldown boundaries, display-only stale data, immediate revocation, definitive unknown-model refresh without replay, Manage-only manual refresh and visible Retry. Retain provider/footer/old-Core fallback, overlapping-owner transfer, final-unmount cleanup and once-per-explicit-login tests. Read the implementation PR's actual results before claiming these checks passed; documentation is not runtime or live OAuth evidence.
82
109
  - **Historical browser/media evidence:** `copilot-search-routing.png` showed the now-retired plugin-detail routing card in isolated Edge with synthetic providers. It is not a current UI, live credentials, provider availability, search success or Desktop activation claim. Host TTL/cooldown timing and account-control lifecycle remain unit-test evidence rather than screenshot evidence.
83
110
 
@@ -86,7 +113,7 @@ The provider integration introduced in `0.4.0-alpha.5` replaces the older indepe
86
113
  - **V3 ownership:** one global Host account and shared metadata source supply many models; explicitly selected/history-backed Sessions retain independent model context. Search facts use the captured initiating Session's effective request-header/config or explicit `GenerateOptions`, not another Session or future default C. Plans are cached per owner to prevent A/B different-model reuse/cancellation. No global current-model/search-status card is added.
87
114
  - **Cold entrypoints:** Chat picker and `/model` `listModels()` ensure the shared managed source without visiting Settings first. Actual cold managed search performs a non-forcing shared ensure before deriving facts. The same 24h maximum TTL, 5min cooldown, account generation and capability/probe checks remain.
88
115
  - **Native API limits:** a new Copilot draft warns that saving a native profile adds another real group, not another account. Add cannot be vetoed and Save cannot be disabled through the public additive slot. Public `session.selectModel` also writes the future global default; unselected empty Sessions can inherit it. Do not claim enforced one-route registration or immutable empty Sessions.
89
- - **Delivery boundary:** code does not auto-migrate configuration, credentials, selections or history. After release, the operator must resolve approved Session/default choices separately; the config-only v1 Ops command performs no automated selection writes, then may compare-and-swap only the reviewed user-native profile path after ruling out base/journal conflicts, and read back registration. Any search allowlist change to `github-copilot-preview` is a separate reviewed Ops edit, never silent broadening. See [migration](./single-route-migration.md).
116
+ - **Delivery boundary:** code does not auto-migrate configuration, credentials, selections or history. Existing preview-route selections may need an explicit native model choice but are never rewritten. No config-only provider-removal command or search-allowlist edit is required to stop production from registering the legacy provider; see the [current route behavior](./single-route-migration.md).
90
117
  - **Request-context correction:** `Agent.options` remains Core's activation seed, not selected-model evidence. Real `installModelSelection` overrides request/assembly; the Session records effective `requestHeader().config` before tools. Capture the initiating Session's proven request context or use explicit `GenerateOptions`; otherwise traditional search is unavailable. Pending new selection before its next request must not expose the prior header as current prompt guidance.
91
118
  - **Acceptance/evidence:** use real `installModelSelection` to check concurrent A/B models against unchanged activation/default seed C, reject unproven or stale-header prompt guidance after a pending selection, cold Chat and `/model` discovery, cold search/probe, owner invalidation, missing initiator, Add warning with Save retained, and CAS-conflict refusal/readback. README screenshots do not prove these behaviors or a completed migration; consult the implementation and operations evidence separately.
92
119
 
@@ -95,7 +122,7 @@ The provider integration introduced in `0.4.0-alpha.5` replaces the older indepe
95
122
  - **Entry point:** no-argument `githubCopilot.migrationStatus()` reads public live leaves synchronously. Generic `session/list` may be stale and inventory lacks loaded-version evidence. The new result carries loaded build `plugin.name`/`plugin.version`, protocol 1, observation time, five structural capability flags and `complete.sessions/defaultSelection/routes`; unknown/incomplete required selection or route evidence must fail the maintenance gate, not be treated as absence. Idle Agents normally have `activeRequestSelection: null`.
96
123
  - **Session scope:** pending model projection → recorded request-header config → current default only for genuinely empty live Sessions with known projection state. Each row has selection provenance; a running Agent's separate `activeRequestSelection` is its latest recorded header, not proof of an in-flight LLM call. `routes.nativeConfigured`, `nativeRegistered` and `managedRegistered` distinguish effective config from registry state.
97
124
  - **Read-only boundary:** no authorization status/discovery, credential access, network, settings/Session mutations, normal UI or global model/search card. Seven ordinary authorization Remotes retain their existing codec; the eighth Remote uses its own strict `GitHubCopilotMigrationStatus` codec. Source ownership is `src/migration-status.ts` plus the controller/Remote bridge; focused evidence is `tests/migration-status.spec.ts`.
98
- - **Limits and Ops handoff:** `historyScope: live-agents-only` excludes cold history. Require operator acknowledgement that older conversations may need explicit selection on resume. Version/capability self-reports are not full Desktop/Core byte attestation or an atomic cross-namespace guarantee; recheck just before CAS. The separate planned Ops `tools/migrate-copilot-managed-route.ps1` in `cloga/dsh-windows-ops` is config-only v1, with no automatic Session/default writes, plugin install, restart or full Desktop-baseline acceptance. This document does not establish its publication, installation or a completed live migration.
125
+ - **Historical Ops handoff, superseded:** `historyScope: live-agents-only` excluded cold history in the earlier migration plan. The planned `tools/migrate-copilot-managed-route.ps1` is not required for current production behavior; this document does not establish that it was published or run.
99
126
  - **Acceptance:** verify loaded identity, missing/malformed seams and incomplete evidence, fresh live-Agent enumeration, pending-versus-recorded selections, truly empty defaults, running-header caveats, effective-config/registry distinction, bounded strict codec and zero side effects. Read actual test/Ops results rather than treating this checklist as a passing report.
100
127
 
101
128
  ## Core alpha2 compatibility follow-up (#105, planned alpha.11)
@@ -9,6 +9,11 @@ selection remains separate. This is not a release receipt or a claim of current
9
9
  installation/runtime state; publication, installation and loaded state require
10
10
  separate evidence.
11
11
 
12
+ > Current production does not register the `github-copilot-preview` model
13
+ > provider. Session-specific account and continuation controls described below
14
+ > applied to that retired route, not native requests. Native account switching
15
+ > is profile-wide; stored settings and histories are not migrated.
16
+
12
17
  ## Requirements
13
18
 
14
19
  ### GitHub login environments (#424)
@@ -334,8 +339,10 @@ uncertain commit. A selector/canonical mismatch after upgrade or an external
334
339
  native sign-in is shown explicitly and requires a user-selected recovery; no
335
340
  automatic credential or Settings migration occurs.
336
341
 
337
- The existing `github-copilot-preview` route and Session account overrides are
338
- separate plugin-owned behavior; they are not the mechanism for native account
342
+ The production package no longer registers the `github-copilot-preview` model
343
+ route; references to that route elsewhere in this document describe historical
344
+ behavior and do not authorize a second provider. Session account overrides are
345
+ separate plugin-owned behavior and are not the mechanism for native account
339
346
  switching. Native quota and optional native hosted search continue to use only
340
347
  the canonical credential, which after a confirmed switch contains the selected
341
348
  account's grant. No account identity is inferred for a native
@@ -399,25 +406,14 @@ The separate `githubCopilotAccounts` namespace exposes `get`, `ensureIdentity`,
399
406
  cannot be named `remove`: official rc.2 reserves that inherited service name
400
407
  and rejects the entire Client contribution.
401
408
 
402
- Credits shows the Session's next-turn account and quota under the existing title.
403
- Its **Switch** dropdown marks the current choice, scrolls long lists internally
404
- and offers **Follow global default**. Adding accounts, reauthorization, removal and global
405
- selection remain in Models. Changing
406
- the preference while a turn runs leaves that turn's old account pinned; the
407
- popover identifies it separately. Other Sessions are unchanged. Unknown identity
408
- is unavailable, not a stale username presented as current.
409
-
410
- One Models **Manage** groups account management, the new-Session continuation
411
- default and shared exact-ID model preferences. The existing Session policy is
412
- under the composer Credits/usage popover → **Visible-history continuation** →
413
- **Session policy**; it appears only for an open Session whose effective model
414
- is the managed account-discovered Copilot route. Choose **On** after reviewing
415
- the loss disclosure. This is distinct from the Models new-Session default and
416
- applies to subsequent turns and managed native compaction summaries, including
417
- on the same account. Active turns keep their captured policy; enabling does not
418
- send or retry a message. See the [synthetic composer capture](./images/copilot-session-continuation.png)
419
- and [continuation contract](./session-continuation.md). When off, an account change pauses for explicit
420
- persistent-enable/keep-off/cancel consent. See the [approved experience and mock](./account-management-experience.md).
409
+ The historical Credits Session-account switch and **Visible-history
410
+ continuation** controls applied only to the managed route. They are not
411
+ available for native model calls. Use Models account management for explicit
412
+ profile-wide native switches. The old new-Session continuation default is no
413
+ longer shown in Models; existing Session and default settings are not rewritten.
414
+ The [composer capture](./images/copilot-session-continuation.png) and
415
+ [continuation contract](./session-continuation.md) document the retired route's
416
+ behavior, not native-route parity.
421
417
 
422
418
  Completed native and managed turns have a compact **Account** disclosure
423
419
  alongside native Usage actions through the public assistant-actions slot. This