dsh-github-copilot 0.4.0-alpha.100
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 +312 -0
- package/CHANGELOG.md +479 -0
- package/CONTRIBUTING.md +46 -0
- package/LICENSE +21 -0
- package/README.md +203 -0
- package/README.zh.md +202 -0
- package/SECURITY.md +29 -0
- package/cordis.patch.yml +16 -0
- package/deployment-baseline.json +1299 -0
- package/docs/agent-readiness.md +110 -0
- package/docs/auto-task-routing.md +234 -0
- package/docs/automatic-model-routing.md +205 -0
- package/docs/copilot-accounts.md +236 -0
- package/docs/copilot-compaction.md +120 -0
- package/docs/copilot-usage.md +125 -0
- package/docs/dual-model.md +66 -0
- package/docs/image-input-compatibility.md +64 -0
- package/docs/images/copilot-accounts-credits.png +0 -0
- package/docs/images/copilot-accounts.png +0 -0
- package/docs/images/copilot-model-preferences.png +0 -0
- package/docs/images/copilot-search-routing.png +0 -0
- package/docs/images/dual-model-desktop.png +0 -0
- package/docs/images/dual-model-mobile.png +0 -0
- package/docs/images/dual-model-provenance.json +35 -0
- package/docs/images/parent-model-follow.png +0 -0
- package/docs/manual-compaction-recovery.md +64 -0
- package/docs/model-compatibility-acceptance.md +164 -0
- package/docs/npm-distribution.md +149 -0
- package/docs/official-first-016-alpha2.md +66 -0
- package/docs/official-first-020-rc1.md +32 -0
- package/docs/official-first-020-rc2.md +16 -0
- package/docs/session-search-routing.md +133 -0
- package/docs/single-route-migration.md +130 -0
- package/docs/web-lifecycle-rc2.md +55 -0
- package/lib/client.js +10822 -0
- package/lib/client.js.map +1 -0
- package/lib/copilot-identity-DRZY_d2X.js +15 -0
- package/lib/index.js +11689 -0
- package/lib/manual-compaction-recovery.js +315 -0
- package/lib/remote.js +734 -0
- package/lib/request-budget-DLY_aRq0.js +87 -0
- package/lib/routed-web.js +120 -0
- package/lib/search-routing-CqysPLve.js +792 -0
- package/lib/types/account-model-auth.d.ts +15 -0
- package/lib/types/account-model-catalog.d.ts +70 -0
- package/lib/types/account-model-source.d.ts +85 -0
- package/lib/types/agent-compaction.d.ts +4 -0
- package/lib/types/authorization-controller.d.ts +119 -0
- package/lib/types/auto-assessment-evidence.d.ts +46 -0
- package/lib/types/auto-model-host.d.ts +27 -0
- package/lib/types/auto-model-intent.d.ts +36 -0
- package/lib/types/auto-model-presentation.d.ts +57 -0
- package/lib/types/auto-model-routing.d.ts +59 -0
- package/lib/types/auto-selection-explanation.d.ts +9 -0
- package/lib/types/auto-task-assessment.d.ts +47 -0
- package/lib/types/auto-task-classifier.d.ts +9 -0
- package/lib/types/background-compaction.d.ts +30 -0
- package/lib/types/client.d.ts +115 -0
- package/lib/types/compact-account.d.ts +42 -0
- package/lib/types/compaction-pressure.d.ts +23 -0
- package/lib/types/compatibility.d.ts +17 -0
- package/lib/types/config.d.ts +89 -0
- package/lib/types/content-file.d.ts +10 -0
- package/lib/types/context-evidence-ui.d.ts +11 -0
- package/lib/types/context-evidence.d.ts +108 -0
- package/lib/types/context-usage.d.ts +4 -0
- package/lib/types/copilot-account-presentation.d.ts +7 -0
- package/lib/types/copilot-accounts-card.d.ts +30 -0
- package/lib/types/copilot-accounts-host.d.ts +75 -0
- package/lib/types/copilot-accounts-remote.d.ts +77 -0
- package/lib/types/copilot-accounts-types.d.ts +42 -0
- package/lib/types/copilot-auth.d.ts +25 -0
- package/lib/types/copilot-grant.d.ts +11 -0
- package/lib/types/copilot-identity.d.ts +11 -0
- package/lib/types/copilot-request.d.ts +11 -0
- package/lib/types/copilot-stream-liveness.d.ts +23 -0
- package/lib/types/copilot-usage-card.d.ts +30 -0
- package/lib/types/copilot-usage-host.d.ts +58 -0
- package/lib/types/copilot-usage-normalize.d.ts +9 -0
- package/lib/types/copilot-usage-remote.d.ts +63 -0
- package/lib/types/copilot-usage-types.d.ts +20 -0
- package/lib/types/copilot-usage-ui.d.ts +4 -0
- package/lib/types/current-provider.d.ts +59 -0
- package/lib/types/deepseek-search-fallback.d.ts +11 -0
- package/lib/types/dual-model-host.d.ts +119 -0
- package/lib/types/dual-model-remote.d.ts +63 -0
- package/lib/types/dual-model-types.d.ts +34 -0
- package/lib/types/external-link.d.ts +3 -0
- package/lib/types/failure.d.ts +38 -0
- package/lib/types/http.d.ts +48 -0
- package/lib/types/image-input-admission.d.ts +5 -0
- package/lib/types/index.d.ts +39 -0
- package/lib/types/manual-compaction-recovery.d.ts +52 -0
- package/lib/types/migration-status.d.ts +50 -0
- package/lib/types/model-exclusions.d.ts +15 -0
- package/lib/types/model-preferences-card.d.ts +9 -0
- package/lib/types/model-protocol.d.ts +31 -0
- package/lib/types/native-select-style.d.ts +4 -0
- package/lib/types/parent-model-follow-card.d.ts +41 -0
- package/lib/types/parent-model-follow.d.ts +44 -0
- package/lib/types/pi-provider-bridge.d.ts +22 -0
- package/lib/types/plan.d.ts +148 -0
- package/lib/types/pre-step-pressure.d.ts +8 -0
- package/lib/types/preview-provider.d.ts +66 -0
- package/lib/types/preview-route.d.ts +74 -0
- package/lib/types/probe.d.ts +39 -0
- package/lib/types/reasoning-presentation.d.ts +55 -0
- package/lib/types/remote-codec.d.ts +10 -0
- package/lib/types/remote.d.ts +199 -0
- package/lib/types/replay-recovery-host.d.ts +28 -0
- package/lib/types/replay-recovery-remote.d.ts +14 -0
- package/lib/types/replay-recovery-types.d.ts +24 -0
- package/lib/types/replay-recovery-ui.d.ts +26 -0
- package/lib/types/replay-recovery.d.ts +17 -0
- package/lib/types/request-body-evidence.d.ts +34 -0
- package/lib/types/request-body-timeout-marker.d.ts +2 -0
- package/lib/types/request-body-timeout.d.ts +4 -0
- package/lib/types/request-budget.d.ts +58 -0
- package/lib/types/request-upload-evidence.d.ts +23 -0
- package/lib/types/response-error-body.d.ts +3 -0
- package/lib/types/responses-reasoning-text.d.ts +24 -0
- package/lib/types/responses-reasoning.d.ts +7 -0
- package/lib/types/responses-replay-compat.d.ts +30 -0
- package/lib/types/route-ownership.d.ts +70 -0
- package/lib/types/routed-web.d.ts +50 -0
- package/lib/types/search-backend.d.ts +16 -0
- package/lib/types/search-routing-host.d.ts +19 -0
- package/lib/types/search-routing-policy.d.ts +18 -0
- package/lib/types/search-routing-remote.d.ts +20 -0
- package/lib/types/search-routing.d.ts +43 -0
- package/lib/types/search-tool-routing.d.ts +22 -0
- package/lib/types/serialize.d.ts +106 -0
- package/lib/types/settings-reader.d.ts +16 -0
- package/lib/types/sse.d.ts +28 -0
- package/lib/types/temporary-models.d.ts +25 -0
- package/lib/types/tool-schema-compat.d.ts +17 -0
- package/lib/types/traditional-search.d.ts +17 -0
- package/lib/types/turn-model-provenance.d.ts +45 -0
- package/lib/types/turn-selection-card.d.ts +10 -0
- package/lib/types/turn-selection-host.d.ts +11 -0
- package/lib/types/turn-selection-remote.d.ts +13 -0
- package/lib/types/turn-selection.d.ts +119 -0
- package/lib/types/turn-usage-evidence.d.ts +66 -0
- package/lib/types/turn-usage-notice.d.ts +7 -0
- package/lib/types/types.d.ts +69 -0
- package/lib/types/usage.d.ts +26 -0
- package/lib/types/watchdog.d.ts +22 -0
- package/lib/types/web-delegate.d.ts +12 -0
- package/lib/types/web-search-routing-card.d.ts +16 -0
- package/lib/types/web-search-routing-config.d.ts +12 -0
- package/lib/types/wire-anthropic.d.ts +37 -0
- package/lib/types/wire.d.ts +56 -0
- package/lib/web-delegate.js +9 -0
- package/output/auto-model-mockup/index.html +207 -0
- package/package.json +236 -0
- package/scripts/check-search-composition.mjs +191 -0
|
@@ -0,0 +1,32 @@
|
|
|
1
|
+
# Official-first review: DSH 0.2.0-rc.1
|
|
2
|
+
|
|
3
|
+
> **Historical review:** this preserves the earlier evaluation, not current
|
|
4
|
+
> support or delivery readiness. Use the [rc.2 review](./official-first-020-rc2.md)
|
|
5
|
+
> and current README for the supported host.
|
|
6
|
+
|
|
7
|
+
## Target and evidence boundary
|
|
8
|
+
|
|
9
|
+
Candidate plugin **`0.4.0-alpha.38`** adds official Core **`0.2.0-rc.1`**, tag commit [`4878cdabd87d4041bdaff61d04c966883b9fd07a`](https://github.com/deepseek-ai/deepseek-harness/commit/4878cdabd87d4041bdaff61d04c966883b9fd07a), as the current target while retaining every earlier compatibility pin. The independently observed Windows Desktop feed also identifies `0.2.0-rc.1`; its Desktop package set is not materialized in this checkout. Source/API qualification, npm package fixtures, and Desktop installation/runtime qualification are separate evidence.
|
|
10
|
+
|
|
11
|
+
This review inspected only the exact official tag and unchanged installed package artifacts. **Complete** means the cited public contract supports the named behavior, not that Desktop or a live service was qualified. **Partial** identifies both the official capability and the gap. **Unverified** means parity was not established, not that official support is absent. Decisions are **retain**, **migrate**, or **retire**. A retirement trigger is evidence for a separately reviewed change, never permission for automatic removal on a version bump.
|
|
12
|
+
|
|
13
|
+
## Compatibility decisions
|
|
14
|
+
|
|
15
|
+
| Surface | Exact official contract and support | Decision | Remaining gap / retirement trigger |
|
|
16
|
+
|---|---|---|---|
|
|
17
|
+
| Copilot OAuth, credentials, catalog and ordinary model transport | The unchanged official [`llm-pi-ai` login/auth exports](https://github.com/deepseek-ai/deepseek-harness/tree/4878cdabd87d4041bdaff61d04c966883b9fd07a/packages/llm/llm-pi-ai/src) continue to own provider registration, OAuth grants, refresh and normal transport. | **Retain** the narrow public credential bridge and account-scoped route; do not add a second adapter or catalog. | The official path does not establish the companion's strict grant normalization, conditional authorization bootstrap, or authenticated per-account endpoint/capability metadata. Retire those bridges only after public official behavior and runtime acceptance preserve the same data and safety contracts. |
|
|
18
|
+
| Core settings access and invalidation | [`SettingsForms`](https://github.com/deepseek-ai/deepseek-harness/blob/4878cdabd87d4041bdaff61d04c966883b9fd07a/packages/settings/settings/src/index.ts) and its public [types](https://github.com/deepseek-ai/deepseek-harness/blob/4878cdabd87d4041bdaff61d04c966883b9fd07a/packages/settings/settings/src/types.ts) expose current descriptor/mutation APIs and the `settings/document-updated` event. | **Migrate** readers to the public descriptor path where legacy `get` is absent; **retain** a narrow legacy branch for older supported releases. | Retire the compatibility reader/listener only when the corresponding older Core pins are removed through an explicit support-policy change and the current namespace/redaction guarantees remain intact. |
|
|
19
|
+
| Volatile provider configuration | The public [`PiAiConfig` provider view](https://github.com/deepseek-ai/deepseek-harness/blob/4878cdabd87d4041bdaff61d04c966883b9fd07a/packages/llm/llm-pi-ai/src/config.ts) wraps provider storage; callers materialize it through `.get()` rather than object indexing. | **Migrate** the plugin's route builder to `.get()` and **retain** object support for older native layouts. | Do not infer registration from an empty volatile wrapper. Retire the legacy object branch only with removal of the older baselines and matching fixture evidence. |
|
|
20
|
+
| Tool results and message history | The current [`Message` contract](https://github.com/deepseek-ai/deepseek-harness/blob/4878cdabd87d4041bdaff61d04c966883b9fd07a/packages/llm/llm/src/message.ts) includes first-class `role: 'tool'` messages; older history can still contain nested tool-result blocks. | **Migrate** serialization to recognize both current and retained forms without rewriting source history. | Do not collapse tool messages into assistant text or change replay ownership. Retire legacy handling only after old stored histories are outside the declared support scope. |
|
|
21
|
+
| Agent creation and existing role-history restoration | The public [Agent lifecycle](https://github.com/deepseek-ai/deepseek-harness/blob/4878cdabd87d4041bdaff61d04c966883b9fd07a/packages/core/agent/src/index.ts) serializes and awaits `agent/created`; the event carries a creation source. | **Retain** compatibility-only projection restoration and test it through the awaited public lifecycle. | Retired role UI/settings/new-root behavior stays retired. Runtime policy enforcement and old-history recovery remain plugin-owned; never infer permission from a missing or malformed descriptor. |
|
|
22
|
+
| Remote and Client Gateway validation | Current [Typert codecs](https://github.com/deepseek-ai/deepseek-harness/blob/4878cdabd87d4041bdaff61d04c966883b9fd07a/packages/typert/protocol/src/types.ts) expose `create()` factories. The [Client Gateway](https://github.com/deepseek-ai/deepseek-harness/blob/4878cdabd87d4041bdaff61d04c966883b9fd07a/packages/api/gateway/src/client/index.ts) forwards parameter payloads without local parsing; strict input validation belongs at the registered Host boundary. Strict result codecs decode only when the descriptor publishes a decoder. | **Migrate** descriptor tests to current `create()` factories; **retain** the same strict Host codecs and legacy `.schema` helper bridge. | Client-side tests must not claim pre-transport input filtering or result validation the current Gateway does not promise. The exact-source Host fixture must continue to prove strict registered-boundary parsing. Retire the legacy bridge only after old Core consumers leave support. |
|
|
23
|
+
| Models UI and additive contribution | The official [Models Client](https://github.com/deepseek-ai/deepseek-harness/blob/4878cdabd87d4041bdaff61d04c966883b9fd07a/packages/client/ui-settings-models/src/client/index.ts) declares keyed `settings.models.provider-card` and list `settings.models.footer` slots. | **Retain** additive account/search controls and native model editing. | Slot existence is not account-management or search-policy parity. Retire a control only after equivalent official workflow, accessibility, ownership and lifecycle behavior pass Client/Desktop acceptance. |
|
|
24
|
+
| Web routing and search | Official Web exposes registered provider dispatch; the plugin's public facade captures an exact registered provider before routed search. | **Retain** fail-closed captured-registration dispatch and the explicit missing-seam diagnostic. | Never replace captured identity with an ID-only lookup, global model default or another Session's selection. Desktop/runtime and live provider behavior remain unverified. |
|
|
25
|
+
| Plugin installation and Desktop injection | The official Windows Desktop feed identifies release `0.2.0-rc.1`, but no installed Desktop package set or loaded runtime is present here. | **Retain** package entry-point/peer checks and document the independent Desktop boundary. | Do not claim successful injection, install, activation, authentication, model calls or UI behavior from Core source or npm package tests alone. |
|
|
26
|
+
|
|
27
|
+
## Qualification ledger
|
|
28
|
+
|
|
29
|
+
- The release/tag and public source contracts above are pinned; the Core tree and installed dependencies were not modified.
|
|
30
|
+
- Local source build, focused tests, repository verifiers, exact-tag runtime fixtures and the complete gate must be reported separately after execution. Package-version metadata is not semantic or runtime proof.
|
|
31
|
+
- No real Copilot OAuth, model, search, live-profile change, Desktop install/restart, publication, push or pull request is part of this adaptation.
|
|
32
|
+
- Desktop package hashes/contents, packaged Electron activation, and loaded-version equivalence are **not verified** in this checkout. The observed feed release is not a materialized Desktop artifact.
|
|
@@ -0,0 +1,16 @@
|
|
|
1
|
+
# Official-first review: DSH 0.2.0-rc.2
|
|
2
|
+
|
|
3
|
+
## Target and evidence
|
|
4
|
+
|
|
5
|
+
The sole admitted target is official [`dsh-v0.2.0-rc.2`](https://github.com/deepseek-ai/deepseek-harness/tree/639ed015397290b3745d163aafe02ffee4aa3f84), commit `639ed015397290b3745d163aafe02ffee4aa3f84`. Compare it with the retained [rc.1 baseline](./official-first-020-rc1.md) using the [official source comparison](https://github.com/deepseek-ai/deepseek-harness/compare/dsh-v0.2.0-rc.1...dsh-v0.2.0-rc.2). The signed installed Windows Desktop `dsh/desktop-runtime.json` is 2,817,387 bytes, SHA-256 `29561160fb7825c3968708f5700564f4381a976985fc270ee5dcc42e5a0a3a54`, and lists 287 shared packages. Desktop, Core and Desktop Host report rc.2; the 16 declared DSH peers resolve rc.2, Cordis 4.0.4 and schemastery 3.18.4. The descriptor establishes peer ownership, not plugin activation, Electron integration or live provider calls.
|
|
6
|
+
|
|
7
|
+
## Public contracts and decisions
|
|
8
|
+
|
|
9
|
+
| Surface | Official support / remaining gap | Decision and retirement trigger |
|
|
10
|
+
|---|---|---|
|
|
11
|
+
| Native model adapter and SDK | Published [`@deepseek-ai/dsh-llm-pi-ai@0.2.0-rc.2`](https://registry.npmjs.org/@deepseek-ai/dsh-llm-pi-ai/-/dsh-llm-pi-ai-0.2.0-rc.2.tgz) depends on pi-ai `^0.87.1`. The native SDK now passes branded `TranscriptContext` to providers, with prompt and tools folded into system messages. | **Migrate** the plugin-owned provider bridge and estimated admission to exact pi-ai `0.87.1`; count each normalized message as a lower bound even when earlier usage anchors omit changed prefixes. Retain native transport and the same stream object. Retire this bridge only when official account-scoped metadata and admission preserve these contracts. |
|
|
12
|
+
| Profile bundle patches | Public `bundlePatchPaths` accepts a bundle's string or ordered array of patches. Signed rc.2 `dsh-web-app` lists five patches, whereas the old plugin preflight accepted only one string. | **Migrate** read-only preflight to the published resolver and compose every patch in order, rejecting malformed manifests and unsupported routing. Retire only after an official installer provides equivalent fail-closed structural admission. |
|
|
13
|
+
| Models UI, authorization, Remote, Session and search | Published rc.2 package entrypoints and inspected public seams retain the rc.1 forms. The official rc.2 UI-agent-preset removes its `developerTools` injection, which this plugin does not use. | **Retain** the public Host/Client/Remote integrations and their guarded ownership. Retirement requires verified official equivalent behavior plus migration and runtime acceptance; lack of a new public seam is not evidence of complete parity. |
|
|
14
|
+
| Desktop package graph | Signed descriptor has the current shared peers; pi-ai and Zod are not shared Host packages. The bundled adapter resolves pi-ai 0.87.1 and Zod separately. | **Retain** required Host peers and Client external React; do not copy bundled dependencies or patch Core. Recheck effective profile resolution before Desktop installation because a stale profile-local Host peer may shadow the bundle. |
|
|
15
|
+
|
|
16
|
+
The unchanged-tagged-source and exact published-artifact fixtures must pass on Windows and Linux before publication. Local synthetic HTTP, source markers, package imports and signed peer metadata do not prove account entitlement, Copilot model calls, loaded Desktop plugin state or profile installation. The Desktop owner performs installation separately after verified publication and preflight; no credentials, model settings or Session histories are migrated by this change.
|
|
@@ -0,0 +1,133 @@
|
|
|
1
|
+
# Provider-aware Web search
|
|
2
|
+
|
|
3
|
+
Target: official DSH / Windows Desktop `0.2.0-rc.2`. The routed facade and
|
|
4
|
+
configuration page are shipped plugin functionality, not a pending proposal.
|
|
5
|
+
|
|
6
|
+
## Choose who searches
|
|
7
|
+
|
|
8
|
+
Open **Plugins → dsh-github-copilot → Details → Web search**.
|
|
9
|
+
|
|
10
|
+
| Control | Behavior |
|
|
11
|
+
|---|---|
|
|
12
|
+
| Search provider: Auto | Follow the initiating Chat provider when its exact supported search registration exists |
|
|
13
|
+
| Search provider: an ID | Always use that registered provider, independent of later Chat model changes |
|
|
14
|
+
| Fallback provider | At most one different final provider after an eligible failure; None disables it |
|
|
15
|
+
|
|
16
|
+
Saving both routing leaves uses one native settings CAS, with no Copilot
|
|
17
|
+
credential, model discovery or capability-probe prerequisite. Saving does not
|
|
18
|
+
prove a provider is available. The directory lists fresh public registrations,
|
|
19
|
+
not static examples; unavailable stored IDs stay visible and fail explicitly.
|
|
20
|
+
Reload sees newly registered IDs.
|
|
21
|
+
|
|
22
|
+

|
|
23
|
+
|
|
24
|
+
The picture uses actual published Client components in an isolated browser.
|
|
25
|
+
It does not demonstrate a live search or loaded Desktop runtime.
|
|
26
|
+
|
|
27
|
+
## Routing and fallback
|
|
28
|
+
|
|
29
|
+
Auto uses the captured initiating Session/request route, never the global Chat
|
|
30
|
+
default or another Session. Copilot aliases keep their account/model checks;
|
|
31
|
+
other IDs match an observed search registration exactly. Model names/families
|
|
32
|
+
do not become search providers. This provider-level convention does not promise
|
|
33
|
+
the same account or execution model across independent registries.
|
|
34
|
+
|
|
35
|
+
A successful primary result, including zero sources, ends routing. Failure may
|
|
36
|
+
try one distinct final fallback, never the same backend twice, a hidden third
|
|
37
|
+
tier or recursive routing. Cancellation, disposal, registration replacement
|
|
38
|
+
and account-proof invalidation terminate the operation. Captured implementations,
|
|
39
|
+
not only replaceable IDs, remain bound to the request.
|
|
40
|
+
|
|
41
|
+
Fallback notices survive native result projection in `WebSearchResult.content`,
|
|
42
|
+
identify the backend and possible charges, and expose no raw exception.
|
|
43
|
+
Generic providers own their authentication and cancellation; their endpoint/model
|
|
44
|
+
provenance is not guessed from Chat. The stronger Copilot/legacy pre-dispatch
|
|
45
|
+
proof guard is not claimed for every third-party implementation.
|
|
46
|
+
|
|
47
|
+
## Copilot model selection and proof
|
|
48
|
+
|
|
49
|
+
Auto-following Copilot search uses the initiating real model. Explicit/fallback
|
|
50
|
+
Copilot search instead preserves a nonempty `github-copilot.searchModel`
|
|
51
|
+
override; otherwise it non-forcing ensures current account metadata and
|
|
52
|
+
considers at most three eligible Responses models in deterministic ID order.
|
|
53
|
+
No model-name table, Session borrowing or global default supplies candidates.
|
|
54
|
+
|
|
55
|
+
Metadata establishes eligibility, not search capability. Default `probe: true`
|
|
56
|
+
requires bounded successful proof before **one final user-query request**.
|
|
57
|
+
Candidate proof is not query replay; a final failure never tries the query on
|
|
58
|
+
another model. `probe: false` is an explicit trust override, not a recommended
|
|
59
|
+
repair. Cancellation or captured credential/account-proof changes fail closed.
|
|
60
|
+
Successful reusable proofs retain account/owner lifetime, not the creating
|
|
61
|
+
request's signal/deadline. Concurrent callers own their unfinished probes.
|
|
62
|
+
|
|
63
|
+
## Settings and legacy compatibility
|
|
64
|
+
|
|
65
|
+
Routing lives in `github-copilot.searchRouting`. One CAS writes nested paths
|
|
66
|
+
`['searchRouting', 'searchProvider']` and
|
|
67
|
+
`['searchRouting', 'defaultSearchProvider']`. Legacy separate namespaces are
|
|
68
|
+
read-only fallback sources. Old fixed/none spending restrictions are preserved
|
|
69
|
+
until an explicit save adopts new policy; unknown IDs never silently normalize
|
|
70
|
+
to an available provider.
|
|
71
|
+
|
|
72
|
+
A nonempty legacy `searchModel` is displayed read-only and remains authoritative.
|
|
73
|
+
Only its separate reset writes `searchModel: ''`. Both actions coordinate the
|
|
74
|
+
shared namespace revision without discarding unsaved drafts. A failed reset
|
|
75
|
+
does not block an unrelated routing save.
|
|
76
|
+
|
|
77
|
+
Official SettingsForms projects volatile Config leaves; the plugin uses native
|
|
78
|
+
live fields and narrow writes, not a manually invented namespace registration.
|
|
79
|
+
Traced Settings/routing Remote faces are captured once at UI registration so
|
|
80
|
+
parent renders retain drafts and pending saves. `routeWebSearch`, enable,
|
|
81
|
+
allowlists and capability proof keep independent responsibilities. Safety and
|
|
82
|
+
transport settings are not routine fields on this card.
|
|
83
|
+
|
|
84
|
+
## Composition and installation safety
|
|
85
|
+
|
|
86
|
+
The plugin moves the original enabled top-level official Web service into
|
|
87
|
+
`github-copilot-original-web`, exposes it through a public Fiber-owned delegate,
|
|
88
|
+
and mounts its routed facade in ordinary Host Web scope. Original configuration,
|
|
89
|
+
fetch and native tool consumers remain under their owners. A separate private
|
|
90
|
+
official WebRuntime retains request validation/source capping for routed search.
|
|
91
|
+
No preset edits, private registry access or Core prototype replacement occurs.
|
|
92
|
+
|
|
93
|
+
Before install/update, run the verified package's read-only
|
|
94
|
+
`scripts/check-search-composition.mjs` with profile, home, install anchor and
|
|
95
|
+
all launcher patches. Require `supported: true`. It parses public composition
|
|
96
|
+
without booting plugins, credentials, network or settings writes and compares
|
|
97
|
+
the baseline with the actual candidate bundle position.
|
|
98
|
+
|
|
99
|
+
Custom/dynamic/nested/disabled/already-isolated layouts, collisions and a nonempty
|
|
100
|
+
disposable `cordis.yml` root are refused. Normal `composeProfile()` rewrites that
|
|
101
|
+
root to `[]`, so preserve it and review complete reconstructibility before any
|
|
102
|
+
separately approved normalization. `dsh plugin add` does not enforce preflight.
|
|
103
|
+
Do not describe unsupported composition as a safe no-op.
|
|
104
|
+
|
|
105
|
+
Desktop supports its qualified bundled CLI, not any generic shim.
|
|
106
|
+
[Installation guidance](./npm-distribution.md#desktop-bundled-cli-on-official-rc2).
|
|
107
|
+
Web service disable/remove/upgrade may require a cold restart; do not use
|
|
108
|
+
remove/re-add as a hot-upgrade workaround.
|
|
109
|
+
[Lifecycle characterization](./web-lifecycle-rc2.md).
|
|
110
|
+
|
|
111
|
+
## Verification and limits
|
|
112
|
+
|
|
113
|
+
Real Loader/ConfigEditor/SettingsForms fixtures cover volatile discovery,
|
|
114
|
+
two-leaf CAS, same Fiber, stale conflicts, hidden legacy reset and restart
|
|
115
|
+
persistence. Client gateway/actual registration tests cover traced identities,
|
|
116
|
+
draft continuity and catalog reads; a settings-map mock alone cannot establish
|
|
117
|
+
native reachability. Native WebRuntime/Agent/tool fixtures cover validation,
|
|
118
|
+
registration disposal, result notices and original fetch ownership.
|
|
119
|
+
|
|
120
|
+
Policy and transport tests cover bounded candidates, lazy account discovery,
|
|
121
|
+
proof expiry, fallback auth, credential discontinuity, cancellation and
|
|
122
|
+
independent requests. Published Client desktop/narrow captures use synthetic
|
|
123
|
+
services. Required exact rc.2 Windows/Linux CI remains the release gate; counts
|
|
124
|
+
and old local registry failures belong in the relevant PR evidence, not permanent
|
|
125
|
+
setup instructions.
|
|
126
|
+
|
|
127
|
+
Live hosted-search capability, paid fallback behavior and Desktop activation
|
|
128
|
+
require separate authorized acceptance. Ordinary Chat success, saved routing,
|
|
129
|
+
synthetic tests or a source marker prove none of those layers.
|
|
130
|
+
Design history: [#135](https://github.com/cloga/dsh-github-copilot/issues/135),
|
|
131
|
+
[#148](https://github.com/cloga/dsh-github-copilot/issues/148),
|
|
132
|
+
[#195](https://github.com/cloga/dsh-github-copilot/issues/195) and
|
|
133
|
+
[#216](https://github.com/cloga/dsh-github-copilot/issues/216).
|
|
@@ -0,0 +1,130 @@
|
|
|
1
|
+
# Optional migration to the account-discovered Copilot route
|
|
2
|
+
|
|
3
|
+
[English guide](../README.md) · [中文操作说明](#中文操作说明)
|
|
4
|
+
|
|
5
|
+
## Result and boundaries
|
|
6
|
+
|
|
7
|
+
One Host-owned OAuth account supplies many account models. The stable managed
|
|
8
|
+
route ID is `github-copilot-preview`, displayed as **GitHub Copilot**.
|
|
9
|
+
Fresh installations need no native provider definition. Upgrades preserve
|
|
10
|
+
existing `llm-pi-ai.providers.github-copilot`; two real groups can remain until
|
|
11
|
+
explicit migration. This is configuration removal, not hiding a card.
|
|
12
|
+
|
|
13
|
+
Native Add/Save can recreate another group. The warning is additive, not
|
|
14
|
+
single-route enforcement; Core Edit/Delete remains. Model discovery/UI lifecycle
|
|
15
|
+
is described in the [current README](../README.md#install-and-sign-in), not a
|
|
16
|
+
prerequisite to removing a route.
|
|
17
|
+
|
|
18
|
+
Keep `llm-pi-ai` and authorization mounted and preserve the sole credential
|
|
19
|
+
record `llm-pi-ai/github-copilot`. Do not sign out, delete credentials or remove
|
|
20
|
+
authorization to hide a group. `models: []` can mean the default catalog, not
|
|
21
|
+
disabled models.
|
|
22
|
+
|
|
23
|
+
Plugin code never auto-migrates settings, selections or histories. Installation,
|
|
24
|
+
real requests, Session/default changes, configuration edits and Host interruption
|
|
25
|
+
need their own explicit approvals. Public `session.selectModel` also writes the
|
|
26
|
+
future global default: other selected/history-backed Sessions keep their context,
|
|
27
|
+
but unselected empty Sessions may inherit it.
|
|
28
|
+
|
|
29
|
+
## Read-only readiness and maintenance scope
|
|
30
|
+
|
|
31
|
+
Use no-argument `githubCopilot.migrationStatus()` for fresh live-Agent evidence,
|
|
32
|
+
not stale generic `session/list` or an unversioned inventory. It reports:
|
|
33
|
+
|
|
34
|
+
| Field | Interpretation |
|
|
35
|
+
|---|---|
|
|
36
|
+
| `plugin.name/version`, `protocolVersion: 1`, `observedAt` | Loaded build's structural self-report, not full Desktop/Core byte attestation |
|
|
37
|
+
| `capabilities` | `agentsList`, `sessionProjections`, `settingsCas`, `providerRegistry`, `defaultSelection` |
|
|
38
|
+
| `complete.sessions/defaultSelection/routes` | Observation completeness; missing/false is unknown, not safe absence |
|
|
39
|
+
| `effectiveSelection` / `selectionSource` | Pending projection, then request-header config, then default only for genuinely empty Sessions with known projection state |
|
|
40
|
+
| `activeRequestSelection` | Latest recorded header, not proven in-flight model work; idle usually null |
|
|
41
|
+
| Native effective configuration and native/managed registration | Separate facts, never infer one from the other |
|
|
42
|
+
|
|
43
|
+
This read uses no auth/discovery, credentials or network and writes no settings
|
|
44
|
+
or Sessions. `historyScope: live-agents-only` excludes cold stored conversations.
|
|
45
|
+
Operators must acknowledge that old conversations may need explicit selection
|
|
46
|
+
when resumed. The observation is not an atomic cross-namespace transaction;
|
|
47
|
+
recheck immediately before CAS.
|
|
48
|
+
|
|
49
|
+
The planned `cloga/dsh-windows-ops` command
|
|
50
|
+
`tools/migrate-copilot-managed-route.ps1` is separate **config-only v1**
|
|
51
|
+
maintenance. This guide does not attest its publication or execution. It does
|
|
52
|
+
not select Sessions/defaults, scan cold history, install/restart DSH or certify a
|
|
53
|
+
Desktop baseline. Resolve approved selection blockers separately.
|
|
54
|
+
|
|
55
|
+
## Review before removal
|
|
56
|
+
|
|
57
|
+
1. Verify an absence-preserving published plugin is installed **and loaded**,
|
|
58
|
+
with matching Host/Client. Older code may recreate the profile. A version
|
|
59
|
+
declaration or screenshot is not loaded-runtime evidence.
|
|
60
|
+
2. Ensure discovery and accepted managed models. Use visible Retry or intentional
|
|
61
|
+
Refresh, not repeated sign-in/disabled validation. Metadata is not transport
|
|
62
|
+
proof; a real test request needs separate approval.
|
|
63
|
+
3. Deliberately select only approved Sessions/defaults. Preserve model/effort
|
|
64
|
+
only if actually supported. Review paused histories, presets/task references
|
|
65
|
+
without bulk rewrites. Confirm selections before removing their old route.
|
|
66
|
+
4. Review configuration source, effective base layers, namespace revision and
|
|
67
|
+
ownership journals. Inherited configuration, ambiguity or another writer
|
|
68
|
+
blocks removal. Never delete journals or patch Core to force it.
|
|
69
|
+
|
|
70
|
+
Keep the existing profile if any prerequisite is uncertain.
|
|
71
|
+
|
|
72
|
+
## Apply the reviewed Ops migration after release
|
|
73
|
+
|
|
74
|
+
1. Recheck readiness/capabilities/completeness and approved selections. Obtain the
|
|
75
|
+
cold-history acknowledgement. Any Host interruption needs separate approval.
|
|
76
|
+
2. Take a private settings-only backup outside Git/shared docs. Do not copy or
|
|
77
|
+
disclose OAuth credentials. Check current user-native profile/base/journal.
|
|
78
|
+
3. CAS-remove only the reviewed user-native
|
|
79
|
+
`llm-pi-ai.providers.github-copilot` path against the observed revision.
|
|
80
|
+
Preserve the mount/section, credentials, companion and all other provider
|
|
81
|
+
fields. Conflict/already-absent is not permission for blind retry.
|
|
82
|
+
4. Read persisted/effective settings and actual registry, then composer and
|
|
83
|
+
`/model`. Report one managed group only when canonical registration is truly
|
|
84
|
+
absent and no other layer supplies it. A hidden card/write success is not enough.
|
|
85
|
+
5. Separately review any nonempty search `providers` allowlist. An approved
|
|
86
|
+
replacement of the legacy entry with `github-copilot-preview` preserves other
|
|
87
|
+
entries; never clear/broaden automatically.
|
|
88
|
+
6. Verify credentials, approved selections/default and other histories separately.
|
|
89
|
+
`route: not-configured` is optional canonical absence, not login failure or
|
|
90
|
+
proof of a successful model/search call.
|
|
91
|
+
|
|
92
|
+
A stuck **Deleting…** dialog proves neither removal nor its failure. Do not
|
|
93
|
+
repeat deletion; review persisted state after an authorized stop.
|
|
94
|
+
|
|
95
|
+
## History, search and rollback
|
|
96
|
+
|
|
97
|
+
Managed IDs remain stable. No transparent canonical alias/history conversion is
|
|
98
|
+
created. Resumed canonical conversations need an explicit supported selection,
|
|
99
|
+
or preservation/restoration of their original route. Search keeps its existing
|
|
100
|
+
[initiator, metadata, allowlist and proof boundaries](./session-search-routing.md);
|
|
101
|
+
removing canonical does not turn managed chat into custom inline transport.
|
|
102
|
+
|
|
103
|
+
For rollback, stop the relevant Host with permission and compare fresh settings
|
|
104
|
+
with the private backup. Restore only reviewed canonical fields and approved
|
|
105
|
+
selection changes, never overwrite unrelated later edits. Keep ambiguous
|
|
106
|
+
journals for review. Restart with approval and verify registration, credentials
|
|
107
|
+
and selections separately; this is not model-call proof. Older plugin rollback
|
|
108
|
+
may recreate canonical, not a second account.
|
|
109
|
+
|
|
110
|
+
## 中文操作说明
|
|
111
|
+
|
|
112
|
+
新安装无需原生 provider;升级保留已有 canonical 配置,两组都是真实路由,
|
|
113
|
+
不是两个账号。迁移只在明确批准后移除审核过的
|
|
114
|
+
`llm-pi-ai.providers.github-copilot`;唯一凭据、`llm-pi-ai`、授权服务及其它配置保留。
|
|
115
|
+
不要退出登录、删除凭据或使用 `models: []` 来隐藏分组。
|
|
116
|
+
|
|
117
|
+
先验证发布版本已实际加载,再调用无参数 `githubCopilot.migrationStatus()`。
|
|
118
|
+
版本、能力或完整性未知就停止;它只覆盖 live Agent,不扫描冷历史,也不调用
|
|
119
|
+
凭据/发现/网络。最新 header 不等于正在推理,结构自报不等于完整字节证明。
|
|
120
|
+
拟议 Ops 命令仅做配置维护,本文不证明其已发布、已执行或迁移已完成。
|
|
121
|
+
|
|
122
|
+
单独批准 Session/未来默认值选择、真实测试请求、配置写入与停止/重启。
|
|
123
|
+
`session.selectModel` 同时修改未来默认值,未选择的空 Session 可能继承;
|
|
124
|
+
其它已选/历史 Session 不批量改写。恢复旧 canonical 会话时可能需显式选择支持的
|
|
125
|
+
托管模型,不能承诺透明续接。
|
|
126
|
+
|
|
127
|
+
检查 base 层和 journal,私密备份设置但不复制 OAuth。写入前重新查询,
|
|
128
|
+
按 revision 做窄路径 CAS;冲突不盲重试。回读持久化/有效配置、真实 registry、
|
|
129
|
+
composer 与 `/model`,才能确认单组。搜索 allowlist 修改另行审核,不隐式扩大。
|
|
130
|
+
回退仅恢复获准字段,不用整份备份覆盖后来改动;注册恢复仍不证明模型调用成功。
|
|
@@ -0,0 +1,55 @@
|
|
|
1
|
+
# DSH 0.2.0-rc.2 Web lifecycle characterization
|
|
2
|
+
|
|
3
|
+
This is a bounded characterization of the public Loader and Web APIs in the pinned DSH 0.2.0-rc.2 packages. It records a known limitation; it is not a passing acceptance test for desired add/remove/re-add behavior and does not exercise the native Desktop package manager.
|
|
4
|
+
|
|
5
|
+
## Reproduce
|
|
6
|
+
|
|
7
|
+
From the repository root, after the normal build:
|
|
8
|
+
|
|
9
|
+
```powershell
|
|
10
|
+
pnpm build
|
|
11
|
+
node --test tests/scripts/web-lifecycle-characterization.test.mjs
|
|
12
|
+
```
|
|
13
|
+
|
|
14
|
+
The test uses the installed `@deepseek-ai/dsh-app-boot` and `@deepseek-ai/dsh-web` packages, loads the built plugin-owned delegate and router through the public Loader, and creates temporary synthetic provider/consumer modules. It makes no network calls and removes its temporary directory and Loader fibers in `finally`.
|
|
15
|
+
|
|
16
|
+
## Observed transitions
|
|
17
|
+
|
|
18
|
+
The test first checks an unaffected no-overlay control: the stock global `ctx.web`, a registered synthetic search provider, and an independent global consumer are active, and a search returns the provider's marker result.
|
|
19
|
+
|
|
20
|
+
For the exact-bundle first-add sequence, it records the activation ordering explicitly. Immediately before the bundle is applied, global `ctx.web`, provider search, and the independent consumer are all active. During staged Loader reconciliation using the bundle's real Web/delegate/router IDs, global `ctx.web` becomes unavailable and the consumer becomes pending. The registered provider remains callable through the captured official WebRuntime, but adding the delegate and routed rows does not restore global `ctx.web` or the consumer in this fixture. This is not evidence that all cold starts fail: the separate cold-load fixture below succeeds.
|
|
21
|
+
|
|
22
|
+
For the separate remove/re-add sequence, the complete Web-routing rows are loaded at boot, then global `ctx.web`, provider search, and the consumer are verified usable before removal. Removal leaves global `ctx.web` unavailable and the consumer pending, while the captured official WebRuntime still answers through the registered synthetic provider. Before re-add, the test asserts and reports this stranded state rather than claiming an active-consumer precondition: removal has already invalidated it. Re-adding the exact candidate rows and retrying reconciliation do not restore global `ctx.web` or consumer activation in this fixture.
|
|
23
|
+
|
|
24
|
+
These are isolated public Loader observations using synthetic plugins. The older untracked reproduction used temporary IDs `delegate` and `routed` and no active provider; it reported that the staged route became usable after the final reconcile. The tracked fixture now uses the exact IDs from `cordis.patch.yml`, tests an active provider for the add/remove scenarios, and separates staged hot-add from a complete cold-loaded route. This accounts for the differing observations; the older alias-ID result is not evidence that the exact bundle hot-add succeeds.
|
|
25
|
+
|
|
26
|
+
The fixture does not exercise the native Desktop package manager, installation behavior, recovery after process restart, or every profile composition. The native manager's `restart-required` result for upgrading an installed package in place is a separate package-update boundary and is not evidence that the hot route lifecycle is repaired.
|
|
27
|
+
|
|
28
|
+
## Native disable warning guidance
|
|
29
|
+
|
|
30
|
+
An observed native Desktop disable completed with the plugin shown as **Off**, then reported only:
|
|
31
|
+
|
|
32
|
+
```text
|
|
33
|
+
web-search-deepseek: pending (waiting for service: web)
|
|
34
|
+
web-fetch-http: pending (waiting for service: web)
|
|
35
|
+
```
|
|
36
|
+
|
|
37
|
+
The plugin cannot change or reclassify that native result after disable because its Client contribution has already been unloaded. While enabled, the plugin details card therefore warns that disable, removal, and upgrade operations affecting this Web composition require a full Desktop exit and cold restart. When the plugin is already **Off** and the native diagnostic contains only dependent entries pending while waiting for a service, restart Desktop instead of repeatedly toggling or reinstalling the plugin. This guidance does not convert other activation errors, mutation failures, or mixed diagnostics into success.
|
|
38
|
+
|
|
39
|
+
The test names begin `known-bug characterization` intentionally. They pass only when the pinned rc.2 fixtures continue to exhibit the documented states. A desired recovery acceptance test must instead prove that the consumer and provider stay usable through each supported transition, global `ctx.web` remains available, official/delegate/routed paths remain correctly owned, and teardown removes only the registrations owned by their fibers. Do not reinterpret this characterization test as approval of the current behavior.
|
|
40
|
+
|
|
41
|
+
## Bounded public-API finding
|
|
42
|
+
|
|
43
|
+
In the exact published rc.2 `WebRuntime` declarations, public search/fetch APIs are provider registration plus `search()` and `fetch()`. Provider maps and configured provider IDs are private. There is no public middleware/interceptor, selected-provider lookup or dispatch operation, or service replacement/rebinding contract for active consumers.
|
|
44
|
+
|
|
45
|
+
The included public-API test also checks additive registration directly: a configured existing provider continues to win over an added routing provider, while two usable providers without a configured ID produce `WEB_PROVIDER_AMBIGUOUS`. It therefore cannot transparently preserve configured-provider selection and the plugin's exact primary/fallback dispatch. A second global `web` service collides with the existing service name; moving the official service to a child scope is the current composition that exposes the consumer lifecycle problem. Cordis effects own this plugin's own registrations but do not rebind other active fibers when a service's scope changes.
|
|
46
|
+
|
|
47
|
+
The specific extension needed for a feature-equivalent plugin route is a public, disposable search-dispatch middleware on the existing `WebRuntime`, invoked after normal provider selection and receiving `(request, signal, next)` so it can route eligible Copilot calls while delegating all other calls to the already-selected provider. It must preserve cancellation, result caps, configured-provider semantics, registration ownership, and unrelated consumers. A Loader-owned alternative would be an explicit public service-replacement operation that rebinds dependents when service isolation changes. Neither contract is present in the pinned rc.2 API examined here.
|
|
48
|
+
|
|
49
|
+
This finding is limited to those inspected APIs and the requirement to preserve current routing behavior for active global consumers; it is not a claim that all possible future APIs or behavior-changing opt-ins are impossible. An independent plugin-owned Web provider/configuration path would require user configuration and would alter existing selection/fallback behavior, so this task does not present it as a transparent repair.
|
|
50
|
+
|
|
51
|
+
## TLS system trust is a separate, unverified operational option
|
|
52
|
+
|
|
53
|
+
The signed rc.2 Desktop main process starts the Host as a separate Node-mode child and passes inherited environment settings to it. The documented Node option `NODE_USE_SYSTEM_CA=1` keeps certificate validation enabled while adding the operating-system CA store to Node's trust sources. This changes which trusted roots Node accepts; it is not a Desktop setting and does not configure Chromium's separate trust behavior. Earlier no-credential HEAD diagnostics reached an HTTP response with system CA enabled where the signed Node runtime's default trust failed certificate verification. This does not prove the cause of the prior OAuth failure or that authentication will work.
|
|
54
|
+
|
|
55
|
+
If an operator later chooses this diagnostic option, use only a user-owned, reversible launcher that sets the variable for a fresh Desktop launch. First fully quit the existing Desktop so a new invocation cannot be handed off to an already-running single instance; then launch the signed executable as the new main process. Do not set a machine/user-global environment variable, edit the installed shortcut or Desktop profile, bypass TLS checks, or install roots. Keep the launcher process and any redirected standard I/O handles alive for the full Desktop process lifetime; do not pipe them through a short-lived shell, which can close the stream and produce `EPIPE`. Removing the user-owned launcher reverses this opt-in. This is a recommendation only: no launcher was created or run, no live Desktop state was changed, and no sign-in retry was performed.
|