dsh-github-copilot 0.1.0-alpha.1.dsh.0.2.1.alpha.5
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 +439 -0
- package/CHANGELOG.md +875 -0
- package/CONTRIBUTING.md +55 -0
- package/LICENSE +21 -0
- package/README.md +366 -0
- package/README.zh.md +341 -0
- package/SECURITY.md +29 -0
- package/cordis.patch.yml +16 -0
- package/deployment-baseline.json +1580 -0
- package/docs/account-management-experience.md +143 -0
- package/docs/agent-readiness.md +110 -0
- package/docs/auto-high-cost.md +255 -0
- package/docs/auto-iteration-review.json +22 -0
- package/docs/auto-review-sampling.md +60 -0
- package/docs/auto-task-routing.md +341 -0
- package/docs/automatic-model-routing.md +236 -0
- package/docs/copilot-accounts.md +424 -0
- package/docs/copilot-compaction.md +148 -0
- package/docs/copilot-usage.md +133 -0
- package/docs/dual-model.md +66 -0
- package/docs/evidence-driven-iteration.md +86 -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-current-provenance.json +39 -0
- package/docs/images/copilot-model-preferences.png +0 -0
- package/docs/images/copilot-search-routing.png +0 -0
- package/docs/images/copilot-session-continuation.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 +109 -0
- package/docs/mockups/copilot-account-dropdown.html +71 -0
- package/docs/mockups/copilot-account-management.html +393 -0
- package/docs/model-compatibility-acceptance.md +182 -0
- package/docs/npm-distribution.md +202 -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 +17 -0
- package/docs/official-first-021-alpha4.md +157 -0
- package/docs/official-first-021-alpha5.md +83 -0
- package/docs/plugin-diagnostics.md +605 -0
- package/docs/session-continuation.md +141 -0
- package/docs/session-search-routing.md +133 -0
- package/docs/single-route-migration.md +131 -0
- package/docs/web-lifecycle-rc2.md +55 -0
- package/lib/client.js +13236 -0
- package/lib/client.js.map +1 -0
- package/lib/copilot-identity-DRZY_d2X.js +15 -0
- package/lib/diagnostics-analysis-io.js +78 -0
- package/lib/diagnostics-analysis.js +427 -0
- package/lib/diagnostics-types-CF-qg8Do.js +708 -0
- package/lib/index.js +15661 -0
- package/lib/manual-compaction-recovery.js +485 -0
- package/lib/remote.js +1507 -0
- package/lib/request-budget-DLY_aRq0.js +87 -0
- package/lib/routed-web.js +120 -0
- package/lib/search-routing-CV2hs8as.js +792 -0
- package/lib/types/account-dropdown.d.ts +22 -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-code-clipboard.d.ts +4 -0
- package/lib/types/authorization-controller.d.ts +121 -0
- package/lib/types/auto-allocation-card.d.ts +9 -0
- package/lib/types/auto-allocation-diagnostics.d.ts +126 -0
- package/lib/types/auto-allocation-evidence.d.ts +44 -0
- package/lib/types/auto-allocation.d.ts +47 -0
- package/lib/types/auto-assessment-evidence.d.ts +111 -0
- package/lib/types/auto-model-host.d.ts +30 -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 +64 -0
- package/lib/types/auto-review-sampling.d.ts +6 -0
- package/lib/types/auto-selection-explanation.d.ts +9 -0
- package/lib/types/auto-task-assessment.d.ts +49 -0
- package/lib/types/auto-task-classifier.d.ts +10 -0
- package/lib/types/background-compaction.d.ts +30 -0
- package/lib/types/client.d.ts +129 -0
- package/lib/types/compact-account.d.ts +42 -0
- package/lib/types/compaction-continuation-ui.d.ts +29 -0
- package/lib/types/compaction-continuation.d.ts +48 -0
- package/lib/types/compaction-input-estimate.d.ts +28 -0
- package/lib/types/compaction-pressure.d.ts +23 -0
- package/lib/types/compaction-replay.d.ts +18 -0
- package/lib/types/compatibility.d.ts +17 -0
- package/lib/types/composer-notice-style.d.ts +7 -0
- package/lib/types/config.d.ts +141 -0
- package/lib/types/content-file.d.ts +10 -0
- package/lib/types/context-evidence-ui.d.ts +28 -0
- package/lib/types/context-evidence.d.ts +256 -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 +43 -0
- package/lib/types/copilot-accounts-host.d.ts +93 -0
- package/lib/types/copilot-accounts-remote.d.ts +85 -0
- package/lib/types/copilot-accounts-types.d.ts +43 -0
- package/lib/types/copilot-auth.d.ts +31 -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 +51 -0
- package/lib/types/copilot-usage-host.d.ts +61 -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/diagnostics-analysis-io.d.ts +23 -0
- package/lib/types/diagnostics-analysis.d.ts +298 -0
- package/lib/types/diagnostics-card.d.ts +12 -0
- package/lib/types/diagnostics-client.d.ts +13 -0
- package/lib/types/diagnostics-collector.d.ts +50 -0
- package/lib/types/diagnostics-host.d.ts +183 -0
- package/lib/types/diagnostics-remote.d.ts +113 -0
- package/lib/types/diagnostics-types.d.ts +893 -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 +67 -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/native-settings-style.d.ts +10 -0
- package/lib/types/parent-model-follow-card.d.ts +32 -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 +77 -0
- package/lib/types/preview-route.d.ts +76 -0
- package/lib/types/probe.d.ts +39 -0
- package/lib/types/remote-codec.d.ts +10 -0
- package/lib/types/remote.d.ts +202 -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 +28 -0
- package/lib/types/replay-recovery.d.ts +17 -0
- package/lib/types/request-body-composition.d.ts +17 -0
- package/lib/types/request-body-evidence.d.ts +37 -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-diagnostics.d.ts +278 -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 +31 -0
- package/lib/types/responses-request-compression.d.ts +33 -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/session-accounts-controller.d.ts +20 -0
- package/lib/types/session-accounts-host.d.ts +33 -0
- package/lib/types/session-accounts-remote.d.ts +114 -0
- package/lib/types/session-accounts.d.ts +38 -0
- package/lib/types/session-continuation-host.d.ts +45 -0
- package/lib/types/session-continuation-remote.d.ts +22 -0
- package/lib/types/session-continuation-types.d.ts +62 -0
- package/lib/types/session-continuation-ui.d.ts +49 -0
- package/lib/types/session-continuation.d.ts +14 -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-request-models.d.ts +55 -0
- package/lib/types/turn-selection-card.d.ts +24 -0
- package/lib/types/turn-selection-host.d.ts +35 -0
- package/lib/types/turn-selection-remote.d.ts +17 -0
- package/lib/types/turn-selection.d.ts +186 -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 +261 -0
- package/scripts/analyze-diagnostics.mjs +91 -0
- package/scripts/check-search-composition.mjs +191 -0
- package/scripts/iteration-review.mjs +53 -0
- package/scripts/release-policy.mjs +353 -0
- package/scripts/select-core-release.mjs +11 -0
|
@@ -0,0 +1,141 @@
|
|
|
1
|
+
# Session cross-account continuation
|
|
2
|
+
|
|
3
|
+
Explicit **visible-history continuation** is a plugin-owned, lossy outgoing
|
|
4
|
+
Responses policy. It is not a new memory service or portable encrypted state.
|
|
5
|
+
Native Core and pi-ai already preserve replay signatures and reconstruct history;
|
|
6
|
+
their same-provider/API/model check does not establish Copilot account identity.
|
|
7
|
+
|
|
8
|
+
## Experience
|
|
9
|
+
|
|
10
|
+
The composer **Credits/usage** pill opens a popover containing
|
|
11
|
+
**Visible-history continuation** only for an open Session whose effective
|
|
12
|
+
selection is the managed account-discovered Copilot route. Expand it and set
|
|
13
|
+
**Session policy → On** to explicitly enable an existing Session after
|
|
14
|
+
reviewing the loss disclosure. The canonical/native route does not show this
|
|
15
|
+
control.
|
|
16
|
+
|
|
17
|
+

