dsh-github-copilot 0.1.0-alpha.2.dsh.0.2.1.alpha.5 → 0.1.0-alpha.2.dsh.0.2.1.rc.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/AGENTS.md CHANGED
@@ -29,7 +29,7 @@ Use native DSH tools for goals, background jobs and scoped subagents. Use local
29
29
 
30
30
  ## Product and architecture
31
31
 
32
- `dsh-github-copilot` currently admits and targets only official DSH `0.2.1-alpha.5`. Twelve earlier DSH pins remain in `deployment-baseline.json` as historical evidence, not current support or CI release gates. Alpha.5 Desktop artifacts/signatures are unverified; the signed rc.2 Desktop evidence is historical peer ownership only. Rc.2 installations must retain alpha.15 or their existing compatible plugin. It does not own a general Copilot chat adapter. DSH's built-in `llm-pi-ai` mount owns the GitHub Copilot provider, catalog, OAuth method and grant format, token exchange, refresh, and normal model transport.
32
+ `dsh-github-copilot` currently admits and targets only official DSH `0.2.1-rc.3`, a prerelease. The prior thirteen DSH pins remain in `deployment-baseline.json` as historical evidence, not current support or CI release gates. Rc.3 source/artifact CI qualification passed on Windows/Linux in run `40098031196`; Desktop artifacts/signatures remain unverified. Do not treat this unpublished candidate as a production Core upgrade recommendation. The signed rc.2 Desktop evidence is historical peer ownership only. Rc.2 installations must retain alpha.15 or their existing compatible plugin. It does not own a general Copilot chat adapter. DSH's built-in `llm-pi-ai` mount owns the GitHub Copilot provider, catalog, OAuth method and grant format, token exchange, refresh, and normal model transport.
33
33
 
34
34
  This repository maintains twelve narrow surfaces and ownership boundaries:
35
35
 
