dsh-github-copilot 0.4.0-alpha.88 → 0.4.0-alpha.91
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 +2 -0
- package/CHANGELOG.md +6 -0
- package/README.md +109 -408
- package/README.zh.md +109 -419
- package/deployment-baseline.json +5 -1
- package/docs/agent-readiness.md +5 -0
- package/docs/auto-task-routing.md +40 -5
- package/docs/automatic-model-routing.md +168 -379
- package/docs/copilot-compaction.md +8 -0
- package/docs/copilot-usage.md +7 -9
- package/docs/dual-model.md +60 -46
- package/docs/image-input-compatibility.md +50 -79
- package/docs/images/copilot-model-preferences.png +0 -0
- package/docs/images/copilot-search-routing.png +0 -0
- package/docs/model-compatibility-acceptance.md +41 -0
- package/docs/npm-distribution.md +129 -178
- package/docs/official-first-016-alpha2.md +4 -0
- package/docs/official-first-020-rc1.md +4 -0
- package/docs/session-search-routing.md +123 -65
- package/docs/single-route-migration.md +112 -97
- package/lib/index.js +117 -29
- package/lib/types/pre-step-pressure.d.ts +8 -0
- package/package.json +1 -1
package/docs/npm-distribution.md
CHANGED
|
@@ -1,198 +1,149 @@
|
|
|
1
|
-
#
|
|
1
|
+
# Distribution and installation
|
|
2
2
|
|
|
3
|
-
|
|
4
|
-
|
|
5
|
-
|
|
6
|
-
|
|
7
|
-
the public npm registry. The name `dsh-github-copilot` remains provisional until
|
|
8
|
-
an authorized maintainer verifies availability or ownership. Never publish an
|
|
9
|
-
empty placeholder package, reuse historical alpha.17, change immutable assets,
|
|
10
|
-
or describe a local archive as a published package.
|
|
3
|
+
Every new version is distributed through an immutable GitHub Release and public
|
|
4
|
+
npm, using the **same original verified tarball**. Package bootstrap is complete;
|
|
5
|
+
subsequent publication uses the configured OIDC Trusted Publisher. Earlier
|
|
6
|
+
Release-only policy and one-time bootstrap tooling are historical.
|
|
11
7
|
|
|
12
8
|
## Authorization and readiness
|
|
13
9
|
|
|
14
|
-
Use
|
|
10
|
+
Use approved registry access and build environments.
|
|
15
11
|
A blocked corporate registry is not authorization to use a VPN, proxy, mirror,
|
|
16
|
-
personal device or
|
|
17
|
-
|
|
18
|
-
|
|
19
|
-
|
|
20
|
-
|
|
21
|
-
|
|
22
|
-
|
|
23
|
-
|
|
24
|
-
|
|
25
|
-
|
|
26
|
-
|
|
27
|
-
|
|
28
|
-
|
|
29
|
-
|
|
30
|
-
|
|
31
|
-
immutable `v0.4.0-alpha.18` GitHub Release archive. The public registry version,
|
|
32
|
-
SHA-512 SRI, `alpha` tag, tarball size and SHA-256 were independently verified
|
|
33
|
-
against those original Release bytes. The one-time workflow, token-authenticated
|
|
34
|
-
bootstrap script and their focused tests have therefore been removed. No normal
|
|
35
|
-
release workflow references `NPM_TOKEN`; removing any now-unused repository
|
|
36
|
-
secret remains a separate explicit maintainer operation.
|
|
37
|
-
|
|
38
|
-
The successful publish was not immediately visible to a read performed about
|
|
39
|
-
four seconds later, so that workflow run ended as a failure even though the
|
|
40
|
-
package and tag subsequently converged. Treat this as an uncertain write, not
|
|
41
|
-
permission to publish again. npm registry package metadata and dist-tags are
|
|
42
|
-
eventually consistent: after any successful or uncertain publish command, wait
|
|
43
|
-
for the exact version to become observable, verify `dist.integrity` and the
|
|
44
|
-
non-decreasing channel tag, then rerun the normal pipeline to reconcile
|
|
45
|
-
read-only. Never retry a publish merely because immediate readback is stale.
|
|
46
|
-
|
|
47
|
-
**`npm stage publish` cannot bootstrap a nonexistent package.** The
|
|
48
|
-
[official npm stage prerequisites](https://docs.npmjs.com/cli/v11/commands/npm-stage/)
|
|
49
|
-
require the package to already exist. For an existing package, staged publishing
|
|
50
|
-
is an optional separately approved process: a maintainer reviews Staged Packages
|
|
51
|
-
on npmjs.com and approves with 2FA. Staged is **pending approval**, not npm live.
|
|
52
|
-
It reserves the version; a conflicting normal publish must fail, not reject or
|
|
53
|
-
overwrite the stage automatically. Approval can update its immutable chosen
|
|
54
|
-
dist-tag, so review channel ordering again before approval. This repository does
|
|
55
|
-
not add a long-term manual/opt-in step to normal releases.
|
|
56
|
-
|
|
57
|
-
## Trusted publishing for subsequent versions
|
|
58
|
-
|
|
59
|
-
[npm trusted publishing](https://docs.npmjs.com/trusted-publishers/) requires
|
|
60
|
-
npm CLI >=11.5.1 and Node >=22.14.0. The publishing workflow uses Node 24 and
|
|
61
|
-
pins npm 11.5.1; package development retains the pinned pnpm version.
|
|
62
|
-
|
|
63
|
-
In the package settings, an authorized maintainer configures:
|
|
64
|
-
|
|
65
|
-
| Field | Value |
|
|
66
|
-
| --- | --- |
|
|
12
|
+
personal device or CI as a bypass. Local synthetic registry tests do not prove
|
|
13
|
+
connectivity, publication rights or live Desktop compatibility.
|
|
14
|
+
|
|
15
|
+
Versions align package, deployment baseline, both README URLs and annotated tag.
|
|
16
|
+
Channel is `alpha`, `beta`, `rc` or stable `latest`; never silently rename a
|
|
17
|
+
package, move/reuse tags, repack immutable assets or publish placeholders.
|
|
18
|
+
|
|
19
|
+
## Trusted publishing
|
|
20
|
+
|
|
21
|
+
[npm Trusted Publishing](https://docs.npmjs.com/trusted-publishers/) requires npm
|
|
22
|
+
>=11.5.1 and Node >=22.14.0. Publishing uses Node 24 and pinned npm 11.5.1;
|
|
23
|
+
development retains the package's pnpm pin.
|
|
24
|
+
|
|
25
|
+
| Publisher field | Value |
|
|
26
|
+
|---|---|
|
|
67
27
|
| Provider | GitHub Actions, GitHub-hosted runner |
|
|
68
|
-
|
|
|
69
|
-
|
|
|
70
|
-
|
|
|
71
|
-
|
|
|
72
|
-
|
|
73
|
-
|
|
74
|
-
|
|
75
|
-
|
|
76
|
-
|
|
77
|
-
`
|
|
78
|
-
|
|
79
|
-
|
|
80
|
-
Do not change token/2FA policy as part of an automated repair.
|
|
28
|
+
| Owner / repository | `cloga` / `dsh-github-copilot` |
|
|
29
|
+
| Workflow | `ci.yml` caller, not reusable `release.yml` |
|
|
30
|
+
| Environment | Unset |
|
|
31
|
+
| Allowed action | Direct `npm publish` |
|
|
32
|
+
|
|
33
|
+
Caller and reusable workflow grant `id-token: write`. No normal release uses
|
|
34
|
+
`NPM_TOKEN` / `NODE_AUTH_TOKEN` or persistent-token fallback. Direct publication
|
|
35
|
+
permission is explicit, not implied by a stage. Staged publication is separately
|
|
36
|
+
approved, pending npm maintainer review/2FA, not live; it reserves the version.
|
|
37
|
+
[`npm stage publish`](https://docs.npmjs.com/cli/v11/commands/npm-stage/) requires
|
|
38
|
+
an existing package and cannot bootstrap one. Do not change auth/2FA policy to
|
|
39
|
+
repair publication.
|
|
81
40
|
|
|
82
41
|
## Same bytes, recovery and tags
|
|
83
42
|
|
|
84
|
-
The
|
|
85
|
-
|
|
86
|
-
|
|
87
|
-
|
|
88
|
-
|
|
89
|
-
|
|
90
|
-
|
|
91
|
-
|
|
92
|
-
|
|
93
|
-
|
|
94
|
-
|
|
95
|
-
|
|
96
|
-
|
|
97
|
-
|
|
98
|
-
|
|
99
|
-
|
|
100
|
-
|
|
101
|
-
|
|
102
|
-
|
|
103
|
-
|
|
104
|
-
|
|
105
|
-
|
|
106
|
-
A matching version with an older/missing tag requires maintainer review; the
|
|
107
|
-
workflow does not silently repair it with separate dist-tag writes.
|
|
108
|
-
|
|
109
|
-
`alpha`, `beta`, and `rc` versions use those tags, never `latest`. Stable
|
|
110
|
-
versions use `latest`. SemVer comparison (not lexical sorting) prevents tag
|
|
111
|
-
downgrades. Publishing a missing older version when its tag already points to a
|
|
112
|
-
newer version fails before writing; reconciling an already published older
|
|
113
|
-
version does not lower that pointer.
|
|
114
|
-
|
|
115
|
-
Report GitHub URL/tag/commit/asset/SHA-256 and npm version/channel/SRI separately.
|
|
116
|
-
GitHub success followed by npm failure is partial delivery, not success.
|
|
117
|
-
There is no historical bulk backfill and no silent npm opt-out.
|
|
43
|
+
The non-cancelling repository release concurrency group serializes publication.
|
|
44
|
+
External publishers must coordinate; dist-tags are not atomic CAS.
|
|
45
|
+
|
|
46
|
+
After the complete compatibility gate, pack once with
|
|
47
|
+
`pnpm --config.ignore-scripts=true pack --pack-destination artifacts`.
|
|
48
|
+
Verification already built/prepacked. Recovery downloads the original uploaded
|
|
49
|
+
archive, verifies tag/source, size/digests, SHA-256/SHA-512 and build equality,
|
|
50
|
+
and never repacks/overwrites immutable bytes. Release assets include
|
|
51
|
+
`SHA256SUMS`; npm receives that same archive with lifecycle scripts disabled.
|
|
52
|
+
|
|
53
|
+
Only registry E404 establishes absence. Auth, TLS, malformed metadata and network
|
|
54
|
+
failures stop delivery. Existing exact versions require matching SRI and a
|
|
55
|
+
same-channel tag at that version or newer; conflicting bytes fail closed.
|
|
56
|
+
Visibility can lag a successful write. After successful/uncertain publication,
|
|
57
|
+
wait for visibility and reconcile read-only; **never automatically republish**.
|
|
58
|
+
A missing/older tag needs review, not a hidden dist-tag write.
|
|
59
|
+
|
|
60
|
+
SemVer ordering prevents downgrades. Missing older releases are not published
|
|
61
|
+
when their channel already points newer; reconciling existing older bytes never
|
|
62
|
+
lowers the pointer. Report GitHub tag/commit/assets/SHA-256 and npm version/SRI
|
|
63
|
+
separately. One channel succeeding is partial delivery.
|
|
64
|
+
[Read-only reconciliation](./npm-publication-readback.md).
|
|
118
65
|
|
|
119
66
|
## Installation preflight still applies
|
|
120
67
|
|
|
121
|
-
Desktop
|
|
122
|
-
|
|
123
|
-
|
|
124
|
-
|
|
125
|
-
|
|
126
|
-
|
|
127
|
-
|
|
128
|
-
|
|
129
|
-
|
|
130
|
-
|
|
131
|
-
|
|
132
|
-
|
|
133
|
-
|
|
134
|
-
|
|
135
|
-
|
|
136
|
-
|
|
68
|
+
Desktop's native package manager accepts an exact verified npm spec, not a URL
|
|
69
|
+
or local archive. Generic/global CLI entry points must not be assumed to manage the reserved
|
|
70
|
+
`desktop` profile. Qualify Desktop's dedicated entry below.
|
|
71
|
+
|
|
72
|
+
Neither entry replaces the checksum-verified package's
|
|
73
|
+
`scripts/check-search-composition.mjs` preflight. Official `composeProfile()`
|
|
74
|
+
writes the empty `cordis.yml` root during normal launch, including resolved
|
|
75
|
+
Desktop profiles. `NONEMPTY_DISPOSABLE_PROFILE_ROOT` must therefore stop
|
|
76
|
+
installation/startup until its contents are preserved and reviewed.
|
|
77
|
+
|
|
78
|
+
A nonempty root may be reconstructible from existing bundles and persistent
|
|
79
|
+
patches, but must never be assumed disposable. Establish complete equality
|
|
80
|
+
through public composition and recheck source hashes before any separately
|
|
81
|
+
approved normalization. Installation approval is not blanket configuration
|
|
82
|
+
deletion approval. Check actual shared-peer resolution for stale profile-local
|
|
83
|
+
shadows; do not patch/copy peers as a plugin compatibility workaround.
|
|
84
|
+
|
|
85
|
+
### Desktop-bundled CLI on official rc.2
|
|
86
|
+
|
|
87
|
+
Read-only inspection of official `@deepseek-ai/dsh-desktop-host@0.2.0-rc.2`
|
|
88
|
+
`lib/cli.js` confirms `runDesktopCli` calls public `runCli` with
|
|
89
|
+
`manageDesktopProfile: true` and bundled pnpm through Electron Node mode.
|
|
90
|
+
This capability is specific to the qualified entry, not a global shim or an
|
|
91
|
+
unverified future release.
|
|
92
|
+
|
|
93
|
+
Resolve the intended installation's `resources\runtime\cli\bin\dsh.cmd`, verify
|
|
94
|
+
its owning version/public entry and exact profile/home/anchor; do not rely on
|
|
95
|
+
PATH. With explicit installation approval, verified bytes and `supported: true`:
|
|
96
|
+
|
|
97
|
+
```powershell
|
|
98
|
+
& '<verified Desktop installation>\resources\runtime\cli\bin\dsh.cmd' plugin --profile desktop add '<absolute path to verified release.tgz>'
|
|
99
|
+
```
|
|
100
|
+
|
|
101
|
+
This example grants no action permission or universal offline guarantee.
|
|
102
|
+
Dependencies still require an approved registry or complete authorized cache.
|
|
103
|
+
CLI support does **not** override composition safety: when preflight fails,
|
|
104
|
+
no add, root rewrite or
|
|
105
|
+
restart followed merely to get past that diagnostic is authorized.
|
|
106
|
+
Use one writer, a private metadata backup, guarded edits and full package/bundle/
|
|
107
|
+
patch/peer readback. Installed-on-disk and loaded runtime remain distinct.
|
|
108
|
+
Stopping/restarting requires separate restart approval.
|
|
137
109
|
|
|
138
110
|
## Controlled offline CLI maintenance for standalone profiles
|
|
139
111
|
|
|
140
|
-
This
|
|
141
|
-
|
|
142
|
-
|
|
143
|
-
|
|
144
|
-
|
|
145
|
-
|
|
146
|
-
for
|
|
147
|
-
|
|
148
|
-
|
|
149
|
-
|
|
150
|
-
|
|
151
|
-
|
|
152
|
-
|
|
153
|
-
|
|
154
|
-
|
|
155
|
-
|
|
156
|
-
|
|
157
|
-
|
|
158
|
-
`supported: true`; unknown, conflicting or unsupported composition is a stop,
|
|
159
|
-
not permission to remove guards or rewrite the profile.
|
|
160
|
-
4. Keep one writer: do not run concurrent package/profile updates. Take a
|
|
161
|
-
private backup of installation metadata (package.json,
|
|
162
|
-
lockfile, bundle/patch configuration and relevant package-manager settings),
|
|
163
|
-
record the current version, and retain a verified rollback artifact.
|
|
164
|
-
Do not copy credential stores, `.env` files or browser storage. If ensuring
|
|
165
|
-
exclusive maintenance requires stopping the Host, obtain separate approval.
|
|
166
|
-
5. Invoke the supported DSH CLI with an absolute path to the verified archive:
|
|
112
|
+
This installs a prebuilt verified Release using existing authorized caches;
|
|
113
|
+
it is not permission to bypass organizational registry restrictions.
|
|
114
|
+
It does not fix TLS or prove public npm health. **Do not use this path
|
|
115
|
+
unchanged for a Desktop-managed/reserved profile**: qualify Desktop's own entry
|
|
116
|
+
and retain independent preflight/approval checks.
|
|
117
|
+
|
|
118
|
+
1. Obtain explicit installation approval for exact version/profile. Resolve
|
|
119
|
+
standalone CLI, install anchor, home and profile; do not infer ownership from
|
|
120
|
+
PATH or target reserved Desktop with a generic entry.
|
|
121
|
+
2. Verify original Release bytes with an independently trusted SHA-256,
|
|
122
|
+
package name/version and safe archive layout. Extract only that artifact,
|
|
123
|
+
never a substitute local build or repack.
|
|
124
|
+
3. Run `scripts/check-search-composition.mjs` with all startup patches and require
|
|
125
|
+
`supported: true`. Unknown/conflicting composition stops before mutation.
|
|
126
|
+
4. Keep one writer. Take a private backup of package/lock/bundle/patch metadata
|
|
127
|
+
and record rollback bytes. Do not copy credential stores, `.env` or browser
|
|
128
|
+
storage. Host shutdown needs separate permission.
|
|
129
|
+
5. Invoke the qualified CLI:
|
|
167
130
|
|
|
168
131
|
```sh
|
|
169
132
|
dsh plugin --profile web add /absolute/path/to/verified-release.tgz --offline --ignore-scripts
|
|
170
133
|
```
|
|
171
134
|
|
|
172
|
-
|
|
173
|
-
|
|
174
|
-
|
|
175
|
-
|
|
176
|
-
|
|
177
|
-
|
|
178
|
-
|
|
179
|
-
|
|
180
|
-
|
|
181
|
-
|
|
182
|
-
|
|
183
|
-
|
|
184
|
-
|
|
185
|
-
|
|
186
|
-
|
|
187
|
-
Use the package manager, not manual copying into node_modules or Core patches.
|
|
188
|
-
7. Report the installed version, checksum, backup and evidence limits. Obtain
|
|
189
|
-
separate restart approval before interrupting the Host or active Sessions.
|
|
190
|
-
Installed-on-disk and loaded-runtime are separate states: after an approved
|
|
191
|
-
restart, verify the loaded build and the intended behavior independently.
|
|
192
|
-
|
|
193
|
-
If installation fails, inspect the actual installed state before retrying or
|
|
194
|
-
rolling back; a failed command is not proof that nothing changed. A rollback
|
|
195
|
-
also needs reviewed, narrowly scoped metadata/dependency restoration. This
|
|
196
|
-
procedure does not authorize Desktop profile management, rewrite installed or
|
|
197
|
-
published historical docs, change machine-wide registry policy, or grant blanket
|
|
198
|
-
approval for future updates.
|
|
135
|
+
Offline needs existing cache; ignore-scripts excludes uncontrolled lifecycle
|
|
136
|
+
work. If cache is incomplete or a build is required, stop. Do not silently
|
|
137
|
+
remove flags, change registry or acquire blocked dependencies elsewhere.
|
|
138
|
+
Keep TLS verification enabled; platform refusals remain authoritative.
|
|
139
|
+
6. Check exit result, installed version, lock/files and all metadata differences.
|
|
140
|
+
Re-run preflight and import-only smoke without plugin activation. CLI may
|
|
141
|
+
reconcile `dsh.profile.bundles`; preserve unrelated entries and review
|
|
142
|
+
unexpected changes. Use package manager, never manual node_modules copying
|
|
143
|
+
or Core patches. A failed command is not proof nothing changed.
|
|
144
|
+
7. Report version/checksum/backup and evidence limits. Obtain restart approval,
|
|
145
|
+
then separately verify loaded build and intended behavior.
|
|
146
|
+
|
|
147
|
+
Rollback needs fresh-state review and narrow restoration of this operation's
|
|
148
|
+
changes, never a whole backup over later user edits. This procedure grants no
|
|
149
|
+
future-update permission or machine-wide network policy change.
|
|
@@ -1,5 +1,9 @@
|
|
|
1
1
|
# Official-first review: DSH 0.1.6-alpha.2
|
|
2
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
|
+
|
|
3
7
|
## Target and evidence boundary
|
|
4
8
|
|
|
5
9
|
Candidate plugin **`0.4.0-alpha.25`** adds the ninth exact target: official **`dsh-v0.1.6-alpha.2`**, commit **`ddefc45fbc7f8e46dd73185e68295696d1297887`**. All eight earlier pins remain, including the historical controlled Desktop baseline; development dependencies remain exactly `0.1.2-rc.1`. This review inspected the unchanged official source checkout read-only. Every official source link below is pinned to that commit, not a moving branch. The [official release notes](https://github.com/deepseek-ai/deepseek-harness/releases/tag/dsh-v0.1.6-alpha.2) were also reviewed: runtime dependency resolution/unload and multiple coexisting Client Sessions make lifecycle and ownership checks mandatory; native subagent sidebar support is not frozen planner/executor policy parity. Native vision-input and Messages API fixes remain the adapter's responsibility, and the companion must not duplicate or override them. The new Plugin Manager owns persistent installation; this adaptation adds no dynamic-plugin replacement or installer. These notes plus source contracts are not published-artifact or installed-runtime qualification.
|
|
@@ -1,5 +1,9 @@
|
|
|
1
1
|
# Official-first review: DSH 0.2.0-rc.1
|
|
2
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
|
+
|
|
3
7
|
## Target and evidence boundary
|
|
4
8
|
|
|
5
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.
|
|
@@ -1,75 +1,133 @@
|
|
|
1
|
-
# Provider-aware
|
|
1
|
+
# Provider-aware Web search
|
|
2
2
|
|
|
3
|
-
|
|
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.
|
|
4
5
|
|
|
5
|
-
|
|
6
|
+
## Choose who searches
|
|
6
7
|
|
|
7
|
-
|
|
8
|
+
Open **Plugins → dsh-github-copilot → Details → Web search**.
|
|
8
9
|
|
|
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 |
|
|
10
15
|
|
|
11
|
-
|
|
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.
|
|
12
21
|
|
|
13
|
-
|
|
14
|
-
2. The plugin's `web-delegate` entry exposes that same official service through a public, Fiber-owned bridge. It does not read any provider registry internals.
|
|
15
|
-
3. The plugin-owned `routed-web` service occupies the ordinary Host `web` scope. It forwards provider registration and fetch to the original service while retaining Fiber-scoped handles for exact-id search dispatch.
|
|
16
|
-
4. Auto-mode Copilot searches use the captured initiating-session route. Fixed/fallback Copilot searches preserve a nonempty explicit provider-owned `searchModel`, otherwise use bounded automatic selection from current account-owned Responses route facts. Other provider ids dispatch through the mirrored public registration. A separate private official WebRuntime supplies native request validation and source capping on every routed branch.
|
|
17
|
-
5. Native `tool-web` consumers, including those in agent presets, retain their original schemas, configured query/source limits, batching, execution policies, timeout metadata, formatting and presentation.
|
|
22
|
+

|
|
18
23
|
|
|
19
|
-
|
|
24
|
+
The picture uses actual published Client components in an isolated browser.
|
|
25
|
+
It does not demonstrate a live search or loaded Desktop runtime.
|
|
20
26
|
|
|
21
27
|
## Routing and fallback
|
|
22
28
|
|
|
23
|
-
|
|
24
|
-
|
|
25
|
-
|
|
26
|
-
|
|
27
|
-
|
|
28
|
-
|
|
29
|
-
|
|
30
|
-
|
|
31
|
-
|
|
32
|
-
|
|
33
|
-
|
|
34
|
-
|
|
35
|
-
|
|
36
|
-
|
|
37
|
-
|
|
38
|
-
|
|
39
|
-
|
|
40
|
-
|
|
41
|
-
|
|
42
|
-
|
|
43
|
-
|
|
44
|
-
|
|
45
|
-
|
|
46
|
-
|
|
47
|
-
|
|
48
|
-
|
|
49
|
-
|
|
50
|
-
|
|
51
|
-
|
|
52
|
-
|
|
53
|
-
|
|
54
|
-
|
|
55
|
-
|
|
56
|
-
|
|
57
|
-
|
|
58
|
-
|
|
59
|
-
|
|
60
|
-
|
|
61
|
-
|
|
62
|
-
-
|
|
63
|
-
|
|
64
|
-
|
|
65
|
-
|
|
66
|
-
|
|
67
|
-
|
|
68
|
-
|
|
69
|
-
|
|
70
|
-
|
|
71
|
-
|
|
72
|
-
|
|
73
|
-
|
|
74
|
-
|
|
75
|
-
|
|
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).
|