|
|
18
|
+
|
|
19
|
+
This 0.4.0 release-candidate capture uses synthetic Session state and quota;
|
|
20
|
+
[capture provenance](./images/copilot-current-provenance.json) records the
|
|
21
|
+
source commit, build and image hashes. It is not evidence of live availability.
|
|
22
|
+
|
|
23
|
+
New, unseeded Sessions created after this feature's first successful
|
|
24
|
+
activation default on. Activation persists a bounded creation-time policy
|
|
25
|
+
epoch using Settings CAS; existing Sessions, seeded histories, forks and
|
|
26
|
+
unknown birth evidence remain off. Manage the separate new-Session default in
|
|
27
|
+
**Models → GitHub Copilot → Manage → New Session continuation default**.
|
|
28
|
+
Changing it affects only subsequently created Sessions. Session overrides (on, off or
|
|
29
|
+
creation-time default) persist across account changes and restarts. No failed
|
|
30
|
+
request is required first and no hourly confirmation is needed.
|
|
31
|
+
|
|
32
|
+
The enabled disclosure stays compact. Details contain the disable action.
|
|
33
|
+
Enable/disable changes affect future turns; the active turn retains its captured
|
|
34
|
+
policy and account. The UI distinguishes pending changes from the active policy.
|
|
35
|
+
Disabling does not undo answers; it may expose the original replay rejection on
|
|
36
|
+
later requests. When off, switching to a different account pauses for persistent
|
|
37
|
+
enable, keep off, or cancel. The ordinary UI no longer offers a next-turn-only
|
|
38
|
+
mode. An exact replay rejection offers **Enable visible-history continuation**
|
|
39
|
+
with the loss disclosure and Cancel when off; this saves the same persistent
|
|
40
|
+
Session policy. When already on, show status and diagnostic guidance, not another
|
|
41
|
+
authorization. It never automatically sends or retries; native Retry is separate.
|
|
42
|
+
The failure-evidence lifetime does not limit the persisted policy. Retain old
|
|
43
|
+
one-turn consent and temporary recovery Remote contracts for compatibility only;
|
|
44
|
+
the normal Client does not create these authorizations.
|
|
45
|
+
|
|
46
|
+
See the [approved account-management experience and mock](./account-management-experience.md).
|
|
47
|
+
On the currently pinned Core, direct Models navigation is not a public Client
|
|
48
|
+
service. Chat omits the nonfunctional management entry rather than accessing
|
|
49
|
+
private stores or replacing Settings.
|
|
50
|
+
|
|
51
|
+
## Loss and retained content
|
|
52
|
+
|
|
53
|
+
On each admitted managed Responses turn, the first normalized payload captures
|
|
54
|
+
fingerprints of pre-existing completed encrypted reasoning. Those exact items,
|
|
55
|
+
including summaries embedded inside them, are omitted from outgoing requests
|
|
56
|
+
throughout that turn. Newly generated reasoning remains available to subsequent
|
|
57
|
+
tool steps and native retries. A later turn treats the preceding turn's reasoning
|
|
58
|
+
as historical, even without an account change.
|
|
59
|
+
|
|
60
|
+
Visible user/assistant messages, native tool calls and result pairing, system/tool
|
|
61
|
+
definitions and disk history remain under their existing owners. No encrypted
|
|
62
|
+
content is decoded, copied to settings or converted into invented raw reasoning.
|
|
63
|
+
The policy does not claim which account issued an old item.
|
|
64
|
+
|
|
65
|
+
## Public integration and safety
|
|
66
|
+
|
|
67
|
+
`github-copilot.sessionContinuation` stores strict bounded entries containing
|
|
68
|
+
only Session ID, policy version, explicit enabled state and consent timestamp.
|
|
69
|
+
Legacy entries without enabled retain their prior true meaning.
|
|
70
|
+
`continuationDefaultHistory` stores chronological bounded `{enabled, changedAt}`
|
|
71
|
+
entries, never Session content. Native SettingsForms CAS,
|
|
72
|
+
hidden volatile owned-field projection and readback preserve other settings and
|
|
73
|
+
the active plugin fiber. A separate strict `githubCopilotSessionContinuation`
|
|
74
|
+
Remote uses explicit Agent lookup; temporary recovery descriptors remain intact.
|
|
75
|
+
|
|
76
|
+
Public `agent/request`, `session/event` and `agent/disposed` bind an in-memory
|
|
77
|
+
per-turn baseline to the exact initiating Session and request signal. The
|
|
78
|
+
published adapter/SDK's payload hook filters the normalized payload. Only
|
|
79
|
+
`github-copilot-preview` Responses chat calls participate. Classifier,
|
|
80
|
+
unbound requests and other protocols remain native. Cold mid-turn recovery
|
|
81
|
+
without a first-step boundary fails explicitly.
|
|
82
|
+
|
|
83
|
+
The persistent Session policy also covers native managed Responses compaction.
|
|
84
|
+
An observed native `compaction/start` bracket plus exact public Agent lookup
|
|
85
|
+
binds each summary before dispatch. Active turns retain their captured persistent
|
|
86
|
+
policy; idle manual summaries capture current Session policy. Legacy next-turn-only
|
|
87
|
+
consent does not authorize summaries. Each segment omits all historical encrypted
|
|
88
|
+
reasoning and embedded summaries, while visible intermediate checkpoints remain.
|
|
89
|
+
Stock and separately selected recovery engines keep their existing transactions;
|
|
90
|
+
no additional failure-first attempt, retry loop or engine replacement is added.
|
|
91
|
+
End, cancellation, disposal and model/scope mismatch revoke filtering.
|
|
92
|
+
|
|
93
|
+
An additive composer notice reports actual filtering and native outcome. Success
|
|
94
|
+
requires a checkpoint replacement and an error-free matching native end, not
|
|
95
|
+
summary text alone. Failed/cancelled outcomes stay distinct; missing Host-lifetime
|
|
96
|
+
evidence remains unknown after restart. A public projection folds only native
|
|
97
|
+
bracket IDs/phase to trigger strict status reads; it stores no content or new
|
|
98
|
+
events. Polling occurs only while the viewed native bracket is active and stops
|
|
99
|
+
on settlement/unmount. When off, an exact replay-scope rejection exposes the same
|
|
100
|
+
loss-disclosed persistent enable control; unrelated failures do not.
|
|
101
|
+
|
|
102
|
+
`/copilot-compact visible-history` remains a one-operation alternative when the
|
|
103
|
+
selected engine supports it; its consent is never made persistent by the command.
|
|
104
|
+
See [summary recovery](./manual-compaction-recovery.md#explicit-visible-history-summary-recovery).
|
|
105
|
+
|
|
106
|
+
The filter scans at most 65536 top-level input items and 4096 reasoning items
|
|
107
|
+
(including duplicates). Only encrypted reasoning is hashed, with an aggregate
|
|
108
|
+
64 Mi UTF-16-code-unit processing bound per invocation and 64 Ki-code-unit chunks
|
|
109
|
+
that yield to cancellation and turn revocation. These are plugin work bounds,
|
|
110
|
+
not supplier byte/token limits. Ordinary tool output, images, nested content,
|
|
111
|
+
system and tool definitions are neither traversed nor serialized by this filter;
|
|
112
|
+
there is no whole-request 16 MiB continuation cap. Failed, cancelled, overlapping
|
|
113
|
+
or revoked processing cannot partially initialize the baseline. Unsupported
|
|
114
|
+
reasoning, malformed settings, missing boundaries and exhausted work bounds
|
|
115
|
+
produce named diagnostics, not partial filtering or guessed success.
|
|
116
|
+
Credentials, account entitlement and model capabilities remain independently guarded.
|
|
117
|
+
|
|
118
|
+
Native retry normalization retains raw reference-restoration evidence but records
|
|
119
|
+
the final filtered bytes for exact 408 matching. No new retry loop is introduced.
|
|
120
|
+
Input admission still precedes payload filtering: this is not an oversized-context,
|
|
121
|
+
quota, upload-timeout or native context-meter repair.
|
|
122
|
+
Actual token pressure still uses the initiating Agent's enabled native compaction
|
|
123
|
+
engine and bounded recovery: commit the native summary, rebuild the request, then
|
|
124
|
+
apply continuation. A continuation work-bound error is not relabeled as context
|
|
125
|
+
overflow. Disabled automatic compaction, missing engines, cancellation, failed or
|
|
126
|
+
insufficient summaries remain explicit limitations, not permission to trim history.
|
|
127
|
+
|
|
128
|
+
## Evidence limits
|
|
129
|
+
|
|
130
|
+
Synthetic account transitions, source/Host/UI tests and exact-source native
|
|
131
|
+
gateway/persistence fixtures are distinct from real supplier acceptance.
|
|
132
|
+
The native compaction fixture covers first-step overflow and continuing-step
|
|
133
|
+
prevention with Auto, a durable in-memory replacement, rebuilt visible history
|
|
134
|
+
and synthetic historical reasoning larger than 16 MiB. It uses an external-model
|
|
135
|
+
double; it does not prove real supplier acceptance or recovery of a live Session.
|
|
136
|
+
Publication, installation, loaded runtime and controlled live A-B-B-A success
|
|
137
|
+
must be reported separately. Enabling this product mode is not authorized by
|
|
138
|
+
implementing it; live existing Sessions still require explicit loss consent.
|
|
139
|
+
The default-on creation policy is disclosed in account controls and can be
|
|
140
|
+
disabled globally or overridden per Session. Source tests do not establish live
|
|
141
|
+
default acceptance or real cross-account transport.
|
|
@@ -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 current built Client components in an isolated synthetic browser fixture.
|
|
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,131 @@
|
|
|
1
|
+
# Optional migration to the account-discovered Copilot route
|
|
2
|
+
|
|
3
|
+
[English guide](../README.md) · [中文操作说明](#中文操作说明)
|
|
4
|
+
|
|
5
|
+
## Result and boundaries
|
|
6
|
+
|
|
7
|
+
The selected 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 canonical credential
|
|
19
|
+
record `llm-pi-ai/github-copilot` and any independently authorized saved accounts.
|
|
20
|
+
Do not sign out, delete credentials or remove
|
|
21
|
+
authorization to hide a group. `models: []` can mean the default catalog, not
|
|
22
|
+
disabled models.
|
|
23
|
+
|
|
24
|
+
Plugin code never auto-migrates settings, selections or histories. Installation,
|
|
25
|
+
real requests, Session/default changes, configuration edits and Host interruption
|
|
26
|
+
need their own explicit approvals. Public `session.selectModel` also writes the
|
|
27
|
+
future global default: other selected/history-backed Sessions keep their context,
|
|
28
|
+
but unselected empty Sessions may inherit it.
|
|
29
|
+
|
|
30
|
+
## Read-only readiness and maintenance scope
|
|
31
|
+
|
|
32
|
+
Use no-argument `githubCopilot.migrationStatus()` for fresh live-Agent evidence,
|
|
33
|
+
not stale generic `session/list` or an unversioned inventory. It reports:
|
|
34
|
+
|
|
35
|
+
| Field | Interpretation |
|
|
36
|
+
|---|---|
|
|
37
|
+
| `plugin.name/version`, `protocolVersion: 1`, `observedAt` | Loaded build's structural self-report, not full Desktop/Core byte attestation |
|
|
38
|
+
| `capabilities` | `agentsList`, `sessionProjections`, `settingsCas`, `providerRegistry`, `defaultSelection` |
|
|
39
|
+
| `complete.sessions/defaultSelection/routes` | Observation completeness; missing/false is unknown, not safe absence |
|
|
40
|
+
| `effectiveSelection` / `selectionSource` | Pending projection, then request-header config, then default only for genuinely empty Sessions with known projection state |
|
|
41
|
+
| `activeRequestSelection` | Latest recorded header, not proven in-flight model work; idle usually null |
|
|
42
|
+
| Native effective configuration and native/managed registration | Separate facts, never infer one from the other |
|
|
43
|
+
|
|
44
|
+
This read uses no auth/discovery, credentials or network and writes no settings
|
|
45
|
+
or Sessions. `historyScope: live-agents-only` excludes cold stored conversations.
|
|
46
|
+
Operators must acknowledge that old conversations may need explicit selection
|
|
47
|
+
when resumed. The observation is not an atomic cross-namespace transaction;
|
|
48
|
+
recheck immediately before CAS.
|
|
49
|
+
|
|
50
|
+
The planned `cloga/dsh-windows-ops` command
|
|
51
|
+
`tools/migrate-copilot-managed-route.ps1` is separate **config-only v1**
|
|
52
|
+
maintenance. This guide does not attest its publication or execution. It does
|
|
53
|
+
not select Sessions/defaults, scan cold history, install/restart DSH or certify a
|
|
54
|
+
Desktop baseline. Resolve approved selection blockers separately.
|
|
55
|
+
|
|
56
|
+
## Review before removal
|
|
57
|
+
|
|
58
|
+
1. Verify an absence-preserving published plugin is installed **and loaded**,
|
|
59
|
+
with matching Host/Client. Older code may recreate the profile. A version
|
|
60
|
+
declaration or screenshot is not loaded-runtime evidence.
|
|
61
|
+
2. Ensure discovery and accepted managed models. Use visible Retry or intentional
|
|
62
|
+
Refresh, not repeated sign-in/disabled validation. Metadata is not transport
|
|
63
|
+
proof; a real test request needs separate approval.
|
|
64
|
+
3. Deliberately select only approved Sessions/defaults. Preserve model/effort
|
|
65
|
+
only if actually supported. Review paused histories, presets/task references
|
|
66
|
+
without bulk rewrites. Confirm selections before removing their old route.
|
|
67
|
+
4. Review configuration source, effective base layers, namespace revision and
|
|
68
|
+
ownership journals. Inherited configuration, ambiguity or another writer
|
|
69
|
+
blocks removal. Never delete journals or patch Core to force it.
|
|
70
|
+
|
|
71
|
+
Keep the existing profile if any prerequisite is uncertain.
|
|
72
|
+
|
|
73
|
+
## Apply the reviewed Ops migration after release
|
|
74
|
+
|
|
75
|
+
1. Recheck readiness/capabilities/completeness and approved selections. Obtain the
|
|
76
|
+
cold-history acknowledgement. Any Host interruption needs separate approval.
|
|
77
|
+
2. Take a private settings-only backup outside Git/shared docs. Do not copy or
|
|
78
|
+
disclose OAuth credentials. Check current user-native profile/base/journal.
|
|
79
|
+
3. CAS-remove only the reviewed user-native
|
|
80
|
+
`llm-pi-ai.providers.github-copilot` path against the observed revision.
|
|
81
|
+
Preserve the mount/section, credentials, companion and all other provider
|
|
82
|
+
fields. Conflict/already-absent is not permission for blind retry.
|
|
83
|
+
4. Read persisted/effective settings and actual registry, then composer and
|
|
84
|
+
`/model`. Report one managed group only when canonical registration is truly
|
|
85
|
+
absent and no other layer supplies it. A hidden card/write success is not enough.
|
|
86
|
+
5. Separately review any nonempty search `providers` allowlist. An approved
|
|
87
|
+
replacement of the legacy entry with `github-copilot-preview` preserves other
|
|
88
|
+
entries; never clear/broaden automatically.
|
|
89
|
+
6. Verify credentials, approved selections/default and other histories separately.
|
|
90
|
+
`route: not-configured` is optional canonical absence, not login failure or
|
|
91
|
+
proof of a successful model/search call.
|
|
92
|
+
|
|
93
|
+
A stuck **Deleting…** dialog proves neither removal nor its failure. Do not
|
|
94
|
+
repeat deletion; review persisted state after an authorized stop.
|
|
95
|
+
|
|
96
|
+
## History, search and rollback
|
|
97
|
+
|
|
98
|
+
Managed IDs remain stable. No transparent canonical alias/history conversion is
|
|
99
|
+
created. Resumed canonical conversations need an explicit supported selection,
|
|
100
|
+
or preservation/restoration of their original route. Search keeps its existing
|
|
101
|
+
[initiator, metadata, allowlist and proof boundaries](./session-search-routing.md);
|
|
102
|
+
removing canonical does not turn managed chat into custom inline transport.
|
|
103
|
+
|
|
104
|
+
For rollback, stop the relevant Host with permission and compare fresh settings
|
|
105
|
+
with the private backup. Restore only reviewed canonical fields and approved
|
|
106
|
+
selection changes, never overwrite unrelated later edits. Keep ambiguous
|
|
107
|
+
journals for review. Restart with approval and verify registration, credentials
|
|
108
|
+
and selections separately; this is not model-call proof. Older plugin rollback
|
|
109
|
+
may recreate canonical, not a second account.
|
|
110
|
+
|
|
111
|
+
## 中文操作说明
|
|
112
|
+
|
|
113
|
+
新安装无需原生 provider;升级保留已有 canonical 配置,两组都是真实路由,
|
|
114
|
+
不是两个账号。迁移只在明确批准后移除审核过的
|
|
115
|
+
`llm-pi-ai.providers.github-copilot`;canonical 凭据、独立授权的已保存账号、`llm-pi-ai`、授权服务及其它配置保留。
|
|
116
|
+
不要退出登录、删除凭据或使用 `models: []` 来隐藏分组。
|
|
117
|
+
|
|
118
|
+
先验证发布版本已实际加载,再调用无参数 `githubCopilot.migrationStatus()`。
|
|
119
|
+
版本、能力或完整性未知就停止;它只覆盖 live Agent,不扫描冷历史,也不调用
|
|
120
|
+
凭据/发现/网络。最新 header 不等于正在推理,结构自报不等于完整字节证明。
|
|
121
|
+
拟议 Ops 命令仅做配置维护,本文不证明其已发布、已执行或迁移已完成。
|
|
122
|
+
|
|
123
|
+
单独批准 Session/未来默认值选择、真实测试请求、配置写入与停止/重启。
|
|
124
|
+
`session.selectModel` 同时修改未来默认值,未选择的空 Session 可能继承;
|
|
125
|
+
其它已选/历史 Session 不批量改写。恢复旧 canonical 会话时可能需显式选择支持的
|
|
126
|
+
托管模型,不能承诺透明续接。
|
|
127
|
+
|
|
128
|
+
检查 base 层和 journal,私密备份设置但不复制 OAuth。写入前重新查询,
|
|
129
|
+
按 revision 做窄路径 CAS;冲突不盲重试。回读持久化/有效配置、真实 registry、
|
|
130
|
+
composer 与 `/model`,才能确认单组。搜索 allowlist 修改另行审核,不隐式扩大。
|
|
131
|
+
回退仅恢复获准字段,不用整份备份覆盖后来改动;注册恢复仍不证明模型调用成功。
|
|
@@ -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.
|