dsh-github-copilot 0.1.0-alpha.17.dsh.0.2.2.rc.3 → 0.1.0-alpha.19.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
@@ -109,9 +109,19 @@ The user-authorized native model sync (#466, #479) is a narrow exception to the
109
109
  no-settings-rewrite rule: after a visible preview and one explicit confirmation, one
110
110
  revision-checked write may replace only
111
111
  `llm-pi-ai.providers.github-copilot.models` in an existing canonical profile.
112
- Prove current canonical-account metadata and the native adapter-owned catalog;
113
- skip unrepresentable or uncertain model capabilities. Disclose additions,
114
- updates, removals, skipped models and configured output request defaults.
112
+ Prove current canonical-account metadata and the native adapter-owned catalog.
113
+ The explicit #508 direction changes this operation to ID-only account model
114
+ submission, not capability qualification: submit all enabled account IDs as
115
+ `{ id }` references without intersecting them with the native catalog. Do not copy,
116
+ correct or certify account capacity, input, image or reasoning facts here.
117
+ Unknown native IDs are advisory only, not skipped; do not invent definitions
118
+ or rewrite route defaults. Native validation may reject the entire update.
119
+ The native adapter owns inherited definitions, validation,
120
+ requests and their limitations. This does not weaken account capability proof
121
+ for search or other plugin-owned request paths. Disclose additions, updates,
122
+ removals and IDs absent from the native catalog, and that replacing customized entries removes their
123
+ per-model overrides and output request defaults. A successful sync is not
124
+ model-call compatibility evidence.
115
125
  Prepare the preview without forced discovery from existing verified evidence.
116
126
  An existing `compat.supportsStrictMode: false` may be preserved only when at
117
127
  least one synced Responses or Completions model supports it; block other unproven
@@ -162,15 +172,15 @@ add model-ID routing rules, patch Core, or claim untested parity.
162
172
  When any later legacy detail in this guide conflicts with this confirmed scope,
163
173
  follow this section and the current acceptance criteria in #455/#456.
164
174
 
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
175
+ The user clarified that the ordinary route is DSH's native
176
+ `github-copilot` provider, with useful plugin enhancements attached only through
177
+ public APIs. The production package registers no `github-copilot-preview`
178
+ provider; do not restore it to preserve old selections or create a history
169
179
  migration. Existing stored conversations, credentials and settings are not
170
- authorized for deletion or rewriting. Explicitly document that old managed
180
+ authorized for deletion or rewriting. Explicitly document that old preview
171
181
  route selections may become unavailable. Native model selection and actual
172
182
  subagent invocation must be verified on `github-copilot`, not inferred from
173
- managed-route tests. Record enhancements that cannot safely attach to native
183
+ legacy-route tests. Record enhancements that cannot safely attach to native
174
184
  APIs rather than patching Core or misrepresenting support.
175
185
 
176
186
  For official DSH `0.2.2-rc.3`, plugin `0.1.0-alpha.14.dsh.0.2.2.rc.3`
@@ -271,13 +281,13 @@ Refresh remains owned by native pi-ai `Models.getAuth()` and DSH
271
281
  If selection and canonical credential diverge after an external native sign-in,
272
282
  show an actionable mismatch and require explicit recovery; never auto-migrate.
273
283
 
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
284
+ Keep the native UI and its canonical quota/search attribution. The
285
+ `github-copilot-preview` adapter remains compatibility code but is not
286
+ registered by the production package entry. Session account overrides are not
287
+ evidence of native-provider behavior or a reason to register a second model
288
+ provider. Disposal removes only plugin registrations. Native model selections
289
+ remain native; explicit `web.searchProvider=github-copilot-hosted` needs a
290
+ user-selected replacement before uninstall. Missing configured Web backends return
281
291
  `WEB_PROVIDER_CONFIGURED_MISSING`, not automatic fallback. Uninstall leaves the
282
292
  last selected grant in the native canonical record. No automatic
283
293
  Settings/history migration or sign-out.
@@ -304,7 +314,7 @@ Additional plugin-owned `github-copilot/account-<opaque-id>` records are written
304
314
 
305
315
  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
316
 
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).
317
+ 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
318
 
309
319
  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
320
 
