dsh-github-copilot 0.1.0-alpha.1.dsh.0.2.1.alpha.5 → 0.1.0-alpha.1.dsh.0.2.2.rc.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/AGENTS.md +180 -39
- package/CHANGELOG.md +51 -0
- package/CONTRIBUTING.md +18 -0
- package/README.md +92 -344
- package/README.zh.md +59 -305
- package/cordis.patch.yml +0 -13
- package/deployment-baseline.json +147 -262
- package/docs/account-management-experience.md +12 -0
- package/docs/agent-readiness.md +1 -1
- package/docs/auto-high-cost.md +4 -0
- package/docs/auto-review-sampling.md +6 -3
- package/docs/auto-task-routing.md +4 -0
- package/docs/automatic-model-routing.md +15 -6
- package/docs/copilot-accounts.md +56 -1
- package/docs/copilot-compaction.md +12 -1
- package/docs/copilot-usage.md +1 -1
- package/docs/dual-model.md +13 -8
- package/docs/image-input-compatibility.md +49 -2
- package/docs/model-compatibility-acceptance.md +97 -173
- package/docs/npm-distribution.md +11 -0
- package/docs/official-first-021-rc3.md +86 -0
- package/docs/plugin-diagnostics.md +16 -40
- package/docs/web-lifecycle-rc2.md +60 -55
- package/lib/client.js +2807 -1640
- package/lib/client.js.map +1 -1
- package/lib/{copilot-identity-DRZY_d2X.js → copilot-identity-BF8J8-9O.js} +1 -4
- package/lib/diagnostics-analysis.js +1 -1
- package/lib/{diagnostics-types-CF-qg8Do.js → diagnostics-types-eEWwFOFD.js} +2 -42
- package/lib/index.js +987 -4715
- package/lib/manual-compaction-recovery.js +2 -2
- package/lib/remote.js +48 -9
- package/lib/routed-web.js +17 -6
- package/lib/traditional-search-BZpWOTZA.js +80 -0
- package/lib/types/auto-model-presentation.d.ts +4 -0
- package/lib/types/client.d.ts +1 -3
- package/lib/types/compatibility.d.ts +5 -5
- package/lib/types/composer-notice-style.d.ts +2 -0
- package/lib/types/context-evidence.d.ts +7 -7
- package/lib/types/copilot-accounts-card.d.ts +3 -1
- package/lib/types/copilot-accounts-host.d.ts +5 -1
- package/lib/types/copilot-accounts-remote.d.ts +4 -1
- package/lib/types/copilot-accounts-types.d.ts +1 -0
- package/lib/types/copilot-login-environment.d.ts +12 -0
- package/lib/types/image-input-admission.d.ts +16 -1
- package/lib/types/index.d.ts +2 -15
- package/lib/types/model-preferences-card.d.ts +1 -1
- package/lib/types/preview-route.d.ts +2 -1
- package/lib/types/replay-failure-evidence.d.ts +34 -0
- package/lib/types/replay-recovery-types.d.ts +7 -0
- package/lib/types/replay-recovery-ui.d.ts +2 -1
- package/lib/types/request-body-evidence.d.ts +3 -0
- package/lib/types/responses-replay-compat.d.ts +21 -1
- package/lib/types/routed-web.d.ts +1 -1
- package/lib/types/session-accounts-remote.d.ts +3 -1
- package/lib/types/tool-schema-compat.d.ts +4 -14
- package/lib/types/turn-selection-card.d.ts +2 -1
- package/package.json +74 -72
- package/scripts/check-search-composition.mjs +15 -38
- package/lib/search-routing-CV2hs8as.js +0 -792
- package/lib/types/parent-model-follow-card.d.ts +0 -32
- package/output/auto-model-mockup/index.html +0 -207
package/AGENTS.md
CHANGED
|
@@ -22,16 +22,65 @@ This repository follows a **plugin-only** policy: implement fixes in `dsh-github
|
|
|
22
22
|
2. Read this file, then `node scripts/agent.mjs describe --json`. `agent-contract.json` maps each task to its owning files, focused tests, risks and approval boundaries; package scripts and release URLs are derived from current metadata.
|
|
23
23
|
3. Run `node scripts/agent.mjs doctor --json` before install. It is a dependency-free, read-only repository preflight: exit 0 means preflight passed, 1 means prerequisites missing, 2 means invalid arguments/metadata. Build presence is not build freshness, and no live DSH or credential readiness is claimed.
|
|
24
24
|
4. Choose a task with `node scripts/agent.mjs plan models --json` (or authorization/search/client/compatibility/tooling/release). Output is an unexecuted argv plan, never implicit permission to run destructive operations.
|
|
25
|
-
5. Use Node 24 LTS for development and the exact pnpm version in `package.json`; the runtime dependency floor is Node 22.19.0.
|
|
25
|
+
5. Use Node 24 LTS for development and the exact pnpm version in `package.json`; the runtime dependency floor is Node 22.19.0. Select the execution environment and task explicitly with `node scripts/agent.mjs guard`. Local auxiliary checks are limited to the guarded dependency-free script tests; dependency installation and full verification belong to GitHub Actions. Do not retry local dependency restoration, change registries, or treat local reports/idle sessions as CI evidence. The guard applies only to operations routed through it; it cannot prevent direct shell bypass.
|
|
26
26
|
6. Create/reuse a tracking issue and feature branch, implement a regression first, run the full gate, inspect the diff, and open a PR. For requested delivery, merge after required review/CI and branch protection without a separate approval prompt, unless the user limits scope. Important updates continue through the release-delivery rule below. Live-profile install and worktree checkout still require explicit user approval.
|
|
27
27
|
|
|
28
28
|
Use native DSH tools for goals, background jobs and scoped subagents. Use local Git and the GitHub REST API for delivery; no external orchestration daemon, roster or `vcs_*` tool is required. Do not assume a model provider's identity is the assisting agent.
|
|
29
29
|
|
|
30
30
|
## Product and architecture
|
|
31
31
|
|
|
32
|
-
|
|
33
|
-
|
|
34
|
-
|
|
32
|
+
### Confirmed product scope (#455, #456)
|
|
33
|
+
|
|
34
|
+
The user-confirmed direction on 2026-11-14 supersedes conflicting legacy feature
|
|
35
|
+
requirements below: this plugin is a lightweight GitHub Copilot model integration
|
|
36
|
+
for DSH Desktop, not a second agent product. The qualification target is the exact
|
|
37
|
+
official DSH `0.2.2-rc.3` source and published package graph; it is a candidate,
|
|
38
|
+
not supported or delivered until the required CI gates pass.
|
|
39
|
+
|
|
40
|
+
DSH owns application login, AgentLoop, model selection, Auto, parent-model
|
|
41
|
+
following, subagents, tools, Web, permissions, history, context/compaction, and
|
|
42
|
+
Usage. The plugin owns only Copilot's native OAuth/credential integration,
|
|
43
|
+
account-proven model and capability discovery, published-adapter composition,
|
|
44
|
+
and narrowly evidenced Copilot compatibility. Do not add a DeepSeek login check,
|
|
45
|
+
read DeepSeek credentials, add another Copilot login or wire, or redirect failed
|
|
46
|
+
Copilot calls to another provider.
|
|
47
|
+
|
|
48
|
+
Parent/child relationships, inheritance, delegation, lifecycle and scheduling
|
|
49
|
+
follow DSH's native contract, not a plugin-defined policy. Subagent compatibility
|
|
50
|
+
means supplying models to that existing flow. Do not add a child-account
|
|
51
|
+
inheritance mode, parent lookup as credential authority, or plugin-owned child
|
|
52
|
+
routing. Verify authentication and request isolation through the same provider
|
|
53
|
+
contract used by ordinary native calls. A missing public seam is a concrete
|
|
54
|
+
compatibility limit to report, not permission to invent a parallel relationship.
|
|
55
|
+
|
|
56
|
+
Retire plugin-owned Auto and parent-follow policy/UI and custom hosted-search
|
|
57
|
+
execution/routing, preserving bounded compatibility for existing selections and
|
|
58
|
+
histories where needed. Retain GitHub Copilot account quota and useful
|
|
59
|
+
enhancements; remove other functionality only when it is demonstrably redundant
|
|
60
|
+
or unnecessary, not merely because it extends the basic model route. Never delete
|
|
61
|
+
or rewrite user settings, accounts, or history, silently substitute a model, or
|
|
62
|
+
claim a native replacement until the
|
|
63
|
+
exact public API and behavior are verified. Preserve necessary Copilot
|
|
64
|
+
authentication, account/turn isolation, request correctness, and actionable
|
|
65
|
+
diagnostics. HydraFusion/Max are explicitly out of scope (#441).
|
|
66
|
+
|
|
67
|
+
Model-facing DSH capabilities added over time, including native subagent model
|
|
68
|
+
selection and actual child invocation (#456), are compatibility goals for
|
|
69
|
+
account-available Copilot models. Verify each against exact public Core APIs and
|
|
70
|
+
supplier-advertised capabilities with focused tests. Unknown metadata or
|
|
71
|
+
unsupported behavior must fail or diagnose explicitly; do not infer support,
|
|
72
|
+
add model-ID routing rules, patch Core, or claim untested parity.
|
|
73
|
+
|
|
74
|
+
When any later legacy detail in this guide conflicts with this confirmed scope,
|
|
75
|
+
follow this section and the current acceptance criteria in #455/#456. Legacy
|
|
76
|
+
behavior that is still needed to safely read old settings or histories remains
|
|
77
|
+
compatibility code, not a reason to restore retired UI or product features.
|
|
78
|
+
|
|
79
|
+
The last qualified release line is official DSH `0.2.1-rc.3`; its source/artifact CI passed on Windows/Linux in run `40098031196`, while Desktop artifacts/signatures remain unverified. DSH `0.2.2-rc.3` is the current requested candidate and has not passed this repository's required CI. The previous thirteen pins remain historical evidence, not current support or release gates. Do not treat either prerelease as a production Core upgrade recommendation. DSH's built-in `llm-pi-ai` owns the canonical GitHub Copilot provider, OAuth, grant format, token exchange, refresh, and normal model transport.
|
|
80
|
+
|
|
81
|
+
The following is a historical architecture inventory, not a requirement to keep
|
|
82
|
+
every surface as a product feature; apply the confirmed scope above when deciding
|
|
83
|
+
which runtime registrations, UI, and settings remain active:
|
|
35
84
|
|
|
36
85
|
1. A conditional authorization-service bootstrap plus Host controller that joins DSH authorization, credentials, and settings.
|
|
37
86
|
2. A Client Models provider-card contribution with one shared account-state owner, Client-safe Remote descriptors and a nested plugin-owned model-preferences disclosure; embed in an existing configured canonical row, suppress its separate footer controller, and retain footer/old-Core section fallback when no such row is mounted.
|
|
@@ -92,8 +141,22 @@ See `src/compaction-replay.ts` and `docs/manual-compaction-recovery.md` (#349).
|
|
|
92
141
|
|
|
93
142
|
## Approved multi-account ownership extension (#297)
|
|
94
143
|
|
|
144
|
+
Login environments (#424) use only pinned native pi-ai OAuth for GitHub.com and
|
|
145
|
+
validated single-label `tenant.ghe.com` Enterprise Cloud hosts. Preserve host
|
|
146
|
+
binding through identity, duplicate checks, reauthorization and native refresh/
|
|
147
|
+
discovery/request auth. Plugin identity rejects redirects; native OAuth redirect
|
|
148
|
+
control is unavailable in pi-ai 1.1.0 and must not be claimed or emulated with a
|
|
149
|
+
global Fetch patch/second flow. GHES and Enterprise quota remain unsupported.
|
|
150
|
+
See `src/copilot-login-environment.ts` and `docs/copilot-accounts.md`.
|
|
151
|
+
|
|
95
152
|
Identity presentation uses additive `ensureIdentity` Remotes, including explicit-Agent Session lookup. Keep `get` metadata-only; visible surfaces may ensure on their sixty-second cadence. Fresh ten-minute cache avoids requests, same-account consumers join a bounded flight, and failures cool down thirty seconds unless explicitly refreshed. Credential notifications revoke pending work even when token bytes are unchanged; no late cache publication. Quota may settle independently only with account-coherent metadata. Presentation cache never replaces fresh identity validation for switch, reauthorization or duplicate checks. Preserve strict sanitized diagnostics and Session/turn ownership (#309).
|
|
96
153
|
|
|
154
|
+
Models account-management/add controls apply a fifteen-second presentation
|
|
155
|
+
deadline only to metadata/identity reads (#346). A failed initial read offers
|
|
156
|
+
metadata-only Retry; late results and disposal cannot publish stale state.
|
|
157
|
+
Never apply this deadline to add/cancel/switch/reauthorize/remove mutations,
|
|
158
|
+
release their fences, cancel Host work or introduce an automatic retry.
|
|
159
|
+
|
|
97
160
|
Account display names survive freshness expiry in bounded Host memory, never credential invalidation or failed verification. Visible account lists may ensure missing configured names without activating accounts; no disk name cache, credential copying or identity-based authorization. Turn admission captures the first verified name for the frozen account. A missing name may be filled by one existing nonforcing account-bound lookup only during that exact active, uncancelled turn/signal; never after turn/end/disposal. Evidence still requires actual native delivery and never reconstructs completed history (#322).
|
|
98
161
|
|
|
99
162
|
The user approved independently authorized account records in the existing DSH credentials service. The canonical `llm-pi-ai/github-copilot` record remains unchanged as the compatibility account. Additional plugin-owned `github-copilot/account-<opaque-id>` records must be written directly by official pi-ai OAuth through public account-bound stores; never copy/move grants, refill the canonical record, introduce a separate credential storage service, patch Core, or implement another wire/catalog. Native `Models.getAuth()` and DSH `modifyRecord()` remain the refresh and serialization owners.
|
|
@@ -143,6 +206,7 @@ Alpha.25 admits native `subagent/descriptor` v3, already v3 in the retained rc.1
|
|
|
143
206
|
- `src/serialize.ts`, `src/sse.ts`, `src/failure.ts`: protocol conversion and bounded error handling.
|
|
144
207
|
- `src/response-error-body.ts`, `src/request-body-timeout.ts`, `src/request-upload-evidence.ts`: bounded clone-only HTTP error evidence and safe managed upload-timeout guidance. Request-scoped public Node diagnostic events supply numeric local body-write/header/ALPN evidence only after an exact verified `408/user_request_timeout`; absent events, multiple native requests and work limits stay explicit. Always dispose subscriptions when Fetch settles, without changing its arguments, Response/errors, dispatcher, proxy or retry owner. Local body-write completion is not upload duration, kernel ACK, supplier receipt or execution; its absence does not prove incomplete upload. Native failure classification/retry metadata stay unchanged; final JSON bytes are not tokens or a payload limit. A separate explicit opt-in compression setting is default-off and never activated by a 408; never infer overflow, auto-compact, trim history, switch models or add retries from a 408.
|
|
145
208
|
- `src/responses-request-compression.ts`: asynchronous `node:zlib` gzip at `Z_BEST_SPEED` only for exact account-proven official Copilot HTTPS `/responses` JSON POSTs through the existing public Fetch seam. `github-copilot.responsesRequestCompression` defaults false; enforce the 256 KiB minimum, 32 MiB compression-work bound and both 5%/4 KiB savings thresholds. Skips retain the original request with a fixed reason, and cancellation/account/deadline fences run before dispatch. No custom Fetch, other protocol, explicit `auto`/WebSocket, DNS/proxy/dispatcher changes, context-admission or replay changes, resend after an encoding rejection, or new retry. Gzip is wire encoding, not compaction or proof of supplier receipt.
|
|
209
|
+
- Verified 408 error correlation (#276) adds only validated model/protocol, UTC header-observation time and strictly formatted `x-github-request-id` / `x-request-id` response IDs. Missing/malformed IDs stay unavailable; no other header values or new persisted population. IDs do not prove receipt/execution, and zero/unknown image composition cannot justify image-budget guidance.
|
|
146
210
|
- `src/request-body-evidence.ts`, `src/request-body-composition.ts`: bounded numeric original-JSON spans for verified 408s and separately consented request observations. Keep replay validation/recovery at 16 MiB; only diagnostic composition may use the 32 MiB cooperative scanner with 64 Ki-character yields, a two-second monotonic deadline and four scan slots. Do not build a full payload object graph or decode image/replay values. Conversation/tool definitions/top-level system/residual partition total bytes; structural image and opaque replay spans are disjoint conversation subsets. Unknown/limited/cancelled evidence stays explicit. Opted-in large scans start after Fetch invocation without delaying ordinary native delivery; retained numeric rows may update after settlement only behind consent/clear/retention/eviction fences. Retain source strings only for bounded in-flight counting, never in storage/logs. Fetch-to-header time excludes analysis and is not upload duration. With gzip, report original JSON and prepared HTTP-body bytes separately; neither establishes delivered bytes. No automatic mitigation, timeout/retry changes or supplier-limit claim.
|
|
147
211
|
- `src/copilot-stream-liveness.ts`: request-local HTTP/SSE byte-idle observation, paired with the public native adapter's bounded assistant-chunk deadline. Default five-minute byte idle and ten-minute semantic silence; no fake assistant output, private watchdog access, new retry or Core patch. Consumer think time is excluded; explicit WebSocket/auto stays native-only. `chatStreamLiveness: false` restores native-only timing. `chatMaxRequestImageBytes` retains Core's 20 MiB default; smaller explicit settings authorize only native image offload, not hidden history trimming or a guessed supplier limit. Synthetic heartbeat evidence is not production heartbeat proof.
|
|
148
212
|
- `tests/`: unit and integration evidence; mirror the source area being changed.
|
|
@@ -151,26 +215,28 @@ Alpha.25 admits native `subagent/descriptor` v3, already v3 in the retained rc.1
|
|
|
151
215
|
- `lib/`: generated release output; never edit it.
|
|
152
216
|
|
|
153
217
|
## Non-negotiable invariants
|
|
154
|
-
|
|
155
|
-
Auxiliary classifier disable proof accepts explicit supplier `off` or the
|
|
156
|
-
selected protocol's native `none` (Responses/Completions) or `disabled`
|
|
157
|
-
(Anthropic), scoped to the isolated classifier model only. Missing/empty effort
|
|
158
|
-
metadata remains unproven. Strict ephemeral candidate counts record one fixed
|
|
159
|
-
first-rejection reason per candidate and distinguish native off preparation
|
|
160
|
-
failure; no candidate IDs, raw metadata, prompts or new persistent population.
|
|
161
|
-
No-fit warnings contain fixed codes only. Legacy absent evidence stays unknown.
|
|
162
|
-
|
|
163
|
-
Auxiliary context projection reserves current/nearest user text and, for exact
|
|
164
|
-
continuations, a substantive anchor within twelve preceding user messages plus
|
|
165
|
-
its user chain. Keep 12 rows/1600 characters per row/8000 serialized characters.
|
|
166
|
-
Task text limitations, absent anchors and task nontext content block downshift;
|
|
167
|
-
incidental history omissions alone do not. Retained text is not semantic
|
|
168
|
-
completeness. Preserve genuine classifier unknown, off/no-tools/one-call
|
|
169
|
-
behavior and native Chat input. Optional strict projection/returned-demand
|
|
170
|
-
evidence is content-free and ephemeral, never a new persistent population.
|
|
218
|
+
|
|
219
|
+
Auxiliary classifier disable proof accepts explicit supplier `off` or the
|
|
220
|
+
selected protocol's native `none` (Responses/Completions) or `disabled`
|
|
221
|
+
(Anthropic), scoped to the isolated classifier model only. Missing/empty effort
|
|
222
|
+
metadata remains unproven. Strict ephemeral candidate counts record one fixed
|
|
223
|
+
first-rejection reason per candidate and distinguish native off preparation
|
|
224
|
+
failure; no candidate IDs, raw metadata, prompts or new persistent population.
|
|
225
|
+
No-fit warnings contain fixed codes only. Legacy absent evidence stays unknown.
|
|
226
|
+
|
|
227
|
+
Auxiliary context projection reserves current/nearest user text and, for exact
|
|
228
|
+
continuations, a substantive anchor within twelve preceding user messages plus
|
|
229
|
+
its user chain. Keep 12 rows/1600 characters per row/8000 serialized characters.
|
|
230
|
+
Task text limitations, absent anchors and task nontext content block downshift;
|
|
231
|
+
incidental history omissions alone do not. Retained text is not semantic
|
|
232
|
+
completeness. Preserve genuine classifier unknown, off/no-tools/one-call
|
|
233
|
+
behavior and native Chat input. Optional strict projection/returned-demand
|
|
234
|
+
evidence is content-free and ephemeral, never a new persistent population.
|
|
171
235
|
|
|
172
236
|
- Explicit replay recovery (#279, #289) is default-off and bound to the initiating native request signal, Session, model and current account proof. Only exact verified scope failures capture bounded full-item fingerprints; no replay bytes reach Client or storage. Public Session running/error snapshots trigger read-only notices on open/settled turns, never polling or durable recovery events. Two-stage confirmation chooses next matching turn (all steps/retries until turn/end) or bounded Session consent, omitting matching old encrypted items and their item summaries only on outgoing requests, never durable history or new reasoning. Preserve get/setEnabled descriptor identities and legacy session-consent semantics; authorize is additive. Active-turn writes, ambient-scope calls and automatic retries are forbidden. Expiry, disposal and proof discontinuity revoke evidence. See `docs/model-compatibility-acceptance.md`.
|
|
173
237
|
|
|
238
|
+
- Cold-open scheduled recovery (#433) refolds only the latest native terminal scope-failure classification/sequence through a separate public projection. Exclude copied fork/child prefixes and clear on later turns. This preserves the explicit persistent continuation entry after request evidence expires or the picker changes; it does not reconstruct fingerprints, invalid items or account origin. Keep missing diagnostics unknown, loss disclosure and confirmed Settings CAS; never enable, resend or retry automatically.
|
|
239
|
+
|
|
174
240
|
- Do not implement a second general wire adapter or independently maintained static Copilot model catalog. The account-scoped route composes the published adapter and SDK with validated supplier metadata.
|
|
175
241
|
- Protocol and capability corrections must follow authenticated, current account metadata; new model IDs must not need new implementation tables. Native pi metadata may be reused only where it agrees with advertised endpoints and capabilities. Matching IDs alone do not prove correctness or authorize migration back into another Core catalog. Preserve old bounded ownership journals solely for verified restoration of legacy writes, never for new global protocol overrides.
|
|
176
242
|
- Native Auto review compatibility must preserve Core's frozen request and strict fail-closed verdict ownership. Automatic reviewer-only omission uses the documented public `internal/get` service-read waterfall, exact Loader root ownership and independently imported official rc.2 `apply` callback equality through same-profile `PluginPackages.packageOf` facts. Clone before native `stream` delegation only for account-proven managed Responses. Recheck identity after await and revoke on disposal; aliases, descendants, impostors and unknown package identity remain native with bounded diagnostics. Never activate a second reviewer or use private caches/registries. Missing optional reviewer packages do not block plugin startup. Ordinary concurrent Chat stays unchanged. The separate legacy `github-copilot.responsesOmitTemperature` override defaults off and affects all managed Responses only when explicitly enabled; it is not the automatic reviewer policy or a capability claim. Never infer support from thinking metadata, match reviewer prompts/models/errors, intercept canonical routes, retry/resend, migrate settings, rewrite verdicts or change permissions. See `docs/auto-review-sampling.md`.
|
|
@@ -232,8 +298,9 @@ The retained upstream baselines and current qualification target are:
|
|
|
232
298
|
- Official tag `dsh-v0.2.0-rc.2`, commit `639ed015397290b3745d163aafe02ffee4aa3f84`; the signed installed Windows Desktop descriptor identifies the rc.2 shared peer graph.
|
|
233
299
|
- Official tag `dsh-v0.2.1-alpha.4`, commit `86a402200d95fecef4529d969836f1fe13c6cb0d`; historical alpha.16 source/npm qualification only.
|
|
234
300
|
- Official tag `dsh-v0.2.1-alpha.5`, commit `1517a4dbca0a2789ff1d41ba439600f8547d23fa`; exact source/npm qualification is separate from unverified candidate Desktop artifacts/signatures.
|
|
301
|
+
- Official tag `dsh-v0.2.1-rc.3`, commit `1f81c047fc48fa190a683e469daa699857e9afe8`; prerelease target with a public `WebRuntime` Volatile-provider contract change. Source and published artifacts require exact CI qualification; Desktop artifacts/signatures remain unverified.
|
|
235
302
|
|
|
236
|
-
The release admission, development dependency and CI targets are exact official `0.2.1-
|
|
303
|
+
The release admission, development dependency and CI targets are exact official `0.2.1-rc.3`; the earlier thirteen pins remain historical evidence only. CI runs unchanged tagged-source and isolated exact published-npm-artifact fixtures on Windows and Linux. Public APIs require pi-ai `1.1.0`, Cordis `4.0.5`, cordis-plugin-loader `1.0.6`, schemastery `3.18.5` and storage-domain-compatible Zod `4.4.3`. The current fixture must await serialized `agent/created`, avoid new synchronous Session-history reads, and preserve MCP/PTC/workflow/Sandbox/Shell/image-offload/Team ownership. Native gateway fixtures bind an explicit public owner Peer and interactive Client carrier; Session-controller fixtures register native resources. Synthetic identities never authorize live access. Neither source nor synthetic tests prove live endpoints, plugin activation, publication or loaded runtime state. See the [rc.3 qualification evidence](./docs/official-first-021-rc3.md); passing source/artifact CI does not authorize Core implementation rewrites or experimental durable records.
|
|
237
304
|
|
|
238
305
|
These pins document compatibility evidence. They do not authorize creating another controlled Core patch or making one a prerequisite for new plugin fixes.
|
|
239
306
|
|
|
@@ -299,10 +366,84 @@ Desktop plugin upgrades do not necessarily reconcile profile-local copies of Hos
|
|
|
299
366
|
|
|
300
367
|
## Mechanical verification
|
|
301
368
|
|
|
302
|
-
|
|
369
|
+
When a task explicitly requires post-upgrade Desktop/UI acceptance, use acceptance
|
|
370
|
+
contract/report schema 2 described in `docs/agent-acceptance.md`. Exact-head CI
|
|
371
|
+
and installed-on-disk evidence cannot replace live behavior or the public loaded
|
|
372
|
+
plugin version. Attempt safe authorized checks on an already-running Desktop;
|
|
373
|
+
unreliable local npm is not a reason to skip them. Use existing computer-use
|
|
374
|
+
tools, never shell activation or a repository script as an App controller.
|
|
375
|
+
Begin with current app discovery, not a historical "already open" claim. If not
|
|
376
|
+
running, start only with explicit launch authorization via controlled `start_app`
|
|
377
|
+
using the exact approved target; then verify discovery and fresh UI, not merely
|
|
378
|
+
the launch receipt. Do not start an already-running app again. A welcome screen
|
|
379
|
+
is not automatically an auth blocker: inspect an official safe skip first. DSH's
|
|
380
|
+
Add API Key -> Set up later path does not submit/store a key or authenticate;
|
|
381
|
+
use it only when actually exposed, within tool permission rules. Never infer
|
|
382
|
+
Copilot account invalidity from welcome UI or bypass real authentication/warnings.
|
|
383
|
+
Welcome dismissal may replace the window: rediscover app/window and read its fresh
|
|
384
|
+
tree before acting, rather than retrying a stale window on an empty immediate diff.
|
|
385
|
+
Honor user-input interruption: reread UI before retrying the same permitted action.
|
|
386
|
+
Before handoff, freshly discover the current app and inspect the target panel or
|
|
387
|
+
workspace, reporting the observation time only; past success does not establish
|
|
388
|
+
current running state or guarantee the app remains running later.
|
|
389
|
+
An action receipt or empty immediate diff is not a navigation failure: obtain
|
|
390
|
+
a fresh post-action `get_window_state` observation first. Keep one attempt per
|
|
391
|
+
supported navigation method, at most two different methods, then report precise
|
|
392
|
+
`automation-blocked` and request the named panel once. User absence or an
|
|
393
|
+
unanswered request never grants permission or proves the panel opened.
|
|
394
|
+
App unavailable, restart/install, account/OAuth/paid actions outside explicit
|
|
395
|
+
permission stay blocked. Do not repeat exhausted methods on ordinary continuation.
|
|
396
|
+
Record only fixed action/outcome codes, numeric times and version/source facts;
|
|
397
|
+
never upload identities, credentials or conversation content. Unknown loaded
|
|
398
|
+
version permits qualified observations only, not a version-specific fix claim.
|
|
399
|
+
For formal upgrade acceptance, prefer the published exact-version GitHub Release
|
|
400
|
+
asset canonical URL, never a local source directory, build, link or worktree.
|
|
401
|
+
A downloaded official tgz is a verified GitHub cache, not a local build; use it
|
|
402
|
+
only as a documented fallback when native URL delivery is unavailable/rejected.
|
|
403
|
+
Record exact source URL/version, archive and Release SHA-256, numeric observation
|
|
404
|
+
time and fixed fallback reason separately. Matching hashes do not grant install
|
|
405
|
+
or restart permission or prove the resulting runtime loaded. The consistency
|
|
406
|
+
checker never downloads/installs or independently authenticates this provenance.
|
|
407
|
+
Missing/not-run/blocked/error/timeout mandatory evidence cannot pass acceptance; even a
|
|
408
|
+
consistent complete report is not trusted proof of execution or automatic closure.
|
|
409
|
+
Keep required-check completeness separate from issue disposition. Controlled
|
|
410
|
+
regressions can exercise timers, never-resolving requests, late results and
|
|
411
|
+
simulated disconnects; production Desktop fault injection is different. Do not
|
|
412
|
+
disconnect networking, alter proxies/accounts or trigger paid requests to fill
|
|
413
|
+
coverage without specific permission. After a specific defect is fixed, relevant
|
|
414
|
+
controlled regressions/exact CI pass, release/install/load premises are met and
|
|
415
|
+
normal live checks do not reproduce it, explicit user risk acceptance may close
|
|
416
|
+
with "fixed/not reproduced; untested faults listed; reopen on recurrence".
|
|
417
|
+
Do not claim the original root cause or production fault coverage was proven.
|
|
418
|
+
Lack of safe/non-destructive production injection alone is not an indefinite
|
|
419
|
+
closure blocker. Known failures/reproduction, critical safety gaps and mandatory
|
|
420
|
+
requirements remain blockers; residual-risk disposition cannot relabel them
|
|
421
|
+
passed or authorize automatic issue closure.
|
|
422
|
+
|
|
423
|
+
For the opt-in task acceptance pilot, define observable requirements before
|
|
424
|
+
implementation and validate the clean candidate with
|
|
425
|
+
`node scripts/agent.mjs accept --contract CONTRACT_FILE --report REPORT_FILE`.
|
|
426
|
+
See [acceptance evidence](https://github.com/cloga/dsh-github-copilot/blob/main/docs/agent-acceptance.md): exact commit/contract and
|
|
427
|
+
local file integrity are checked, not execution, environment truth, reviewer
|
|
428
|
+
independence or delivery permission. Keep reports outside Git and never upload
|
|
429
|
+
live diagnostics automatically. Failed, blocked and not-run requirements cannot
|
|
430
|
+
pass; new commits require new evidence. Existing review/CI/release gates remain
|
|
431
|
+
authoritative. This tooling does not activate agents or access live profiles.
|
|
432
|
+
|
|
433
|
+
Choose a bounded local auxiliary check or authoritative remote evidence explicitly
|
|
434
|
+
with `node scripts/agent.mjs guard --task TASK_ID --environment local-auxiliary
|
|
435
|
+
--operation scripts-test` or `--environment github-actions-evidence
|
|
436
|
+
--operation ci-evidence --head FULL_COMMIT_SHA`. The dependency-free scripts
|
|
437
|
+
tests are the only guarded local verification here. Do not run dependency
|
|
438
|
+
installation/recovery locally; full install, build, types, integration and
|
|
439
|
+
package verification use the existing GitHub Actions workflow. See
|
|
440
|
+
[environment and CI evidence guardrails](./docs/environment-evidence-guardrails.md).
|
|
441
|
+
The guard covers only operations invoked through this entry point and is not a
|
|
442
|
+
shell sandbox.
|
|
443
|
+
|
|
444
|
+
The full gate and package commands, run by the existing CI workflow, are:
|
|
303
445
|
|
|
304
446
|
```sh
|
|
305
|
-
pnpm install --frozen-lockfile
|
|
306
447
|
pnpm verify
|
|
307
448
|
pnpm pack --pack-destination artifacts
|
|
308
449
|
```
|
|
@@ -311,9 +452,9 @@ Then run `pnpm verify:tarball -- artifacts/dsh-github-copilot-<package-version>.
|
|
|
311
452
|
|
|
312
453
|
`pnpm verify` checks the Agent contract, source and local test types, baseline markers, a clean build, Vitest tests, Node tooling tests, and real built Host import/Client-loader/Remote smoke. `tests/fixtures` are intentionally excluded from local test typecheck because they import source from a separate pinned Core checkout. The checked-in code must pass; never suppress compiler errors or weaken a test to get a green report.
|
|
313
454
|
|
|
314
|
-
If
|
|
455
|
+
If a historical/approved local installation attempt is blocked solely by an enterprise registry or network policy while GitHub Actions can obtain unchanged pinned packages from an authorized official registry, record it as **local validation blocked**, not passed. Do not repeat dependency recovery, switch sources, or expand permissions. A PR may proceed with that limitation disclosed; the complete required GitHub CI matrix, including install, tests, build and package checks, is authoritative before merge. Never weaken or skip CI, substitute dependencies, bypass organizational restrictions, claim unrun local gates succeeded, or tag/release a revision whose required CI is not green. If CI has the same failure, resolve it through approved infrastructure rather than bypassing it.
|
|
315
456
|
|
|
316
|
-
The release CI matrix targets only exact official `0.2.1-
|
|
457
|
+
The release CI matrix targets only exact official `0.2.1-rc.3` on Windows and Linux; earlier pins are not support gates. It runs the unchanged tagged-source runtime fixture, optional native Chat fixture, exact published-artifact adapter fixture and all 28 native reviewer regressions without skips. This is a required gate, not evidence that an unexecuted qualification passed. `verify:upstream` is static seam-marker evidence. `verify:controlled-core` exclusively installs a temporary config fixture, refuses an existing target, and removes only its own file; it is not full plugin activation. Published-artifact synthetic adapter fixtures do not prove live provider transport. The release job must wait for the complete reusable CI matrix on the tagged revision, then verify its own packed bytes before publishing.
|
|
317
458
|
|
|
318
459
|
### Evidence and side effects
|
|
319
460
|
|
|
@@ -371,19 +512,19 @@ Completed-turn Usage diagnostics (#259) are read-only plugin conversation data a
|
|
|
371
512
|
Auto task routing (#258) uses current `model_picker_category` facts, never model
|
|
372
513
|
names, effort or context capacity as a quality category. Hard eligibility/input
|
|
373
514
|
fit precede task/preference policy; unknown category and uncertain task evidence
|
|
374
|
-
remain explicit. High-cost-v4 retains every eligible fitting model across
|
|
375
|
-
categories with positive weight. Task/preference sets the favored target, not
|
|
376
|
-
hard category exclusion. Per-model category factors are target 1, second 0.25,
|
|
377
|
-
third 0.05, unknown 0.02 in the existing order, then multiplied by cost/recency.
|
|
378
|
-
These are uncalibrated trial factors, not fixed category probability quotas;
|
|
379
|
-
candidate populations affect shares. Ordinary weight 1 receives finite
|
|
380
|
-
previous-model multiplier 1.5; marked base 0.2 decays to 0.02 only for the previous
|
|
381
|
-
model. One-turn recency resets after a different model, not a hidden streak
|
|
382
|
-
counter or task-failure inference. Preserve v1/v2/v3 historical codecs/cohorts and
|
|
383
|
-
their original explanation. Fit is not task
|
|
384
|
-
success; non-target draws are intentional opportunity, not absence/failure of
|
|
385
|
-
target candidates. Never infer incapability or add task-failure escalation.
|
|
386
|
-
Capture actual reasons once
|
|
515
|
+
remain explicit. High-cost-v4 retains every eligible fitting model across
|
|
516
|
+
categories with positive weight. Task/preference sets the favored target, not
|
|
517
|
+
hard category exclusion. Per-model category factors are target 1, second 0.25,
|
|
518
|
+
third 0.05, unknown 0.02 in the existing order, then multiplied by cost/recency.
|
|
519
|
+
These are uncalibrated trial factors, not fixed category probability quotas;
|
|
520
|
+
candidate populations affect shares. Ordinary weight 1 receives finite
|
|
521
|
+
previous-model multiplier 1.5; marked base 0.2 decays to 0.02 only for the previous
|
|
522
|
+
model. One-turn recency resets after a different model, not a hidden streak
|
|
523
|
+
counter or task-failure inference. Preserve v1/v2/v3 historical codecs/cohorts and
|
|
524
|
+
their original explanation. Fit is not task
|
|
525
|
+
success; non-target draws are intentional opportunity, not absence/failure of
|
|
526
|
+
target candidates. Never infer incapability or add task-failure escalation.
|
|
527
|
+
Capture actual reasons once
|
|
387
528
|
per turn without durable decision events or changing Usage.
|
|
388
529
|
`autoSemanticAssessment` is default-on by explicit user rollout request (#267),
|
|
389
530
|
only for locally unknown demand; preserve explicit false opt-out. One bounded concrete
|
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,56 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 0.1.0-alpha.1.dsh.0.2.2.rc.3 (prepared)
|
|
4
|
+
|
|
5
|
+
- Begin narrowing the product to account-authorized Copilot models through DSH's published native adapter. Plugin-owned Auto and parent-follow routing and hosted-search composition are retired in the candidate; preserve account quota and review other enhancements before removing only demonstrably unnecessary functionality.
|
|
6
|
+
- Hide inactive Auto and parent-follow settings and remove the obsolete Auto high-cost marking control without changing saved preferences; retain legacy settings and Remote for compatibility.
|
|
7
|
+
- Preserve historical account, model and incomplete-Usage evidence separately from retired Auto selection UI; never reconstruct account history or replace native Usage.
|
|
8
|
+
- Label retired Auto and parent-follow documentation as historical and omit the obsolete Auto UI mockup from the package.
|
|
9
|
+
- Require account-metadata-driven native subagent model selection and actual child invocation, including supported Thinking and concurrent/account-bound request checks; synthetic exact-source fixtures passed on Windows and Linux, but do not establish live supplier or Desktop behavior.
|
|
10
|
+
- Target DSH ownership of parent/child relationships, inheritance and scheduling; legacy dedicated-role orchestration still requires safe retirement.
|
|
11
|
+
- Remove HydraFusion/Max from scope. No additional login, Core changes, model-name routing rules, silent provider substitution, publication, profile installation, or Desktop restart is included.
|
|
12
|
+
- Target official DSH 0.2.2-rc.3. Required Windows/Linux CI, pnpm-lock alignment, publication, profile installation, and loaded-runtime compatibility remain unverified.
|
|
13
|
+
|
|
14
|
+
## 0.1.0-alpha.5.dsh.0.2.1.rc.3 (prepared)
|
|
15
|
+
|
|
16
|
+
- Replace the stale rc.2 Desktop lifecycle heading with version-neutral guidance. Recommend a full exit and restart only when the native plugin manager reports `restart-required`; do not repeatedly toggle an Off plugin when the manager reports only pending service dependencies.
|
|
17
|
+
- Keep historical rc.2 Desktop observations distinct from current rc.3 synthetic Loader evidence, and synchronize the English/Chinese README and user-visible copy regressions (#453).
|
|
18
|
+
- Prepare same-Core alpha.5 metadata only. The rc.3 release mapping remains pending; no tag, GitHub Release, npm publication, profile installation or Desktop restart is included.
|
|
19
|
+
|
|
20
|
+
## 0.1.0-alpha.4.dsh.0.2.1.rc.3 (prepared)
|
|
21
|
+
|
|
22
|
+
- Carry forward bounded Responses replay refusal diagnostics from retired draft #218 under #446: fixed reasons, zero-based input positions, allowlisted type/status and field-presence booleans through the existing native `INVALID_REQUEST` surface. No IDs, summaries, tool data, unknown values or encrypted bytes enter diagnostics.
|
|
23
|
+
- Exercise current pinned pi-ai 1.1.0 synthetic two-turn summary-only rejection and terminal encryption backfill, preserving original history, exact opaque bytes and `call_id` pairing. Retain existing replay acceptance, account isolation, consent and cancellation ownership; no new retry, history deletion or model switch.
|
|
24
|
+
- Prepare the next same-Core candidate metadata for required PR validation only. No tag, merge, publication, profile installation, restart or live model call is authorized.
|
|
25
|
+
|
|
26
|
+
## 0.1.0-alpha.3.dsh.0.2.1.rc.3 (prepared)
|
|
27
|
+
|
|
28
|
+
- Explain projected-image admission failures through the standard native error path with bounded model, projected/allowed MIME, projected role/position and current build details (#426). Retain the existing fail-closed gate, explicit account restrictions and native projection ownership.
|
|
29
|
+
- Explain why historical images can block text-only continuations and offer explicit future-turn recovery choices. No automatic model switch, retry, image conversion/removal, history mutation or new diagnostic collector.
|
|
30
|
+
- Auto still checks general vision capability before candidate-specific projection is available. This change does not establish the original incident's model, image format, trigger block or loaded version, and does not claim live recovery. PR-only preparation does not authorize merge, publication, installation or restart.
|
|
31
|
+
|
|
32
|
+
## 0.1.0-alpha.2.dsh.0.2.1.rc.3 (prepared)
|
|
33
|
+
|
|
34
|
+
- Bound account-management metadata and identity reads to fifteen seconds, provide metadata-only Retry after initial failure, and discard late results (#346). Account mutations retain their original locks and settlement; no Host cancellation or automatic retry.
|
|
35
|
+
- Align recovery and context notices with native composer side clearance on narrow and embedded layouts, avoid double-constraining nested disclosures, and distinguish primary Enable from quiet Cancel (#317). Explicit loss consent and native history/compaction ownership remain unchanged.
|
|
36
|
+
- Add validated model/protocol, UTC header-observation time and strictly formatted supplier request IDs to verified 408 diagnostics (#276). Recommend image-offload changes only when recognized image bytes are present. No transport, retry, timeout, account or stored-diagnostic changes; production timeout cause/frequency remains unproven.
|
|
37
|
+
- Retain exact DSH 0.2.1-rc.3 admission and the documented native hot-readd limitation. No Core changes, profile installation, sign-in, paid model probes or restart.
|
|
38
|
+
|
|
39
|
+
## 0.1.0-alpha.1.dsh.0.2.1.rc.3 (prepared)
|
|
40
|
+
|
|
41
|
+
- Target exact official DSH 0.2.1-rc.3 at `1f81c047fc48fa190a683e469daa699857e9afe8` (#432, #435). Align engines, public peers, exact reviewer ownership and Windows/Linux tagged-source and published-artifact qualification without Core changes.
|
|
42
|
+
- Adapt the plugin-owned search runtime to the public rc.3 `WebRuntime` Volatile-provider contract. Preserve native provider, account, transport, retry and configuration ownership.
|
|
43
|
+
- Retain cold-open scheduled replay-scope failure evidence for the explicit continuation policy control (#433). Missing ephemeral fingerprints remain unknown; no automatic enable, retry, account fallback or stored-history mutation.
|
|
44
|
+
- Parse concatenated Zstandard frames independently in the offline history maintenance tool, retaining bounded structural checks, source hashes and detached-copy-only output. No live history repair is performed.
|
|
45
|
+
- Restore this exact source-bound release-notes section and test the tracked package/changelog preflight before publication (#436). Immutable tags/releases, OIDC publication and identical GitHub/npm archive verification remain unchanged.
|
|
46
|
+
- DSH rc.3 is a prerelease, not a production upgrade recommendation. Desktop artifacts/signatures, live activation, OAuth and model/search calls remain unverified; publication does not authorize profile installation, migration or restart. Rc.2 hosts must retain their existing compatible plugin.
|
|
47
|
+
|
|
48
|
+
## 0.1.0-alpha.2.dsh.0.2.1.alpha.5 (prepared)
|
|
49
|
+
|
|
50
|
+
- Add a login-environment choice for independently authorized GitHub.com and GitHub Enterprise Cloud data-residency (`tenant.ghe.com`) Copilot accounts through pinned pi-ai 1.1.0 (#424). Validate the tenant before login; bind device links, identity, duplicate checks and reauthorization to its host.
|
|
51
|
+
- Retain account-local native refresh, model discovery and the existing published adapter with OAuth-derived trusted endpoints. Show tenant hosts beside verified account names in Models, Credits and historical Account evidence. Preserve existing GitHub.com Remote methods and add strict environment-aware methods.
|
|
52
|
+
- GitHub Enterprise Server and Enterprise quota remain unsupported. Plugin identity rejects redirects; native OAuth exposes no redirect-control seam, so OAuth redirect rejection is not claimed. No second OAuth/model wire, Core changes, live sign-in, settings migration, installation or restart.
|
|
53
|
+
|
|
3
54
|
## 0.1.0-alpha.1.dsh.0.2.1.alpha.5 (prepared)
|
|
4
55
|
|
|
5
56
|
- Start an independent plugin sequence for each exact DSH Core at `0.1.0-alpha.1.dsh.<Core>`; same-Core fixes increment `alpha.N`. Validate the explicit mapping, suffix, engines and baseline together. Retain published alpha.15/alpha.16 anchors; no code/history reset, new npm channel or automatic updater integration.
|
package/CONTRIBUTING.md
CHANGED
|
@@ -33,6 +33,24 @@ Core inspection is read-only. Isolated tests may use unchanged pinned Core artif
|
|
|
33
33
|
|
|
34
34
|
Generated `lib/` output, archives, `.env`, tokens, local credentials, machine state and production screenshots with real authorization codes must not be committed. Use synthetic fixtures for screenshots and report staged UI honestly.
|
|
35
35
|
|
|
36
|
+
The project disables pnpm's minimum package publication age. Newly published
|
|
37
|
+
dependencies can therefore be installed immediately; lockfile integrity and
|
|
38
|
+
the required CI and release checks still apply.
|
|
39
|
+
|
|
40
|
+
## Task acceptance pilot
|
|
41
|
+
|
|
42
|
+
Define requirement IDs, expected behavior, verification methods and non-goals
|
|
43
|
+
before implementation. On the clean committed candidate, use
|
|
44
|
+
`node scripts/agent.mjs accept --contract CONTRACT_FILE --report REPORT_FILE`.
|
|
45
|
+
The [acceptance evidence guide](https://github.com/cloga/dsh-github-copilot/blob/main/docs/agent-acceptance.md) defines the bounded
|
|
46
|
+
contract and report formats. Keep evidence outside Git, record exact commit and
|
|
47
|
+
contract/artifact hashes, and distinguish failed, blocked and not-run outcomes.
|
|
48
|
+
This verifies consistency only, not test execution, independent review or live
|
|
49
|
+
behavior; it never replaces required reviews or CI. Review artifacts before any
|
|
50
|
+
explicit sharing and do not upload raw live diagnostics. Subsequent commits need
|
|
51
|
+
fresh evidence. The current-Core PR-template target is mechanically checked
|
|
52
|
+
against package metadata without altering historical evidence.
|
|
53
|
+
|
|
36
54
|
## Release changes
|
|
37
55
|
|
|
38
56
|
GitHub Releases and npm are the default distribution channels for every new version, superseding the Release-only decision in #43 at the user's request. The public package uses the exact same verified tarball in both channels. No automatic npm opt-out is allowed. See [npm distribution](./docs/npm-distribution.md) for initial maintainer bootstrap, OIDC, retry recovery and organizational access requirements.
|