@@ -91,17 +91,23 @@ codes, never raw errors. Installation alone neither selects nor invokes recovery
91
91
  See `src/compaction-replay.ts` and `docs/manual-compaction-recovery.md` (#349).
92
92
 
93
93
  ## Approved multi-account ownership extension (#297)
94
-
95
- Login environments (#424) use only pinned native pi-ai OAuth for GitHub.com and
96
- validated single-label `tenant.ghe.com` Enterprise Cloud hosts. Preserve host
97
- binding through identity, duplicate checks, reauthorization and native refresh/
98
- discovery/request auth. Plugin identity rejects redirects; native OAuth redirect
99
- control is unavailable in pi-ai 1.1.0 and must not be claimed or emulated with a
100
- global Fetch patch/second flow. GHES and Enterprise quota remain unsupported.
101
- See `src/copilot-login-environment.ts` and `docs/copilot-accounts.md`.
94
+
95
+ Login environments (#424) use only pinned native pi-ai OAuth for GitHub.com and
96
+ validated single-label `tenant.ghe.com` Enterprise Cloud hosts. Preserve host
97
+ binding through identity, duplicate checks, reauthorization and native refresh/
98
+ discovery/request auth. Plugin identity rejects redirects; native OAuth redirect
99
+ control is unavailable in pi-ai 1.1.0 and must not be claimed or emulated with a
100
+ global Fetch patch/second flow. GHES and Enterprise quota remain unsupported.
101
+ See `src/copilot-login-environment.ts` and `docs/copilot-accounts.md`.
102
102
 
103
103
  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).
104
104
 
105
+ Models account-management/add controls apply a fifteen-second presentation
106
+ deadline only to metadata/identity reads (#346). A failed initial read offers
107
+ metadata-only Retry; late results and disposal cannot publish stale state.
108
+ Never apply this deadline to add/cancel/switch/reauthorize/remove mutations,
109
+ release their fences, cancel Host work or introduce an automatic retry.
110
+
105
111
  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).
106
112
 
107
113
  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.
@@ -151,6 +157,7 @@ Alpha.25 admits native `subagent/descriptor` v3, already v3 in the retained rc.1
151
157
  - `src/serialize.ts`, `src/sse.ts`, `src/failure.ts`: protocol conversion and bounded error handling.
152
158
  - `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.
153
159
  - `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.
160
+ - 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.
154
161
  - `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.
155
162
  - `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.
156
163
  - `tests/`: unit and integration evidence; mirror the source area being changed.
@@ -159,26 +166,28 @@ Alpha.25 admits native `subagent/descriptor` v3, already v3 in the retained rc.1
159
166
  - `lib/`: generated release output; never edit it.
160
167
 
161
168
  ## Non-negotiable invariants
162
-
163
- Auxiliary classifier disable proof accepts explicit supplier `off` or the
164
- selected protocol's native `none` (Responses/Completions) or `disabled`
165
- (Anthropic), scoped to the isolated classifier model only. Missing/empty effort
166
- metadata remains unproven. Strict ephemeral candidate counts record one fixed
167
- first-rejection reason per candidate and distinguish native off preparation
168
- failure; no candidate IDs, raw metadata, prompts or new persistent population.
169
- No-fit warnings contain fixed codes only. Legacy absent evidence stays unknown.
170
-
171
- Auxiliary context projection reserves current/nearest user text and, for exact
172
- continuations, a substantive anchor within twelve preceding user messages plus
173
- its user chain. Keep 12 rows/1600 characters per row/8000 serialized characters.
174
- Task text limitations, absent anchors and task nontext content block downshift;
175
- incidental history omissions alone do not. Retained text is not semantic
176
- completeness. Preserve genuine classifier unknown, off/no-tools/one-call
177
- behavior and native Chat input. Optional strict projection/returned-demand
178
- evidence is content-free and ephemeral, never a new persistent population.
169
+
170
+ Auxiliary classifier disable proof accepts explicit supplier `off` or the
171
+ selected protocol's native `none` (Responses/Completions) or `disabled`
172
+ (Anthropic), scoped to the isolated classifier model only. Missing/empty effort
173
+ metadata remains unproven. Strict ephemeral candidate counts record one fixed
174
+ first-rejection reason per candidate and distinguish native off preparation
175
+ failure; no candidate IDs, raw metadata, prompts or new persistent population.
176
+ No-fit warnings contain fixed codes only. Legacy absent evidence stays unknown.
177
+
178
+ Auxiliary context projection reserves current/nearest user text and, for exact
179
+ continuations, a substantive anchor within twelve preceding user messages plus
180
+ its user chain. Keep 12 rows/1600 characters per row/8000 serialized characters.
181
+ Task text limitations, absent anchors and task nontext content block downshift;
182
+ incidental history omissions alone do not. Retained text is not semantic
183
+ completeness. Preserve genuine classifier unknown, off/no-tools/one-call
184
+ behavior and native Chat input. Optional strict projection/returned-demand
185
+ evidence is content-free and ephemeral, never a new persistent population.
179
186
 
180
187
  - 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`.
181
188
 
189
+ - 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.
190
+
182
191
  - 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.
183
192
  - 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.
184
193
  - 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`.
@@ -240,8 +249,9 @@ The retained upstream baselines and current qualification target are:
240
249
  - Official tag `dsh-v0.2.0-rc.2`, commit `639ed015397290b3745d163aafe02ffee4aa3f84`; the signed installed Windows Desktop descriptor identifies the rc.2 shared peer graph.
241
250
  - Official tag `dsh-v0.2.1-alpha.4`, commit `86a402200d95fecef4529d969836f1fe13c6cb0d`; historical alpha.16 source/npm qualification only.
242
251
  - Official tag `dsh-v0.2.1-alpha.5`, commit `1517a4dbca0a2789ff1d41ba439600f8547d23fa`; exact source/npm qualification is separate from unverified candidate Desktop artifacts/signatures.
252
+ - 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.
243
253
 
244
- The release admission, development dependency and CI targets are exact official `0.2.1-alpha.5`; the other twelve 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-alpha.2`, schemastery `3.18.5-alpha.2` 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. Historical signed Desktop evidence is not alpha.5 package/signature acceptance. Neither source nor synthetic tests prove live endpoints, plugin activation, publication or loaded runtime state. See [the official-first review](./docs/official-first-021-alpha5.md); this update does not authorize Core implementation rewrites or experimental durable records.
254
+ 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.
245
255
 
246
256
  These pins document compatibility evidence. They do not authorize creating another controlled Core patch or making one a prerequisite for new plugin fixes.
247
257
 
@@ -321,7 +331,7 @@ Then run `pnpm verify:tarball -- artifacts/dsh-github-copilot-<package-version>.
321
331
 
322
332
  If the exact frozen install is blocked solely by an enterprise registry or network policy while the repository's GitHub Actions can obtain the unchanged pinned packages from an authorized official registry, record the attempted command and exact environmental failure as **local validation blocked**, not passed. A PR may proceed with that limitation disclosed; the complete required GitHub CI matrix, including its install, tests, build and package checks, is then the authoritative gate 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.
323
333
 
324
- The release CI matrix targets only exact official `0.2.1-alpha.5` 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.
334
+ 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.
325
335
 
326
336
  ### Evidence and side effects
327
337
 
@@ -379,19 +389,19 @@ Completed-turn Usage diagnostics (#259) are read-only plugin conversation data a
379
389
  Auto task routing (#258) uses current `model_picker_category` facts, never model
380
390
  names, effort or context capacity as a quality category. Hard eligibility/input
381
391
  fit precede task/preference policy; unknown category and uncertain task evidence
382
- remain explicit. High-cost-v4 retains every eligible fitting model across
383
- categories with positive weight. Task/preference sets the favored target, not
384
- hard category exclusion. Per-model category factors are target 1, second 0.25,
385
- third 0.05, unknown 0.02 in the existing order, then multiplied by cost/recency.
386
- These are uncalibrated trial factors, not fixed category probability quotas;
387
- candidate populations affect shares. Ordinary weight 1 receives finite
388
- previous-model multiplier 1.5; marked base 0.2 decays to 0.02 only for the previous
389
- model. One-turn recency resets after a different model, not a hidden streak
390
- counter or task-failure inference. Preserve v1/v2/v3 historical codecs/cohorts and
391
- their original explanation. Fit is not task
392
- success; non-target draws are intentional opportunity, not absence/failure of
393
- target candidates. Never infer incapability or add task-failure escalation.
394
- Capture actual reasons once
392
+ remain explicit. High-cost-v4 retains every eligible fitting model across
393
+ categories with positive weight. Task/preference sets the favored target, not
394
+ hard category exclusion. Per-model category factors are target 1, second 0.25,
395
+ third 0.05, unknown 0.02 in the existing order, then multiplied by cost/recency.
396
+ These are uncalibrated trial factors, not fixed category probability quotas;
397
+ candidate populations affect shares. Ordinary weight 1 receives finite
398
+ previous-model multiplier 1.5; marked base 0.2 decays to 0.02 only for the previous
399
+ model. One-turn recency resets after a different model, not a hidden streak
400
+ counter or task-failure inference. Preserve v1/v2/v3 historical codecs/cohorts and
401
+ their original explanation. Fit is not task
402
+ success; non-target draws are intentional opportunity, not absence/failure of
403
+ target candidates. Never infer incapability or add task-failure escalation.
404
+ Capture actual reasons once
395
405
  per turn without durable decision events or changing Usage.
396
406
  `autoSemanticAssessment` is default-on by explicit user rollout request (#267),
397
407
  only for locally unknown demand; preserve explicit false opt-out. One bounded concrete
package/CHANGELOG.md CHANGED
@@ -1,5 +1,21 @@
1
1
  # Changelog
2
2
 
3
+ ## 0.1.0-alpha.2.dsh.0.2.1.rc.3 (prepared)
4
+
5
+ - 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.
6
+ - 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.
7
+ - 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.
8
+ - 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.
9
+
10
+ ## 0.1.0-alpha.1.dsh.0.2.1.rc.3 (prepared)
11
+
12
+ - 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.
13
+ - Adapt the plugin-owned search runtime to the public rc.3 `WebRuntime` Volatile-provider contract. Preserve native provider, account, transport, retry and configuration ownership.
14
+ - 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.
15
+ - 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.
16
+ - 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.
17
+ - 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.
18
+
3
19
  ## 0.1.0-alpha.2.dsh.0.2.1.alpha.5 (prepared)
4
20
 
5
21
  - 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.
package/README.md CHANGED
@@ -8,14 +8,14 @@
8
8
 
9
9
  GitHub Copilot account discovery, contextual Auto routing and hosted search for DSH. The plugin reuses DSH's published native adapter, retaining a profile-wide account default with independent Session next-turn choices; it does not patch Core or maintain a second model catalog.
10
10
 
11
- **Historical stable release: [`0.4.1`](https://github.com/cloga/dsh-github-copilot/releases/tag/v0.4.1); pending DSH alpha.5 iteration: `0.1.0-alpha.2.dsh.0.2.1.alpha.5`.** Each exact DSH Core version starts an independent plugin sequence at `0.1.0-alpha.1.dsh.<Core>`; same-Core fixes increment `alpha.N`. The suffix normalizes Core `0.2.1-alpha.5` to `dsh.0.2.1.alpha.5`, but compatibility is validated against explicit metadata, not guessed from the name. This resets numbering, not code, history or qualification requirements. Existing versions/tags remain unchanged. Candidate Desktop artifacts/signatures are unverified; this is not a Desktop-upgrade recommendation. Published, installed and loaded states remain separate.
11
+ **Historical stable release: [`0.4.1`](https://github.com/cloga/dsh-github-copilot/releases/tag/v0.4.1); pending DSH rc.3 update: `0.1.0-alpha.2.dsh.0.2.1.rc.3`.** DSH `0.2.1-rc.3` is a prerelease. This plugin line is a compatibility candidate, not a production Core upgrade recommendation; Desktop artifacts/signatures are unverified. Each exact DSH Core version starts an independent plugin sequence at `0.1.0-alpha.1.dsh.<Core>`; same-Core fixes increment `alpha.N`. The suffix normalizes Core `0.2.1-rc.3` to `dsh.0.2.1.rc.3`, but compatibility is validated against explicit metadata, not guessed from the name. Existing published versions/tags remain unchanged. Published, installed and loaded states remain separate.
12
12
 
13
13
  Select by **exact Core**, never global SemVer maximum or npm `latest`/`alpha`.
14
14
  The read-only `node scripts/select-core-release.mjs 0.2.0-rc.2` command checks
15
15
  `deployment-baseline.json`'s mapping and verifies the exact public GitHub Release,
16
16
  tarball/checksum assets and npm version's `engines.dsh` before returning an
17
- install spec. Rc.2 maps to alpha.15, Core alpha.4 to alpha.16, and Core alpha.5
18
- to this candidate; until both channels are observable, it reports pending or
17
+ install spec. Rc.2 maps to alpha.15, Core alpha.4 to alpha.16, alpha.5 remains
18
+ its historical line, and rc.3 maps to this pending candidate; until both channels are observable, it reports pending or
19
19
  incomplete without an install recommendation. Unknown targets fail explicitly. The existing npm
20
20
  `alpha` channel remains global and is not compatibility-aware; `latest` remains
21
21
  the historical stable pointer. No automatic updater integration or old-Core
@@ -25,7 +25,7 @@ maintenance is promised. See [release selection](./docs/npm-distribution.md#exac
25
25
 
26
26
  **Compaction planning:** alpha.15 fixes byte counts being compared with token budgets in the separately selected recovery engine. Planning now uses the public native token meter, preserving complete tool relations and final native admission. Truly oversized balanced units still fail explicitly; this is not history repair or guaranteed recovery. See [compaction recovery](./docs/manual-compaction-recovery.md).
27
27
 
28
- **DSH alpha.5 adaptation:** exact public APIs use pi-ai `1.1.0`, the official
28
+ **Historical DSH alpha.5 adaptation:** exact public APIs used pi-ai `1.1.0`, the official
29
29
  Cordis/schemastery peers and storage-domain's Zod `4.4.3`. The
30
30
  [fixed-target official-first review](https://github.com/cloga/dsh-github-copilot/blob/main/docs/official-first-021-alpha5.md)
31
31
  records every retain/migrate/retire/defer decision. Alpha.4 natively hides blank
@@ -36,6 +36,11 @@ selector regressions gate admission. No Core patch, version exemption, new
36
36
  wire/catalog, policy migration or durable decision recording is introduced.
37
37
 
38
38
 
39
+ The rc.3 candidate additionally adapts the public `WebRuntime` Volatile provider
40
+ getters and requires exact reviewer package/version/callback identity. Its
41
+ tagged-source and published-artifact gates passed on Windows/Linux in
42
+ [CI 40098031196](https://github.com/cloga/dsh-github-copilot/actions/runs/40098031196),
43
+ including full verification and package checks; no rc.3 Desktop runtime is claimed.
39
44
  Alpha.5 qualification also preserves code-first PTC schemas and function-body/REPL instructions. The new inline model-label slot is an opportunity only: no label UI or historical model attribution is added. Alpha.4 hosts may retain alpha.16.
40
45
 
41
46
  ## What you can do
@@ -155,10 +160,10 @@ Supply any launcher patches with repeated `--patch /absolute/file`. Require `sup
155
160
  For a **standalone named profile**:
156
161
 
157
162
  ```sh
158
- dsh plugin --profile web add https://github.com/cloga/dsh-github-copilot/releases/download/v0.1.0-alpha.2.dsh.0.2.1.alpha.5/dsh-github-copilot-0.1.0-alpha.2.dsh.0.2.1.alpha.5.tgz
163
+ dsh plugin --profile web add https://github.com/cloga/dsh-github-copilot/releases/download/v0.1.0-alpha.2.dsh.0.2.1.rc.3/dsh-github-copilot-0.1.0-alpha.2.dsh.0.2.1.rc.3.tgz
159
164
  ```
160
165
 
161
- The command above is a prepared-release example, usable only after publication, and requires official DSH `0.2.1-alpha.5`. **Desktop rc.2 must not install alpha.16 or `0.1.0-alpha.2.dsh.0.2.1.alpha.5`**; retain `dsh-github-copilot@0.4.2-alpha.15` there. Candidate Desktop package/signature and profile peer composition remain unverified. The [historical rc.2 bundled-CLI qualification](./docs/npm-distribution.md#desktop-bundled-cli-on-official-rc2) is not alpha.5 acceptance; a generic/global `dsh` shim is not equivalent. No install, restart, registry-policy bypass, peer patch or configuration deletion is authorized by this release.
166
+ The command above is a prepared-release example, usable only after publication and required CI qualification; it requires official DSH prerelease `0.2.1-rc.3`. **Do not install this candidate into production Desktop profiles.** Desktop artifacts/signatures and profile peer composition remain unverified; retain the existing compatible plugin on rc.2. The [historical rc.2 bundled-CLI qualification](./docs/npm-distribution.md#desktop-bundled-cli-on-official-rc2) does not qualify rc.3, and a generic/global `dsh` shim is not equivalent. No installation or restart is authorized.
162
167
 
163
168
  Desktop's native package manager and qualified bundled CLI are profile-specific.
164
169
  [Standalone offline maintenance](./docs/npm-distribution.md#controlled-offline-cli-maintenance-for-standalone-profiles)
@@ -180,7 +185,9 @@ Completed managed turns show **Account** beside native Usage. It records the req
180
185
 
181
186
  Saved account names can load without activating the account. Names are cached for the Host lifetime, invalidated by credential changes or failed verification, and never prove authorization or model access. A global switch requires fresh identity/model validation and confirmed settings persistence. If switching is blocked, let authorization or pinned work settle and use **Refresh account information**; unknown route/activity evidence remains a blocker. The dropdown, not a button beside each saved account, is the selection control.
182
187
 
183
- **Desktop lifecycle:** disable/remove/upgrade can require a full cold restart for Web service recomposition. If the plugin is Off and the native manager reports only `pending (waiting for service: web)`, do not repeatedly toggle or reinstall. Obtain restart approval and follow [rc.2 lifecycle guidance](./docs/web-lifecycle-rc2.md).
188
+ Account-management metadata and identity reads have a fifteen-second Client deadline instead of indefinite Checking. An initial read failure offers metadata-only **Retry**; late results are ignored. This does not cancel Host work, retry automatically or unlock an unresolved account mutation.
189
+
190
+ **Desktop lifecycle:** the current rc.3 public-Loader fixture preserves active Web consumers on a single-step add, but staged add and remove/re-add can leave the global `web` service unavailable and dependent account integration inactive. No feature-equivalent plugin-only recovery API is currently available; [issue #371](https://github.com/cloga/dsh-github-copilot/issues/371) remains open. An in-place upgrade without native HMR is explicitly `restart-required`; honor that manager result. The synthetic fixture does not justify repeated toggles or a restart when the manager has not requested one. See the [rc.3 lifecycle evidence](./docs/web-lifecycle-rc2.md).
184
191
 
185
192
  ## Auto and model preferences
186
193
 
@@ -261,7 +268,7 @@ Compaction feedback separates **compaction completed** and **subsequent request
261
268
 
262
269
  Running visible-history compaction notices stay visible. Confirmed success disappears eight seconds after first observation; settled failures, cancellation, unavailable status and enable prompts stay until **Close** (or the existing **Cancel**). Closing only hides this Session/operation/status notice, never changes consent, history or native proof, and never sends or retries. A bounded Client registration retains expiry/dismissal across incidental remounts and Session switches, not across teardown or eviction.
263
270
 
264
- For exact verified `408 / user_request_timeout`, diagnostics describe bounded request composition and observable timing, not a proven payload limit or root cause. Image counts include native Responses tool outputs; older stored diagnostics may have counted those images as residual history. Bytes are not tokens; timing is not upload duration. Small, image-free requests can also time out. Follow [request-budget and timeout guidance](./docs/copilot-compaction.md); do not automatically trim history, disable proof, switch models or add retries.
271
+ For exact verified `408 / user_request_timeout`, diagnostics describe bounded request composition and observable timing, not a proven payload limit or root cause. They include the validated model/protocol, UTC response-header observation time and strictly recognized supplier request IDs when available, without other headers or new stored diagnostics. IDs are correlation only, not receipt/execution proof. Image counts include native Responses tool outputs; older stored diagnostics may have counted those images as residual history. Only positive recognized image bytes suggest explicit image offload; zero/unknown image evidence does not. Bytes are not tokens; timing is not upload duration. Small, image-free requests can also time out. Follow [request-budget and timeout guidance](./docs/copilot-compaction.md); do not automatically trim history, disable proof, switch models or add retries.
265
272
 
266
273
  The experimental `github-copilot.responsesRequestCompression` option is **off by default**. When explicitly enabled, it losslessly gzips only eligible managed HTTP Responses requests through the existing native Fetch seam. It starts at 256 KiB, skips compression work above 32 MiB and requires at least 5% and 4 KiB savings; every skip sends the original request. This changes prepared HTTP body bytes, not context/token admission. Custom Fetch, explicit `auto`/WebSocket and other protocols remain native, and a gzip rejection is never automatically resent uncompressed. On a verified 408, diagnostics distinguish original JSON composition from the prepared gzip body size; neither proves delivery or cures every timeout. Installation does not enable the option.
267
274
 
@@ -316,6 +323,10 @@ The name “New Session” describes default inheritance, not a one-message feat
316
323
 
317
324
  Context evidence and Replay recovery use compact, centered notices bounded by the native composer width. Model/item counts and status refresh live in collapsed technical details; loss consent remains explicit. Context sampling warns only for a concrete incident, can be dismissed for that Session/incident, and never asserts the native meter's current value; native statistics stay unchanged. Switching accounts does not make old encrypted reasoning portable. The concise scope error points to explicit recovery or a new conversation; bounded, sanitized dispatch counts stay in Host diagnostics, not the main error. **Authorized** means permission is ready, not that a message was sent or recovery succeeded.
318
325
 
326
+ Notice frames also follow native horizontal clearance on narrow and embedded layouts; nested details do not apply the width limit twice. Recovery uses one primary **Enable** action and a quiet **Cancel**, without changing consent or initiating a retry.
327
+
328
+ For a failed scheduled/background task, open its original Session to review **Replay recovery**. The latest recorded exact scope rejection keeps this entry available after temporary request diagnostics expire, Host restart or a picker change. Unavailable item/account diagnostics stay unknown; copied fork history does not create an entry. Enablement still requires the loss-disclosed Session policy choice and never resends the task. Check its possible side effects before choosing native Retry; a later native turn clears the old failure notice.
329
+
319
330
  ## Ownership and further reading
320
331
 
321
332
  DSH Core owns Sessions, tools, sandboxing, attachments, native accounting and other providers. `llm-pi-ai` owns OAuth, token exchange/refresh and normal model transport. This plugin composes the published adapter with authenticated account metadata; new supported account model IDs need no name-based routing patch. Credentials stay Host-only: `llm-pi-ai/github-copilot` is the canonical compatibility record; additional accounts are independently authorized plugin-owned records in the same DSH credentials service, never copied grants.
@@ -325,7 +336,8 @@ Public APIs cannot replace Core Edit/Delete, restructure its flat picker or make
325
336
  | Guide | Scope |
326
337
  |---|---|
327
338
  | [Compatibility acceptance](./docs/model-compatibility-acceptance.md) | Metadata, reasoning, replay and public-interface limits |
328
- | [Current official-first review](./docs/official-first-020-rc2.md) | Exact rc.2 seams and retained gaps |
339
+ | [Current compatibility review](./docs/official-first-021-rc3.md) | Exact rc.3 WebRuntime contract, reviewer identity and source/artifact qualification |
340
+ | [Historical rc.2 official-first review](./docs/official-first-020-rc2.md) | Earlier rc.2 seams and retained gaps |
329
341
  | [Migration](./docs/single-route-migration.md) | Fresh read-only readiness and explicit config-only maintenance |
330
342
  | [Distribution](./docs/npm-distribution.md) | Same-byte GitHub/npm publication and qualified installation |
331
343
  | [Agent guide](./AGENTS.md), [contributing](./CONTRIBUTING.md) | Owners, task plans, gates and delivery policy |
@@ -343,7 +355,7 @@ pnpm pack --pack-destination artifacts
343
355
  pnpm verify:tarball -- artifacts/dsh-github-copilot-<package-version>.tgz
344
356
  ```
345
357
 
346
- `pnpm verify` covers contracts, types, baseline, build, tests and built entry smoke. Required CI targets unchanged official rc.2 source and published artifacts on Windows/Linux. Passing synthetic tests does not prove live account/model/search behavior.
358
+ `pnpm verify` covers contracts, types, baseline, build, tests and built entry smoke. Required CI passed against unchanged official rc.3 source and published artifacts on Windows/Linux; see the [qualification evidence](./docs/official-first-021-rc3.md). This unpublished candidate is not installed or Desktop-qualified. Passing synthetic tests does not prove live account/model/search behavior.
347
359
 
348
360
  Agents start with `node scripts/agent.mjs describe --json`, `doctor --json` and `plan <task> --json`; plans are unexecuted arguments, not action approval. Follow [AGENTS.md](./AGENTS.md) for the full change/release policy. Important updates require protected merge and verified dual-channel publication; documentation-only work does not release by default. Profile installation, sign-out and session-interrupting restart need separate authorization.
349
361
 
@@ -354,14 +366,14 @@ Commit attribution uses `Assisted-by` with the actual tool, never the model prov
354
366
  GitHub Releases and npm distribute the same original verified tarball. Pin a version; verify Release SHA-256 or npm `dist.integrity`. Never repack an immutable release or move/reuse its tag.
355
367
 
356
368
  ```sh
357
- curl -LO https://github.com/cloga/dsh-github-copilot/releases/download/v0.1.0-alpha.2.dsh.0.2.1.alpha.5/dsh-github-copilot-0.1.0-alpha.2.dsh.0.2.1.alpha.5.tgz
358
- curl -LO https://github.com/cloga/dsh-github-copilot/releases/download/v0.1.0-alpha.2.dsh.0.2.1.alpha.5/SHA256SUMS
369
+ curl -LO https://github.com/cloga/dsh-github-copilot/releases/download/v0.1.0-alpha.2.dsh.0.2.1.rc.3/dsh-github-copilot-0.1.0-alpha.2.dsh.0.2.1.rc.3.tgz
370
+ curl -LO https://github.com/cloga/dsh-github-copilot/releases/download/v0.1.0-alpha.2.dsh.0.2.1.rc.3/SHA256SUMS
359
371
  sha256sum --check SHA256SUMS
360
372
  ```
361
373
 
362
374
  ```powershell
363
375
  $expected = (Get-Content .\SHA256SUMS).Split()[0]
364
- $actual = (Get-FileHash .\dsh-github-copilot-0.1.0-alpha.2.dsh.0.2.1.alpha.5.tgz -Algorithm SHA256).Hash.ToLowerInvariant()
376
+ $actual = (Get-FileHash .\dsh-github-copilot-0.1.0-alpha.2.dsh.0.2.1.rc.3.tgz -Algorithm SHA256).Hash.ToLowerInvariant()
365
377
  if ($actual -cne $expected) { throw 'Release checksum mismatch' }
366
378
  ```
367
379
 
package/README.zh.md CHANGED
@@ -8,13 +8,13 @@
8
8
 
9
9
  为 DSH 提供 GitHub Copilot 账号模型发现、上下文 Auto 选模和 hosted search。插件复用 DSH 公开的原生适配器,保留 profile 全局默认账号,并支持 Session 后续 turn 指定独立账号;不修改 Core,也不维护第二套模型目录。
10
10
 
11
- **历史稳定版:[`0.4.1`](https://github.com/cloga/dsh-github-copilot/releases/tag/v0.4.1);DSH alpha.5 待发布迭代:`0.1.0-alpha.2.dsh.0.2.1.alpha.5`。** 每个精确 DSH Core 版本都从独立插件序列 `0.1.0-alpha.1.dsh.<Core>` 开始;同一 Core 内修复递增 `alpha.N`。后缀将 Core `0.2.1-alpha.5` 规范化为 `dsh.0.2.1.alpha.5`,但兼容性仍须核对明确元数据,不能只猜版本名。重置的是编号,不是代码、历史或资格验证要求;既有版本和 tag 不变。候选 Desktop 制品/签名未核验,这不是 Desktop 升级建议。已发布、已安装、已加载仍是不同状态。
11
+ **历史稳定版:[`0.4.1`](https://github.com/cloga/dsh-github-copilot/releases/tag/v0.4.1);DSH rc.3 更新候选:`0.1.0-alpha.2.dsh.0.2.1.rc.3`。** DSH `0.2.1-rc.3` 是预发布版本。本插件线是兼容性候选,不是生产 Core 升级建议;Desktop 制品/签名尚未核验。每个精确 DSH Core 版本都从独立插件序列 `0.1.0-alpha.1.dsh.<Core>` 开始;同一 Core 内修复递增 `alpha.N`。后缀将 Core `0.2.1-rc.3` 规范化为 `dsh.0.2.1.rc.3`,但兼容性仍须核对明确元数据,不能只猜版本名。既有已发布版本和 tag 不变。已发布、已安装、已加载仍是不同状态。
12
12
 
13
13
  按**精确 Core**选版本,不按全局 SemVer 最大值或 npm `latest`/`alpha`。
14
14
  只读命令 `node scripts/select-core-release.mjs 0.2.0-rc.2` 先读取
15
15
  `deployment-baseline.json` 映射,再核验精确 GitHub Release、原始 tarball/校验和资产,
16
16
  以及 npm 版本中的 `engines.dsh`,全部匹配后才返回安装规格。rc.2 对应 alpha.15,
17
- Core alpha.4 对应 alpha.16,Core alpha.5 对应本次候选;任一渠道尚不可见时,
17
+ Core alpha.4 对应 alpha.16,alpha.5 保留其历史线,rc.3 对应当前待验证候选;任一渠道尚不可见时,
18
18
  会报告待发布或未完成,不给安装建议。未知目标明确失败。沿用的 npm `alpha` 渠道是全局指针,
19
19
  不感知兼容性;`latest` 仍指历史稳定版。不承诺原生自动更新会使用此映射,
20
20
  也不承诺维护旧 Core 分支。参见[版本选择](./docs/npm-distribution.md#exact-core-release-lines)。
@@ -23,7 +23,7 @@ Core alpha.4 对应 alpha.16,Core alpha.5 对应本次候选;任一渠道尚
23
23
 
24
24
  **压缩规划:**alpha.15 修复独立选择的恢复引擎将字节数与 token 预算直接比较的问题,改用公开的原生 token meter,保留完整工具关系和最终原生准入。真正超大的配对历史单元仍明确失败;这不是历史修复,也不保证恢复成功。参见[压缩恢复](./docs/manual-compaction-recovery.md)。
25
25
 
26
- **DSH alpha.5 适配:**公开 API 对齐 pi-ai `1.1.0`、官方 Cordis/schemastery peer,
26
+ **历史 DSH alpha.5 适配:**公开 API 对齐 pi-ai `1.1.0`、官方 Cordis/schemastery peer,
27
27
  以及 storage-domain 的 Zod `4.4.3`。
28
28
  [固定目标的 official-first 调研](https://github.com/cloga/dsh-github-copilot/blob/main/docs/official-first-021-alpha5.md)
29
29
  逐项记录保留/迁移/退役/延期决定。alpha.4 原生隐藏空白 Thinking 折叠行,
@@ -32,6 +32,8 @@ Core alpha.4 对应 alpha.16,Core alpha.5 对应本次候选;任一渠道尚
32
32
  replay、账号/Remote/压缩与真实 selector 挂载回归共同约束准入。
33
33
  不修改 Core,不豁免版本,不新增 wire/目录、迁移策略或持久决策记录。
34
34
 
35
+ rc.3 候选还适配公开 `WebRuntime` Volatile provider getter,并要求精确 reviewer 包版本及回调身份。[CI 40098031196](https://github.com/cloga/dsh-github-copilot/actions/runs/40098031196) 已在 Windows/Linux 通过 tagged-source、published-artifact、完整验证和打包门禁;当前不声称 rc.3 Desktop runtime 已验证。
36
+
35
37
  alpha.5 资格验证同时保留代码优先的 PTC 参数顺序和函数体/REPL 指引。新增内联模型标签插槽仅作为后续机会记录:本次不新增标签 UI,也不据此推断历史模型执行。alpha.4 主机可保留 alpha.16。
36
38
 
37
39
  ## 你可以做什么
@@ -133,10 +135,10 @@ node package/scripts/check-search-composition.mjs --profile-dir /absolute/profil
133
135
  **独立具名 profile**:
134
136
 
135
137
  ```sh
136
- dsh plugin --profile web add https://github.com/cloga/dsh-github-copilot/releases/download/v0.1.0-alpha.2.dsh.0.2.1.alpha.5/dsh-github-copilot-0.1.0-alpha.2.dsh.0.2.1.alpha.5.tgz
138
+ dsh plugin --profile web add https://github.com/cloga/dsh-github-copilot/releases/download/v0.1.0-alpha.2.dsh.0.2.1.rc.3/dsh-github-copilot-0.1.0-alpha.2.dsh.0.2.1.rc.3.tgz
137
139
  ```
138
140
 
139
- 上面的命令是准备发布的示例,仅在发布后可用,并要求官方 DSH `0.2.1-alpha.5`。**Desktop rc.2 不得安装 alpha.16 或 `0.1.0-alpha.2.dsh.0.2.1.alpha.5`**,应保留 `dsh-github-copilot@0.4.2-alpha.15`。候选 Desktop 包/签名及 profile peer 组合仍未核验。[历史 rc.2 随附 CLI 核验](./docs/npm-distribution.md#desktop-bundled-cli-on-official-rc2)不代表 alpha.5 验收;全局/普通 `dsh` shim 不等价。此版本不授权安装、重启、绕过包源政策、修改 peer 或删除配置。
141
+ 上面的命令是准备发布的示例,仅在发布且所需 CI 通过后可用;目标是官方 DSH 预发布版 `0.2.1-rc.3`。**不要把此候选安装到生产 Desktop profile。** Desktop 制品/签名及 profile peer 组合仍未核验;rc.2 应保留现有兼容插件。[历史 rc.2 随附 CLI 核验](./docs/npm-distribution.md#desktop-bundled-cli-on-official-rc2)不代表 rc.3 验收;全局/普通 `dsh` shim 不等价。本次不授权安装或重启。
140
142
 
141
143
  Desktop 原生包管理器和已核验的随附 CLI 都有 profile 边界。
142
144
  [独立 profile 离线维护](./docs/npm-distribution.md#controlled-offline-cli-maintenance-for-standalone-profiles)
@@ -158,7 +160,9 @@ Desktop 原生包管理器和已核验的随附 CLI 都有 profile 边界。
158
160
 
159
161
  读取已保存账号名称不必激活账号。名称在 Host 生命周期内缓存,凭据变更或验证失败会失效,也不证明授权或模型可用。全局切换需要新鲜身份/模型验证及设置持久化确认。切换被阻止时,等待授权或锁定工作结束,再**刷新账号信息**;未知路由/活动证据仍是阻塞。选择入口是下拉菜单,不是每个已保存账号旁的按钮。
160
162
 
161
- **Desktop 生命周期:**停用、移除、升级后的 Web 服务重组可能需要完整冷重启。若插件已 Off,而原生 manager 仅提示 `pending (waiting for service: web)`,不要反复切换或重装。先取得重启许可,遵循[rc.2 生命周期说明](./docs/web-lifecycle-rc2.md)。
163
+ 账号管理的元数据和身份读取使用 15 秒 Client 展示期限,避免无限 Checking。首次读取失败提供只读元数据**重试**;迟到结果不会覆盖新状态。不取消 Host 工作、不自动重试,也不会解锁尚未完成的账号修改操作。
164
+
165
+ **Desktop 生命周期:**当前 rc.3 公共 Loader 测试中,单步添加可保留正在使用的 Web 消费者;但分阶段添加或移除后重新添加,可能导致全局 `web` 服务不可用及依赖它的账号集成无法启动。目前没有功能等价的插件侧恢复 API;[#371](https://github.com/cloga/dsh-github-copilot/issues/371) 仍保持开放。没有原生 HMR 时,原生管理器会明确返回 `restart-required`;应遵循该结果。合成测试本身不构成反复切换或重启的依据。参见 [rc.3 生命周期证据](./docs/web-lifecycle-rc2.md)。
162
166
 
163
167
  ## Auto 与模型偏好
164
168
 
@@ -236,7 +240,7 @@ Copilot 搜索要求当前账号/协议证据及能力 proof。固定/fallba
236
240
 
237
241
  可见历史压缩进行中时提示持续可见。确认成功后从首次观察起八秒自动消失;失败、取消、状态不可用和开启提示保留至手动**关闭**(或原有**取消**)。关闭仅隐藏当前 Session/操作/状态的提示,不改变授权、历史或原生证据,不发送或重试。Client 注册范围内的有界状态使临时重挂载和会话切换不会重置期限;注册销毁或记录淘汰后不保留。
238
242
 
239
- 严格核验的 `408 / user_request_timeout`诊断给出有界请求构成和可观察耗时,不证明供应方 payload 上限或根因。图片统计包括原生 Responses 工具输出中的图片;旧的已存诊断可能把这些图片算作剩余历史。字节不是 tokens,耗时不是上传时长;小型无图请求也可能超时。参见[预算与超时指导](./docs/copilot-compaction.md),不要自动裁剪历史、禁用 proof、切换模型或增加重试。
243
+ 严格核验的 `408 / user_request_timeout`诊断给出有界请求构成和可观察耗时,不证明供应方 payload 上限或根因。还包含经过校验的模型/协议、收到响应头时的 UTC 时间及格式严格受限的供应方请求 ID;不添加其他头信息或新的持久诊断。ID 仅用于关联,不证明接收或执行。图片统计包括原生 Responses 工具输出中的图片;旧的已存诊断可能把这些图片算作剩余历史。只有明确测得图片字节时才提示显式图片 offload;图片为零或未知时不建议缩减图片预算。字节不是 tokens,耗时不是上传时长;小型无图请求也可能超时。参见[预算与超时指导](./docs/copilot-compaction.md),不要自动裁剪历史、禁用 proof、切换模型或增加重试。
240
244
 
241
245
  实验性配置 `github-copilot.responsesRequestCompression` **默认关闭**。显式开启后,仅通过现有原生 Fetch 接口对符合条件的托管 HTTP Responses 请求进行无损 gzip 编码。请求至少 256 KiB;超过 32 MiB 的压缩工作会跳过,且必须同时节省至少 5% 和 4 KiB;任何跳过都会发送原始请求。这只改变准备发送的 HTTP body 字节,不改变 context/token 准入。自定义 Fetch、显式 `auto`/WebSocket 和其他协议维持原生行为;gzip 被拒绝后绝不会自动改成未压缩请求重发。严格核验的 408 诊断会区分原始 JSON 组成字节与准备发送的 gzip body 大小;两者均不证明请求已送达,也不保证消除超时。安装不会启用此选项。
242
246
 
@@ -291,6 +295,10 @@ Credits 账号面板显示当前账号和 **切换**,下拉菜单只列已有
291
295
 
292
296
  上下文证据与回放恢复以紧凑、居中提示显示在输入框上方,宽度遵循原生输入框。模型、项数和状态刷新收进默认折叠的技术详情;有损恢复仍需明确确认。上下文采样只在明确事件时告警,可按 Session/事件关闭,且不会断言原生仪表当前值;原生统计不变。切换账号不会让旧加密推理自动变得可跨账号使用。简短 scope 错误指向显式恢复或新会话;有界、脱敏的请求结构计数留在 Host 诊断中,不挤占主错误。**已授权**只表示授权已准备好,不表示消息已发送或恢复已成功。
293
297
 
298
+ 窄屏和嵌入式布局也遵循原生输入框的横向留白,嵌套详情不会重复限宽。恢复操作突出一个**开启**主按钮,**取消**保持弱化;不改变损失确认或自动发起重试。
299
+
300
+ 定时/后台任务失败后,打开任务原来的 Session 查看**回放恢复**。最近一次已记录的精确 scope 拒绝,在临时请求诊断过期、Host 重启或更换模型选择后仍保留入口。不可用的项数/账号诊断保持未知;复制的 fork 历史不会创建入口。开启仍须用户确认有损 Session 策略,不会重发任务。自行选择原生重试前,请先检查失败任务可能已产生的副作用;后续原生轮次开始时清除旧失败提示。
301
+
294
302
  ## 所有权与深入阅读
295
303
 
296
304
  DSH Core 所有会话、工具、sandbox、附件、原生计量和其它 provider;`llm-pi-ai`所有 OAuth、token 交换/刷新和普通模型传输。插件以认证后的账号元数据组合公开适配器,受支持的新模型 ID 无需名称路由补丁。凭据仅在 Host:`llm-pi-ai/github-copilot` 是 canonical 兼容记录;额外账号在同一 DSH 凭据服务的插件所有记录中独立授权,不复制 grant。
@@ -300,7 +308,8 @@ DSH Core 所有会话、工具、sandbox、附件、原生计量和其它 provid
300
308
  | 指南 | 范围 |
301
309
  |---|---|
302
310
  | [兼容验收](./docs/model-compatibility-acceptance.md) | 元数据、reasoning、replay 及公开接口限制 |
303
- | [当前 official-first](./docs/official-first-020-rc2.md) | 准确 rc.2 seam 与保留差距 |
311
+ | [当前兼容性评估](./docs/official-first-021-rc3.md) | 精确 rc.3 WebRuntime 契约、reviewer 身份和源码/制品资格证据 |
312
+ | [历史 rc.2 official-first](./docs/official-first-020-rc2.md) | 旧 rc.2 seam 与保留差距 |
304
313
  | [迁移](./docs/single-route-migration.md) | 新鲜只读就绪证据及显式 config-only 维护 |
305
314
  | [分发](./docs/npm-distribution.md) | 同字节 GitHub/npm 发布和合格安装入口 |
306
315
  | [Agent 指南](./AGENTS.md)、[贡献](./CONTRIBUTING.md) | owner、任务计划、gate 与交付政策 |
@@ -318,7 +327,7 @@ pnpm pack --pack-destination artifacts
318
327
  pnpm verify:tarball -- artifacts/dsh-github-copilot-<package-version>.tgz
319
328
  ```
320
329
 
321
- `pnpm verify`覆盖合同、类型、baseline、build、测试和构建入口 smoke。必需 CI 在 Windows/Linux 使用未修改的官方 rc.2 源码与发布制品。模拟测试通过不证明真实账号/模型/搜索可用。
330
+ `pnpm verify`覆盖合同、类型、baseline、build、测试和构建入口 smoke。必需 CI 已在 Windows/Linux 使用未修改的官方 rc.3 源码与发布制品通过,见[资格证据](./docs/official-first-021-rc3.md)。此候选尚未发布、安装或通过 Desktop 验收。模拟测试通过不证明真实账号/模型/搜索可用。
322
331
 
323
332
  Agent 从 `node scripts/agent.mjs describe --json`、`doctor --json`及`plan <task> --json`开始;计划仅返回未执行 argv,不授权副作用。完整变更/发布政策见[AGENTS.md](./AGENTS.md)。重要更新必须经受保护合并与双渠道发布;纯文档默认不发包。Profile 安装、退出和中断会话的重启另需许可。
324
333
 
@@ -329,14 +338,14 @@ Agent 从 `node scripts/agent.mjs describe --json`、`doctor --json`及`plan <ta
329
338
  GitHub Releases 和 npm 分发同一原始已校验 tarball。固定版本并核验 Release SHA-256 或 npm `dist.integrity`;不重打包不可变 Release、不移动/复用 tag。
330
339
 
331
340
  ```sh
332
- curl -LO https://github.com/cloga/dsh-github-copilot/releases/download/v0.1.0-alpha.2.dsh.0.2.1.alpha.5/dsh-github-copilot-0.1.0-alpha.2.dsh.0.2.1.alpha.5.tgz
333
- curl -LO https://github.com/cloga/dsh-github-copilot/releases/download/v0.1.0-alpha.2.dsh.0.2.1.alpha.5/SHA256SUMS
341
+ curl -LO https://github.com/cloga/dsh-github-copilot/releases/download/v0.1.0-alpha.2.dsh.0.2.1.rc.3/dsh-github-copilot-0.1.0-alpha.2.dsh.0.2.1.rc.3.tgz
342
+ curl -LO https://github.com/cloga/dsh-github-copilot/releases/download/v0.1.0-alpha.2.dsh.0.2.1.rc.3/SHA256SUMS
334
343
  sha256sum --check SHA256SUMS
335
344
  ```
336
345
 
337
346
  ```powershell
338
347
  $expected = (Get-Content .\SHA256SUMS).Split()[0]
339
- $actual = (Get-FileHash .\dsh-github-copilot-0.1.0-alpha.2.dsh.0.2.1.alpha.5.tgz -Algorithm SHA256).Hash.ToLowerInvariant()
348
+ $actual = (Get-FileHash .\dsh-github-copilot-0.1.0-alpha.2.dsh.0.2.1.rc.3.tgz -Algorithm SHA256).Hash.ToLowerInvariant()
340
349
  if ($actual -cne $expected) { throw 'Release checksum mismatch' }
341
350
  ```
342
351
 
@@ -8,12 +8,13 @@
8
8
  },
9
9
  "package": {
10
10
  "name": "dsh-github-copilot",
11
- "version": "0.1.0-alpha.2.dsh.0.2.1.alpha.5"
11
+ "version": "0.1.0-alpha.2.dsh.0.2.1.rc.3"
12
12
  },
13
13
  "releaseLines": [
14
14
  { "core": "0.2.0-rc.2", "version": "0.4.2-alpha.15", "status": "published" },
15
15
  { "core": "0.2.1-alpha.4", "version": "0.4.2-alpha.16", "status": "published" },
16
- { "core": "0.2.1-alpha.5", "version": "0.1.0-alpha.2.dsh.0.2.1.alpha.5", "status": "pending" }
16
+ { "core": "0.2.1-alpha.5", "version": "0.1.0-alpha.2.dsh.0.2.1.alpha.5", "status": "published" },
17
+ { "core": "0.2.1-rc.3", "version": "0.1.0-alpha.2.dsh.0.2.1.rc.3", "status": "pending" }
17
18
  ],
18
19
  "evidence": {
19
20
  "kind": "source-and-synthetic-test-inventory",
@@ -24,12 +25,12 @@
24
25
  "platforms": ["windows", "linux"],
25
26
  "node": ">=22.19.0",
26
27
  "dsh": {
27
- "release": "0.2.1-alpha.5",
28
- "tag": "dsh-v0.2.1-alpha.5",
29
- "commit": "1517a4dbca0a2789ff1d41ba439600f8547d23fa",
30
- "developmentRelease": "0.2.1-alpha.5",
31
- "admittedReleases": ["0.2.1-alpha.5"],
32
- "peerRange": "0.2.1-alpha.5",
28
+ "release": "0.2.1-rc.3",
29
+ "tag": "dsh-v0.2.1-rc.3",
30
+ "commit": "1f81c047fc48fa190a683e469daa699857e9afe8",
31
+ "developmentRelease": "0.2.1-rc.3",
32
+ "admittedReleases": ["0.2.1-rc.3"],
33
+ "peerRange": "0.2.1-rc.3",
33
34
  "baselines": [
34
35
  {
35
36
  "release": "0.1.1-rc.2",
@@ -281,6 +282,34 @@
281
282
  "managedProviderValidation": "synthetic-tagged-source-runtime",
282
283
  "resolvedProfileDiagnostics": "plugin-owned-empty-modelErrors",
283
284
  "runtimeTests": ["tests/preview-route.spec.ts", "tests/published-core.spec.ts", "tests/single-route.spec.ts", "tests/search-routing.spec.ts", "tests/routed-web.spec.ts", "tests/deepseek-search-fallback.spec.ts", "tests/tool-schema-compat.spec.ts", "tests/fixtures/alpha2-contracts-core.fixture.ts", "tests/fixtures/compaction-pressure-core.fixture.ts", "tests/remote-codec.spec.ts", "tests/dual-model-projection.spec.ts", "tests/fixtures/scoped-compaction-core.fixture.ts", "tests/fixtures/model-exclusions-core.fixture.ts", "tests/fixtures/turn-usage-core.fixture.ts", "tests/fixtures/copilot-accounts-persistence-core.fixture.ts", "tests/fixtures/copilot-accounts-host-core.fixture.ts", "tests/fixtures/copilot-accounts-gateway-core.fixture.ts", "tests/fixtures/copilot-accounts-request-core.fixture.ts", "tests/copilot-stream-liveness.spec.ts", "tests/copilot-stream-adapter.spec.ts", "tests/fixtures/auto-review-copilot-core.fixture.ts", "tests/fixtures/diagnostics-storage-core.fixture.ts", "tests/fixtures/diagnostics-gateway-core.fixture.ts", "tests/fixtures/session-context-core.fixture.ts", "tests/fixtures/remote-core.fixture.ts", "tests/fixtures/alpha4-contracts-core.fixture.ts", "tests/fixtures/copilot-usage-selector-core.fixture.ts"]
285
+ },
286
+ {
287
+ "release": "0.2.1-rc.3",
288
+ "tag": "dsh-v0.2.1-rc.3",
289
+ "commit": "1f81c047fc48fa190a683e469daa699857e9afe8",
290
+ "source": "https://github.com/deepseek-ai/deepseek-harness",
291
+ "desktopRelease": "not-verified",
292
+ "webRuntimeConfig": "volatile-provider-getters-required-config",
293
+ "desktopPackageSet": "not-materialized",
294
+ "webSearchRouter": "synthetic-fixed-readonly-volatile",
295
+ "reviewerIdentity": "exact-package-version-and-published-callback-identity",
296
+ "modelsUi": "provider-card",
297
+ "providerHeaders": "fetch-validated-discovery",
298
+ "strictModeCompat": "route-switch",
299
+ "fileContentHelper": "contentHasFile",
300
+ "agentCreation": "awaited-serial-agent-created",
301
+ "sessionHistory": "request-header-and-projections-no-new-sync-history",
302
+ "sessionFormatVersion": 4,
303
+ "strictRemoteCodecs": "create-factories-with-legacy-schema-bridge",
304
+ "roleChildDescriptorVersion": 3,
305
+ "roleChildCacheVersion": 2,
306
+ "roleChildHistory": "unknown-legacy-history-fail-closed",
307
+ "runtimeDependencies": "public-resolution-and-unload",
308
+ "clientSessionContext": "multiple-session-owner-isolation",
309
+ "evidenceScope": "unchanged-tagged-source-target",
310
+ "standaloneNpmArtifacts": "tested",
311
+ "managedProviderValidation": "synthetic-tagged-source-and-published-artifact-runtime",
312
+ "runtimeTests": ["tests/preview-route.spec.ts", "tests/published-core.spec.ts", "tests/single-route.spec.ts", "tests/search-routing.spec.ts", "tests/routed-web.spec.ts", "tests/deepseek-search-fallback.spec.ts", "tests/tool-schema-compat.spec.ts", "tests/fixtures/alpha2-contracts-core.fixture.ts", "tests/fixtures/compaction-pressure-core.fixture.ts", "tests/remote-codec.spec.ts", "tests/dual-model-projection.spec.ts", "tests/fixtures/scoped-compaction-core.fixture.ts", "tests/fixtures/model-exclusions-core.fixture.ts", "tests/fixtures/turn-usage-core.fixture.ts", "tests/fixtures/copilot-accounts-persistence-core.fixture.ts", "tests/fixtures/copilot-accounts-host-core.fixture.ts", "tests/fixtures/copilot-accounts-gateway-core.fixture.ts", "tests/fixtures/copilot-accounts-request-core.fixture.ts", "tests/copilot-stream-liveness.spec.ts", "tests/copilot-stream-adapter.spec.ts", "tests/fixtures/auto-review-copilot-core.fixture.ts", "tests/fixtures/diagnostics-storage-core.fixture.ts", "tests/fixtures/diagnostics-gateway-core.fixture.ts", "tests/fixtures/session-context-core.fixture.ts", "tests/fixtures/remote-core.fixture.ts", "tests/fixtures/alpha4-contracts-core.fixture.ts", "tests/fixtures/copilot-usage-selector-core.fixture.ts"]
284
313
  }
285
314
  ],
286
315
  "packages": [
@@ -312,8 +341,8 @@
312
341
  "zod": "4.4.3"
313
342
  },
314
343
  "sharedPeerDependencies": {
315
- "@deepseek-ai/dsh-authorization": "0.2.1-alpha.5",
316
- "@deepseek-ai/schemastery": "3.18.5-alpha.2"
344
+ "@deepseek-ai/dsh-authorization": "0.2.1-rc.3",
345
+ "@deepseek-ai/schemastery": "3.18.5"
317
346
  },
318
347
  "clientExternals": {
319
348
  "react": {
@@ -953,6 +982,7 @@
953
982
  {"file": "src/replay-recovery-remote.ts", "marker": "githubCopilotReplayRecovery.setEnabled"},
954
983
  {"file": "src/replay-recovery-remote.ts", "marker": "githubCopilotReplayRecovery.authorize"},
955
984
  {"file": "src/replay-recovery-ui.ts", "marker": "recovery: true"},
985
+ {"file": "src/replay-failure-evidence.ts", "marker": "export const replayFailureDefinition"},
956
986
  {"file": "src/session-continuation-ui.ts", "marker": "Enable visible-history continuation"}
957
987
  ],
958
988
  "tests": [
@@ -962,6 +992,10 @@
962
992
  {"file": "tests/replay-recovery.spec.ts", "name": "admits only the next matching native turn, including its steps and retries"},
963
993
  {"file": "tests/replay-recovery-ui.spec.ts", "name": "enables only persistent Session continuation after loss disclosure, without legacy authorization or sending"},
964
994
  {"file": "tests/replay-recovery-ui.spec.ts", "name": "is absent normally, reads on settled turns without polling and resets dismissal only for new evidence"},
995
+ {"file": "tests/replay-recovery-ui.spec.ts", "name": "offers explicit recovery for a cold-open scheduled failure without temporary fingerprints or a current managed selection"},
996
+ {"file": "tests/replay-failure-evidence.spec.ts", "name": "cold-folds only the latest exact terminal replay failure without retaining raw errors or request evidence"},
997
+ {"file": "tests/replay-failure-evidence.spec.ts", "name": "does not offer recovery for a copied fork or child failure and admits only the new owner tail"},
998
+ {"file": "tests/fixtures/session-context-core.fixture.ts", "name": "cold-folds an unattended terminal replay failure through the native registry without request fingerprints"},
965
999
  {"file": "tests/preview-route.spec.ts", "name": "offers exact failed replay only to its initiating session and recovers after explicit confirmation"},
966
1000
  {"file": "tests/fixtures/remote-core.fixture.ts", "name": "binds explicit replay recovery through native Client and %s Host gateways"}
967
1001
  ]
@@ -1362,12 +1396,12 @@
1362
1396
  "id": "dsh-supported-baselines-fail-loud-guard",
1363
1397
  "required": true,
1364
1398
  "sourceMarkers": [
1365
- {"file": "src/compatibility.ts", "marker": "peerRange: '0.2.1-alpha.5'"}
1399
+ {"file": "src/compatibility.ts", "marker": "peerRange: '0.2.1-rc.3'"}
1366
1400
  ],
1367
1401
  "tests": [
1368
1402
  {"file": "tests/compatibility.spec.ts", "name": "admits only the exact current official release"},
1369
1403
  {"file": "tests/compatibility.spec.ts", "name": "declares the current and retained exact contract targets without claiming live Desktop validation"},
1370
- {"file": "tests/compatibility.spec.ts", "name": "accepts the supported DSH service contract"},
1404
+ {"file": "tests/compatibility.spec.ts", "name": "accepts the public service contract without reading private WebRuntime config"},
1371
1405
  {"file": "tests/compatibility.spec.ts", "name": "fails before startup when a required API is absent"}
1372
1406
  ]
1373
1407
  },