@@ -438,7 +448,7 @@ to remove the native provider or migrate settings.
438
448
  - 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
449
  - 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
450
  - `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.
451
+ - 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
452
 
443
453
  ## Supported DSH seams
444
454
 
@@ -483,7 +493,7 @@ These pins document compatibility evidence. They do not authorize creating anoth
483
493
  - Authorization service: rc.1 Core provides it; the rc.2 web/headless profiles rely on this package's runtime dependency and conditional bootstrap.
484
494
  - Credentials: use record description/read/modify/delete APIs on the Host. Never read records in the browser.
485
495
  - 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.
496
+ - 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
497
  - 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
498
  - Route activation: the dormant `llm-pi-ai` mount observes the profile and registers the route.
489
499
  - Client activation: package metadata injects DSH remotes and Models UI; `./client` mounts `./remote`.
@@ -516,13 +526,45 @@ For historical alpha.25, source markers, local rc.1-backed focused tests and fif
516
526
 
517
527
  ## Important-update release delivery
518
528
 
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.
529
+ - 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.
530
+ - 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
531
  - 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
532
  - 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
533
  - 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
534
  - 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
535
 
536
+ ### Classify delivery before packaging (#502)
537
+
538
+ Choose the task's consumer impact before editing versions, installation URLs or
539
+ package contents. Record the classification and concrete rationale in the PR's
540
+ `Release delivery` section:
541
+
542
+ | Classification | Completion and artifact boundary |
543
+ | --- | --- |
544
+ | `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. |
545
+ | `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. |
546
+ | `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. |
547
+ | `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. |
548
+
549
+ Never add repository tools, fixtures or guides to `package.json.files`, or bump a
550
+ version, merely to make an engineering task releasable. If an intended change
551
+ touches an already shipped executable or other release-significant file, preserve the existing release-policy gate:
552
+ separate/defer that artifact change or establish its real consumer release scope,
553
+ never relabel it repository-only to bypass the gate. Preserve historical releases,
554
+ tags and package contents; this rule does not authorize unpublishing or repacking.
555
+ Documentation-only source edits, including packaged guides, may wait for the next
556
+ independently justified version without changing any already published bytes.
557
+
558
+ The existing PR `documentation-impact` check also checks this declaration against
559
+ the actual base/head manifests and important-file diff. It rejects repository-only
560
+ package changes and metadata-only manufactured plugin updates, and requires a
561
+ reviewable artifact-specific authorization statement for the explicit exception.
562
+ These are consistency checks, not proof of semantic impact or user consent; an
563
+ agent or human must review the rationale and actual request without adding a new
564
+ human-only approval gate. Report repository delivery, plugin publication,
565
+ installed-on-disk and loaded-runtime status separately. No runtime benefit means
566
+ no recommendation to install or restart merely because a new package exists.
567
+
526
568
  ## Installation-agent PowerShell practice
527
569
 
528
570
  Installation agents using the DSH `pwsh` tool must follow these rules:
package/CHANGELOG.md CHANGED
@@ -5,6 +5,20 @@ 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.19.dsh.0.2.2.rc.3 (prepared)
9
+
10
+ - Submit all enabled account model IDs directly instead of copying account capabilities or filtering against the native catalog (#508).
11
+ - Stop excluding native entries because of narrower input limits, restricted image formats or account reasoning metadata. The native adapter keeps its definitions and request behavior; this is not a compatibility certification.
12
+ - Sync submits only `{ id }` references, replacing existing per-model customizations and output defaults after the visible preview and explicit confirmation. IDs absent from the native catalog are advisory, not skipped; native validation may reject the entire update.
13
+ - Preserve canonical-account verification, existing route settings, Settings CAS/readback, history and model selections. No automatic profile update or installation.
14
+
15
+ ## 0.1.0-alpha.18.dsh.0.2.2.rc.3 (prepared)
16
+
17
+ - Stop registering the separate `github-copilot-preview` model provider while retaining account metadata for explicitly confirmed native model sync (#500).
18
+ - Keep native provider settings, account grants and conversation history unchanged. Existing preview-route selections may require an explicit native model selection.
19
+ - If no native Copilot provider is configured, add one in DSH Models; the plugin does not create its profile.
20
+ - Remove the retired route's new-Session continuation default from Models without rewriting saved settings.
21
+
8
22
  ## 0.1.0-alpha.17.dsh.0.2.2.rc.3 (prepared)
9
23
 
10
24
  - 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,58 +73,64 @@ 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.19.dsh.0.2.2.rc.3/dsh-github-copilot-0.1.0-alpha.19.dsh.0.2.2.rc.3.tgz
77
+ curl -fLO https://github.com/cloga/dsh-github-copilot/releases/download/v0.1.0-alpha.19.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.19.dsh.0.2.2.rc.3/dsh-github-copilot-0.1.0-alpha.19.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
- To copy enabled models from the verified account used by the native provider into an existing
104
+ To select enabled model IDs from the verified account used by the native provider in an existing
103
105
  native provider, open **Manage → Model preferences**, review the displayed
104
- additions, updates, removals, skipped models and per-request output defaults,
106
+ additions, updates, removals and any IDs absent from the native catalog,
105
107
  then choose **Sync models**. Preparing the display uses the current verified
106
108
  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
- 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.
115
- Models with unproven or incompatible native catalog protocols, unknown or
116
- narrower server input caps, unknown context or vision support, or unknown or
117
- unsupported reasoning controls are skipped rather than guessed.
118
- New Completions and Anthropic models without a native catalog compatibility
119
- baseline are also skipped; catalog-backed models retain native compatibility.
120
- Image models are included only when the account explicitly supports all four
121
- native request formats: PNG, JPEG, WebP, and GIF. Custom native authentication,
111
+ The submitted list contains all enabled account model IDs as `{ id }` references;
112
+ it is not intersected with the installed native catalog. A successfully saved
113
+ list remains after the plugin is unloaded or uninstalled. Capacities, protocols,
114
+ image support and reasoning controls are resolved by the native adapter,
115
+ not copied or certified from account metadata. Differences
116
+ in account input limits, image formats or reasoning metadata no longer exclude
117
+ a model from this submission. IDs absent from the native catalog are advisory,
118
+ not skipped. The native settings validator may reject the entire update when
119
+ it cannot resolve a model's protocol; the plugin does not guess a protocol or
120
+ change the route API to force it through. A rejected write is not reported as
121
+ successful; check the saved settings before trying again.
122
+ **Sync replaces existing per-model customizations, including configured output
123
+ request defaults, with native definitions.** Review updated and removed entries
124
+ before confirming. Route-wide settings remain unchanged. This selects a model
125
+ list; it does not prove supplier compatibility or enforce account-specific
126
+ limits. Native requests retain DSH's transport, validation and error behavior.
127
+ Custom native authentication,
122
128
  endpoints, headers, nonempty model overrides, or unproven route compatibility
123
129
  overrides block sync rather than changing those settings. An existing
124
130
  `compat.supportsStrictMode: false` is preserved when at least one synced
125
131
  Responses or Completions model supports that native override. An existing native default
126
- reasoning effort must also be supported by each synced model. Core uses each
127
- configured `maxTokens` as that model's per-request output default. The sync does
132
+ reasoning effort is preserved for native resolution. ID-only entries do not add
133
+ per-model `maxTokens` request defaults. The sync does
128
134
  not change credentials, select a model, alter history, or automatically follow
129
135
  later account changes.
130
136
 
@@ -136,8 +142,12 @@ OAuth grant as a saved account. In-progress requests are not redirected, and
136
142
  the operation does not change model selections, provider settings or history.
137
143
  Account switching does not change the native provider's bundled/configured
138
144
  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.
145
+ The plugin does not add a separate Copilot model route. Existing
146
+ `github-copilot-preview` selections are not migrated and may become unavailable;
147
+ stored settings and conversation history remain unchanged. Legacy
148
+ preview-only Session account overrides and continuation controls do not apply
149
+ to native model calls. The old new-Session continuation default is no longer
150
+ shown; existing settings are preserved.
141
151
  Starting the plugin or completing sign-in does not automatically repair the
142
152
  native provider's settings.
143
153
  The plugin registers optional `github-copilot-hosted` search in DSH's existing
@@ -207,11 +217,11 @@ applied to the canonical credential slot. Removing the plugin is not signing
207
217
  out; explicit sign-out or removal of that authorization is a different action
208
218
  and can affect native login.
209
219
 
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
220
+ Existing `github-copilot-preview` model selections are not migrated and may
221
+ become unavailable; explicitly select a native model where needed. If Web is
222
+ set to `github-copilot-hosted`, select another available backend in native Web
223
+ settings before removing the plugin. Removing the plugin does not rewrite Web
224
+ settings: a retained missing backend produces
215
225
  `WEB_PROVIDER_CONFIGURED_MISSING`, not an automatic fallback. Additional-account
216
226
  management and plugin-specific search require the plugin; the last selected
217
227
  native OAuth grant remains in DSH's canonical credential record.
package/README.zh.md CHANGED
@@ -61,53 +61,61 @@ 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.19.dsh.0.2.2.rc.3/dsh-github-copilot-0.1.0-alpha.19.dsh.0.2.2.rc.3.tgz
65
+ curl -fLO https://github.com/cloga/dsh-github-copilot/releases/download/v0.1.0-alpha.19.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.19.dsh.0.2.2.rc.3/dsh-github-copilot-0.1.0-alpha.19.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
- 如需将原生 provider 所用的已验证账号的启用模型复制到已配置的原生 provider,请打开
87
- **Manage → Model preferences**,查看显示的新增、更新、移除、跳过项和每次请求的输出
88
- 默认值,然后选择 **Sync models**。页面使用当前已验证的账号快照准备这些信息,不强制
89
+ 如需在已配置的原生 provider 中选择当前已验证账号的启用模型 ID,请打开
90
+ **Manage → Model preferences**,查看显示的新增、更新、移除以及原生目录未收录的 ID,
91
+ 然后选择 **Sync models**。页面使用当前已验证的账号快照准备这些信息,不强制
89
92
  重新发现;如果快照不可用,请使用 **Refresh models**。此显式单次快照只通过
90
- Settings CAS 和回读替换 `llm-pi-ai.providers.github-copilot.models`。原生 profile
91
- 中保存的非空列表会替代原生内置目录,卸载或停用插件后仍然保留。复制模型设置不会将
92
- 托管路线的权限参数过滤迁移到原生请求,也不能证明供应商调用成功。两条路线均不会在
93
- 发送前将实际投影的图片 MIME 与账号模型的格式清单进行对照检查。
94
- 托管路线也直接使用原生 Goal 更新 schema,不再改写。
95
- 无法证明或与原生目录不兼容的协议、未知或更窄的服务端输入上限、未知上下文或图像支持,
96
- 以及未知或不支持的推理控制会被跳过,不会猜测。缺少原生目录兼容性基线的新 Completions 和
97
- Anthropic 模型也会被跳过;已有目录模型保留原生兼容性。只有账号明确支持 PNG、JPEG、WebP、GIF 四种原生请求图像格式时,
98
- 才会同步图像模型。原生 provider 存在自定义认证、端点、请求头、非空模型覆盖或无法验证的
93
+ Settings CAS 和回读替换 `llm-pi-ai.providers.github-copilot.models`。
94
+ 提交的列表包含账号中所有启用模型的 `{ id }` 引用,不再与原生内置目录取交集。
95
+ 成功保存的列表在卸载或停用插件后仍然保留。容量、协议、图像能力和推理控制
96
+ 交由原生解析,不再复制或认证账号元数据中的能力。
97
+ 账号输入上限、图像格式或推理元数据的差异不再成为排除模型的条件。
98
+ 原生目录未收录的 ID 只做提示,不会跳过;如果原生无法解析某个模型的协议,
99
+ 原生设置校验可能拒绝整次更新。插件不会猜测协议或自动更改路线 API 来绕过拒绝。
100
+ 失败写入不会显示为成功,请检查已保存设置后再重试。
101
+ **同步会用原生定义替换已有的模型自定义参数,包括单次请求输出默认值。**
102
+ 确认前请检查更新和移除项。路线级设置保持不变。这只是模型列表选择,不代表供应商
103
+ 兼容性已经验证,也不会强制执行账号特有的限制;传输、校验和错误处理仍由原生拥有。
104
+ 原生 provider 存在自定义认证、端点、请求头、非空模型覆盖或无法验证的
99
105
  路线兼容性覆盖时,同步会停止,不会修改这些设置。已有的 `compat.supportsStrictMode: false`
100
106
  会保留,但至少一个同步模型必须使用支持该设置的 Responses 或 Completions 协议。已有的
101
- 原生默认推理级别也必须受模型支持。Core 会将配置的
102
- `maxTokens` 同时作为模型的单次请求输出默认值。同步不修改凭据、选择或历史,也不会自动
107
+ 原生默认推理级别会保留并交由原生解析。仅含 ID 的条目不添加模型级 `maxTokens`
108
+ 请求默认值。同步不修改凭据、选择或历史,也不会自动
103
109
  跟随后续账号变化。
104
110
 
105
111
  在原生 GitHub Copilot 账号面板的 **Manage → 账号管理 → 切换** 中选择账号,
106
112
  会将该账号应用到 DSH canonical 凭据槽 `llm-pi-ai/github-copilot`,供此 profile
107
113
  后续的原生请求使用。首次切换会将原有原生 OAuth 授权保留为已保存账号。
108
114
  切换不会重定向正在进行的请求,也不会更改模型选择、provider 设置或历史。
109
- 原生 provider 的内置/配置模型目录不会因此按账号权限过滤。现有
110
- `github-copilot-preview` 仍是独立的插件模型路线,但原生账号切换不依赖它。
115
+ 原生 provider 的内置/配置模型目录不会因此按账号权限过滤。插件不再添加单独的 Copilot
116
+ 模型路线。已有的 `github-copilot-preview` 选择不会自动迁移,可能变为不可用;已保存的设置和
117
+ 对话历史保持不变。旧 preview 路线专用的 Session 账号覆盖和续接控件不适用于原生模型请求;
118
+ 旧的“新 Session 续接默认项”不再显示,已有设置会保留。
111
119
  启动插件或完成登录时,不会自动修复原生 provider 设置。
112
120
  插件在 DSH 现有 Web 服务中注册可选的 `github-copilot-hosted` 搜索后端。
113
121
  请在原生 Web 设置中明确选择,并按需启用原生搜索工具;安装不会改变默认后端。
@@ -160,9 +168,9 @@ Local diagnostics 已移除;现有诊断数据和设置均不改动。若旧
160
168
  原生 **GitHub Copilot** 继续使用最近一次明确应用到 canonical 凭据槽的账号。卸载不是退出登录;
161
169
  显式退出或移除原始授权是另一项操作,会影响原生登录。
162
170
 
163
- 依赖插件的选择不会自动变成原生选择。卸载前,请明确将使用 `github-copilot-preview`
164
- 的 Session/默认模型切回原生模型。如果 Web 选中了 `github-copilot-hosted`,
165
- 请先在原生 Web 设置中选择其他可用后端。卸载不会改写 Web 设置;
171
+ 已有的 `github-copilot-preview` 模型选择不会自动迁移,可能变为不可用;需要时请显式选择原生模型。
172
+ 如果 Web 选中了 `github-copilot-hosted`,请先在原生 Web 设置中选择其他可用后端。
173
+ 卸载不会改写 Web 设置;
166
174
  保留已缺失的后端会返回 `WEB_PROVIDER_CONFIGURED_MISSING`,不会自动回退。
167
175
  附加账号管理和插件专属搜索仍然依赖插件;最近选中的原生 OAuth 授权会保留在 DSH canonical 凭据记录中。
168
176
 
@@ -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.19.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.19.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
  ]
@@ -741,7 +742,7 @@
741
742
  "activation": "visible-nonforcing-preview-and-one-shot-confirmation",
742
743
  "evidenceScope": "tagged-native-settings-and-resolution-with-synthetic-catalog-proof-plus-separate-adapter-ownership-tests-not-live-provider",
743
744
  "sourceMarkers": [
744
- {"file": "src/native-model-sync.ts", "marker": "NATIVE_INHERITED_API_MISMATCH"},
745
+ {"file": "src/native-model-sync.ts", "marker": "nativeCatalogMissingIds"},
745
746
  {"file": "src/native-copilot-access.ts", "marker": "captureNativeCopilotCatalog"},
746
747
  {"file": "src/authorization-controller.ts", "marker": "path: ['providers', GITHUB_COPILOT_PROVIDER_ID, 'models']"},
747
748
  {"file": "src/model-preferences-card.ts", "marker": "Sync models"},
@@ -749,14 +750,12 @@
749
750
  {"file": "src/remote.ts", "marker": "GitHubCopilotNativeModelSyncPreviewSchema"}
750
751
  ],
751
752
  "tests": [
752
- {"file": "tests/native-model-sync.spec.ts", "name": "copies only enabled account models and reports additions, removals, and changed model definitions"},
753
- {"file": "tests/native-model-sync.spec.ts", "name": "does not repoint a known native model when its inherited catalog protocol differs"},
754
- {"file": "tests/native-model-sync.spec.ts", "name": "skips new non-Responses models without a native compatibility baseline"},
755
- {"file": "tests/native-model-sync.spec.ts", "name": "skips narrower or unknown server input caps that cannot be represented natively"},
756
- {"file": "tests/native-model-sync.spec.ts", "name": "skips missing vision or reasoning evidence rather than treating it as disabled"},
757
- {"file": "tests/native-model-sync.spec.ts", "name": "does not expose an off control that the managed account model does not expose"},
753
+ {"file": "tests/native-model-sync.spec.ts", "name": "submits all enabled account IDs without copying or qualifying capabilities"},
754
+ {"file": "tests/native-model-sync.spec.ts", "name": "does not reject native entries for narrower input, image formats or unavailable account reasoning controls"},
755
+ {"file": "tests/native-model-sync.spec.ts", "name": "leaves mixed-protocol model definitions with the native catalog instead of rewriting them"},
756
+ {"file": "tests/native-model-sync.spec.ts", "name": "includes unknown native IDs with an advisory instead of filtering them or inventing defaults"},
757
+ {"file": "tests/native-model-sync.spec.ts", "name": "treats native schema-injected empty fields as unchanged but discloses removal of custom definitions"},
758
758
  {"file": "tests/preview-route.spec.ts", "name": "binds native sync discovery and proof to the global account, not the initiating Session"},
759
- {"file": "tests/native-model-sync.spec.ts", "name": "syncs vision only when account metadata covers every native request image format"},
760
759
  {"file": "tests/account-model-catalog.spec.ts", "name": "distinguishes absent vision and reasoning metadata from explicitly declared empty support"},
761
760
  {"file": "tests/native-copilot-access.spec.ts", "name": "exposes the proven unfiltered adapter catalog independently of the configured model list"},
762
761
  {"file": "tests/native-copilot-access.spec.ts", "name": "revokes a catalog snapshot when its native Loader entry is removed"},
@@ -1449,17 +1448,19 @@
1449
1448
  ]
1450
1449
  },
1451
1450
  {
1452
- "id": "single-managed-route-native-oauth",
1451
+ "id": "native-route-account-metadata",
1453
1452
  "required": true,
1454
1453
  "sourceMarkers": [
1455
1454
  {"file": "src/authorization-controller.ts", "marker": "current !== undefined && providerSupportsStrictMode(current) !== false"},
1456
- {"file": "src/preview-route.ts", "marker": "displayName: 'GitHub Copilot (multi-account)'"},
1455
+ {"file": "src/index.ts", "marker": "registerLegacyProvider: false"},
1456
+ {"file": "src/preview-route.ts", "marker": "registerLegacyProvider = false"},
1457
1457
  {"file": "src/client.ts", "marker": "GitHubCopilotAccountSurface"}
1458
1458
  ],
1459
1459
  "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"},
1460
+ {"file": "tests/single-route.spec.ts", "name": "keeps the native login flow without registering a second model provider"},
1461
+ {"file": "tests/single-route.spec.ts", "name": "discovers account model metadata without registering a model provider"},
1462
+ {"file": "tests/single-route.spec.ts", "name": "handles model preference updates without registering a legacy provider"},
1463
+ {"file": "tests/single-route.spec.ts", "name": "does not replace a removed native profile with the retired provider"},
1463
1464
  {"file": "tests/authorization-controller.spec.ts", "name": "does not recreate an absent canonical profile during status or explicit reconciliation"},
1464
1465
  {"file": "tests/authorization-controller.spec.ts", "name": "keeps absent-profile legacy journal conflicts visible instead of bypassing ownership review"}
1465
1466
  ]
@@ -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