dsh-github-copilot 0.4.0-alpha.128 → 0.4.0-alpha.130
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 +21 -2
- package/CHANGELOG.md +12 -0
- package/README.md +16 -13
- package/README.zh.md +13 -12
- package/deployment-baseline.json +5 -2
- package/docs/copilot-usage.md +4 -4
- package/docs/plugin-diagnostics.md +64 -0
- package/lib/client.js +97 -42
- package/lib/client.js.map +1 -1
- package/lib/diagnostics-analysis-io.js +78 -0
- package/lib/diagnostics-analysis.js +425 -0
- package/lib/diagnostics-types-FVf6zjob.js +182 -0
- package/lib/index.js +68 -38
- package/lib/manual-compaction-recovery.js +2 -1
- package/lib/request-budget-DLY_aRq0.js +87 -0
- package/lib/types/context-evidence-ui.d.ts +14 -1
- package/lib/types/context-evidence.d.ts +29 -1
- package/lib/types/diagnostics-analysis-io.d.ts +23 -0
- package/lib/types/diagnostics-analysis.d.ts +295 -0
- package/package.json +3 -1
- package/scripts/analyze-diagnostics.mjs +91 -0
- package/lib/request-budget-Cui2hCi1.js +0 -268
package/AGENTS.md
CHANGED
|
@@ -43,7 +43,15 @@ This repository owns twelve narrow surfaces:
|
|
|
43
43
|
8. Optional, provider-scoped Chat presentation for completed empty reasoning disclosures; durable content and encrypted replay metadata remain Core-owned.
|
|
44
44
|
9. Compatibility-only policy restoration and request recovery for existing dedicated planner/executor Sessions. Model roles UI, settings writes and new dedicated roots are retired (#158); never reintroduce them or migrate histories implicitly.
|
|
45
45
|
10. Managed-route estimated input/output admission, optional exact-request pressure signalling through official compaction recovery, supported low summary effort only when no effort is already resolved, and default-off lossless gzip for explicitly opted-in account-proven HTTP Responses requests. See [compaction budgets](./docs/copilot-compaction.md). Preserve truthful capacities, requested output caps, native errors/replay and transaction ownership; no hidden history trimming, wire chunking, competing compaction service or automatic model switch. The separately selected, single-service [recovery engine](./docs/manual-compaction-recovery.md) defaults to automatic segmented recovery for known oversized summaries or one typed native capacity failure through the public subclass hook. Preserve `automaticRecovery: false`, native `auto: false`, scopes and custom engines; at most 16 physical calls including a failed first attempt, no recursive retry or 408/network/auth/quota fallback. Installation alone never selects or migrates an engine.
|
|
46
|
-
11. Optional account quota reads and a session-scoped composer usage control
|
|
46
|
+
11. Optional account quota reads and a session-scoped composer usage control
|
|
47
|
+
through public credentials, strict Remotes and additive slots. Keep account
|
|
48
|
+
billing-cycle credits separate from context tokens and session cost. Missing,
|
|
49
|
+
pooled, legacy and stale data must retain their real semantics; never infer credits
|
|
50
|
+
from token estimates or account deltas. A separate plugin-owned historical context
|
|
51
|
+
projection may diagnose concrete failed-zero or invalid-sample incidents; ordinary
|
|
52
|
+
request progress and absent fresh sampling stay quiet. Never filter shared native
|
|
53
|
+
usage, replace Core's meter, infer current occupancy/percentages or rewrite history.
|
|
54
|
+
See [quota boundaries](./docs/copilot-usage.md).
|
|
47
55
|
12. Default-off local account/Checking/compaction diagnostics through public storage-domain and strict additive Remotes. Keep fixed-dimension Client/Host and logical/physical populations separate, with bounded handles/rows, 14-day retention, explicit loss/uncertainty and native commit evidence. Isolate the home-wide backend by public profile context, never account/Session identity; one writer per profile is required. No content, raw errors, identities/hashes, credential/history reads, ad-hoc files, Settings logs, upload, daily task or automatic repair. Enable/pause uses only the hidden volatile `diagnosticsEnabled` CAS leaf; clear is a separately confirmed epoch fence. Missing/corrupt storage remains unavailable, never healthy empty data. Publication does not enable collection. See [local diagnostics](./docs/plugin-diagnostics.md).
|
|
48
56
|
|
|
49
57
|
## Session-policy compaction replay consent (#349, #352)
|
|
@@ -97,7 +105,15 @@ Alpha.25 admits native `subagent/descriptor` v3, already v3 in the retained rc.1
|
|
|
97
105
|
- `src/reasoning-presentation.ts`: guarded native Chat delegation and historical Copilot provenance; filters temporary view props only, never messages, signatures, replay indexes or usage.
|
|
98
106
|
- `src/remote.ts`: Typert Remote contribution. Never add credential payloads here.
|
|
99
107
|
- `src/copilot-usage-host.ts`, `src/copilot-usage-remote.ts`, `src/copilot-usage-card.ts`, `src/copilot-usage-ui.ts`: bounded Host quota snapshots, an independent strict namespace and reversible composer presentation. No real account fetches in tests, private Client store/DOM injection, quota-specific credential owner or general model wire.
|
|
100
|
-
- `src/context-usage.ts`, `src/context-evidence.ts`,
|
|
108
|
+
- `src/context-usage.ts`, `src/context-evidence.ts`,
|
|
109
|
+
`src/context-evidence-ui.ts`: diagnostic-only failed-zero/invalid-sample
|
|
110
|
+
incidents and bounded numeric historical evidence through a plugin-owned public
|
|
111
|
+
projection and additive composer disclosure. Keep ordinary progress quiet;
|
|
112
|
+
dismissal is bounded Client presentation keyed by Session/incident, and a valid
|
|
113
|
+
applicable sample clears the incident. Never filter native usage chunks to
|
|
114
|
+
protect context readings: shared samples also feed Core's turn and cumulative
|
|
115
|
+
accounting. Historical counts never become current occupancy; Core pressure,
|
|
116
|
+
billing and durable events stay under Core ownership.
|
|
101
117
|
- `src/current-provider.ts`: selected DSH route plus installed pi-ai catalog facts.
|
|
102
118
|
- `src/temporary-models.ts`: exact, account-gated corrections with semantic protocol/capability retirement.
|
|
103
119
|
- `src/model-protocol.ts`: explicit Core capability detection and conservative legacy fallback.
|
|
@@ -301,6 +317,9 @@ above the composer, with shared native secondary typography. Do not restore long
|
|
|
301
317
|
notices to the nonwrapping statistics row or mutate its parent DOM. Scope errors
|
|
302
318
|
keep concise recovery guidance; bounded dispatch counts are separate Host diagnostics,
|
|
303
319
|
not proof of the rejected item, account-switch failure or recovery success.
|
|
320
|
+
Ordinary context-request progress stays quiet. Only concrete sequenced sampling
|
|
321
|
+
incidents may notify, with bounded Session/incident dismissal; missing or unknown
|
|
322
|
+
projection evidence remains a named diagnostic and never fabricated health.
|
|
304
323
|
|
|
305
324
|
Completed-turn Usage diagnostics (#259) are read-only plugin conversation data and an additive assistant-actions explanation. Official rc.2 hides its total if any attempt lacks complete accounting; the plugin's finish-only pre-dispatch pressure block can trigger this rule even after recovery. Never fabricate zero usage or replace it with successful-step partial totals. Identify local interception only from its exact recorded finish-only diagnostic, keep other missing samples and paged evidence uncertain, and suppress the explanation whenever native `tokenUsage` exists. Preserve native accounting, history, pressure and recovery; see `docs/copilot-usage.md`.
|
|
306
325
|
|
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,17 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 0.4.0-alpha.130 (prepared)
|
|
4
|
+
|
|
5
|
+
- Add explicit offline analysis for a caller-selected persisted diagnostics unit or reviewed aggregate view (#368). Bound reads, reject unsafe/changed inputs, and write strict reports only to a new explicitly selected local file.
|
|
6
|
+
- Keep version, Client/Host, operation, terminal outcome and duration populations distinct. Preserve overflow and collection gaps; do not infer failure rates, live pending state, root cause or improvement from unmatched or persisted-only evidence.
|
|
7
|
+
- Synthetic tests cover read safety and report semantics; the first descriptive report remains private local evidence. No live profile read, collection change, upload, schedule, install or restart is part of release validation.
|
|
8
|
+
|
|
9
|
+
## 0.4.0-alpha.129
|
|
10
|
+
|
|
11
|
+
- Keep ordinary post-compaction steps and requests without a fresh usage sample quiet instead of repeatedly showing context-sampling uncertainty (#367).
|
|
12
|
+
- Notify only for a concrete failed-zero or invalid-sample incident. Bind dismissal to the Session and incident across ordinary remounts/switches; a later applicable valid sample clears the incident and a newer incident can notify.
|
|
13
|
+
- Preserve the existing eight-second native-confirmed compaction result, historical-count labeling, unknown-evidence diagnostics, native usage/context meters and Core-owned compaction/accounting without replacement percentages, retries or live installation.
|
|
14
|
+
|
|
3
15
|
## 0.4.0-alpha.128
|
|
4
16
|
|
|
5
17
|
- Separate native compaction commit, subsequent ordinary-request outcome and applicable historical input sampling in one composer disclosure (#364).
|
package/README.md
CHANGED
|
@@ -27,7 +27,7 @@ Visible Models and Credits resolve missing names for saved accounts without acti
|
|
|
27
27
|
|
|
28
28
|
Adding an account now keeps the device-authorization link, selectable URL, one-time code, Copy code action and Cancel together while authorization is pending. After GitHub authorizes, identity and model verification are shown as a separate phase. Adding never changes the global default; use the existing explicit **Switch** action when ready. Technical diagnostics are secondary, and account/turn identity fallbacks never expose opaque account IDs or infer historical identity from today's settings.
|
|
29
29
|
|
|
30
|
-
**Package version: `0.4.0-alpha.
|
|
30
|
+
**Package version: `0.4.0-alpha.130` (prepared). Supported host: official DSH / Windows Desktop `0.2.0-rc.2`.** Earlier DSH pins are historical evidence, not supported installation targets. Publication, profile installation and the version loaded by a running Host are separate states. Verify the published Release and assets before using the versioned commands below; these instructions do not prove publication or installation.
|
|
31
31
|
|
|
32
32
|
## What you can do
|
|
33
33
|
|
|
@@ -52,10 +52,13 @@ The [local diagnostics pilot](./docs/plugin-diagnostics.md) records bounded
|
|
|
52
52
|
account/Checking and compaction aggregates, **default off**. After installing
|
|
53
53
|
and loading the published build, open the plugin detail settings page →
|
|
54
54
|
**Local diagnostics → Read status → Enable local collection**. This enables
|
|
55
|
-
local persistence, not uploads or
|
|
56
|
-
|
|
57
|
-
|
|
58
|
-
|
|
55
|
+
local persistence, not uploads or scheduled analysis. The package also has an
|
|
56
|
+
explicit offline analyzer for a caller-selected persisted unit or reviewed
|
|
57
|
+
aggregate view; it writes only to a new local report file and never scans,
|
|
58
|
+
uploads or changes collection. Pause preserves evidence; Clear requires
|
|
59
|
+
separate confirmation. Client/Host populations, uncovered paths and
|
|
60
|
+
reporting/storage gaps remain explicit. Descriptive counts are not reconstructed
|
|
61
|
+
history, failure rates or proof of an improvement.
|
|
59
62
|
|
|
60
63
|
| Task | Where to start |
|
|
61
64
|
|---|---|
|
|
@@ -93,10 +96,10 @@ Supply any launcher patches with repeated `--patch /absolute/file`. Require `sup
|
|
|
93
96
|
For a **standalone named profile**:
|
|
94
97
|
|
|
95
98
|
```sh
|
|
96
|
-
dsh plugin --profile web add https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.0-alpha.
|
|
99
|
+
dsh plugin --profile web add https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.0-alpha.130/dsh-github-copilot-0.4.0-alpha.130.tgz
|
|
97
100
|
```
|
|
98
101
|
|
|
99
|
-
For **Desktop**, its native package manager accepts `dsh-github-copilot@0.4.0-alpha.
|
|
102
|
+
For **Desktop**, its native package manager accepts `dsh-github-copilot@0.4.0-alpha.130` after publication. Official rc.2's **Desktop-bundled CLI** also supports reserved-profile plugin management; a global/generic `dsh` shim is not equivalent. Qualify the installed entry before use. See [Desktop CLI qualification](./docs/npm-distribution.md#desktop-bundled-cli-on-official-rc2) and the distinct [standalone offline procedure](./docs/npm-distribution.md#controlled-offline-cli-maintenance-for-standalone-profiles). Neither path authorizes registry-policy bypass, peer patches or configuration deletion.
|
|
100
103
|
|
|
101
104
|
After an approved reload/restart:
|
|
102
105
|
|
|
@@ -165,7 +168,7 @@ canonical inline path; it is not a third routed fallback. Fetch is unchanged.
|
|
|
165
168
|
|
|
166
169
|
**Credits** shows validated account billing-cycle data, not context tokens or Session cost. Stale, pooled and unavailable readings keep their real meanings. The quota request alone uses Node plus system CA roots with TLS verification enabled; it does not change trust for sign-in, models, search or Desktop globally.
|
|
167
170
|
|
|
168
|
-
Native context occupancy and Turn Usage remain Core-owned. The plugin forwards usage unchanged, including zero samples on failure/cancellation.
|
|
171
|
+
Native context occupancy and Turn Usage remain Core-owned. The plugin forwards usage unchanged, including zero samples on failure/cancellation. Ordinary in-progress requests and missing new samples stay quiet; only a concrete failed-zero or invalid-sample incident opens the separate, dismissible context warning. Any retained count is labeled historical evidence, never current occupancy or a replacement percentage. **Turn Usage incomplete** explains missing samples/lifecycle and recorded local blocks; it invents neither zero usage nor partial totals. Cancellation can retain usage, but does not guarantee a final supplier receipt. [Usage boundaries](./docs/copilot-usage.md).
|
|
169
172
|
|
|
170
173
|
Owned timeout/replay errors preserve native usage before terminal failure restoration, including nonzero samples. A failed zero can still make the native ring show `0%`; this is not proof of an empty request. Retry-entry times describe backoff, not the failed request's duration. These accounting fixes do not cure supplier HTTP 408 or change retry policy.
|
|
171
174
|
|
|
@@ -177,7 +180,7 @@ For continuing steps with a committed managed route and no pending model change,
|
|
|
177
180
|
|
|
178
181
|
**Visible-history continuation also covers this Session's native managed Responses compaction**, including automatic summaries: no extra manual recovery command or failure-first retry is required when enabled. Old encrypted reasoning and embedded summaries are omitted from outgoing input; hidden context may be lost. Visible messages/tool pairs and source history remain intact, and only the native transaction commits a smaller checkpoint. A composer notice identifies degradation and distinguishes committed, failed and cancelled outcomes. When off, an exact replay-scope rejection offers the same loss-disclosed enable control; unknown failures do not authorize loss. `/copilot-compact visible-history` remains a one-time alternative through the selected recovery engine. Read [recovery consent and limits](./docs/manual-compaction-recovery.md#explicit-visible-history-summary-recovery); this does not enable an absent engine or repair capacity, quota or timeout failures.
|
|
179
182
|
|
|
180
|
-
Compaction feedback separates **compaction completed
|
|
183
|
+
Compaction feedback separates **compaction completed** and **subsequent request succeeded** during the existing eight-second result window. It does not turn ordinary request progress or absence of a fresh sample into a persistent composer warning. A later concrete sampling incident can appear independently and may include a labeled historical count, but never an occupancy percentage. The plugin sends no extra test request, adds no retry and leaves the native context ring, Usage accounting and expandable compaction history unchanged. See [context evidence](./docs/copilot-usage.md#historical-context-evidence).
|
|
181
184
|
|
|
182
185
|
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.
|
|
183
186
|
|
|
@@ -229,7 +232,7 @@ The Credits account panel shows the current account and **Switch**. Its dropdown
|
|
|
229
232
|
|
|
230
233
|
[Visible-history continuation](./docs/session-continuation.md) is configured beside account switching, not permanently above the composer. New unseeded Sessions default on after the feature's first successful activation; existing Sessions and inherited histories remain off unless explicitly authorized. Global defaults affect new Sessions only; Session on/off overrides persist across accounts/restarts until disabled. With continuation off, a different-account switch offers persistent enable, keep off or cancel, without a one-turn mode. Each new enabled turn omits prior encrypted reasoning and embedded summaries, even on the same account; current-turn reasoning, visible messages, tools and disk history remain unchanged. Authorization never auto-sends/retries and is not a quota/context cure. Exact replay failures expose the same policy and require a separate native retry. The pinned Core lacks a public Models deep link; Chat omits the nonfunctional management entry. Full management remains in Settings → Models → GitHub Copilot → Manage.
|
|
231
234
|
|
|
232
|
-
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.
|
|
235
|
+
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.
|
|
233
236
|
|
|
234
237
|
## Ownership and further reading
|
|
235
238
|
|
|
@@ -269,14 +272,14 @@ Commit attribution uses `Assisted-by` with the actual tool, never the model prov
|
|
|
269
272
|
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.
|
|
270
273
|
|
|
271
274
|
```sh
|
|
272
|
-
curl -LO https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.0-alpha.
|
|
273
|
-
curl -LO https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.0-alpha.
|
|
275
|
+
curl -LO https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.0-alpha.130/dsh-github-copilot-0.4.0-alpha.130.tgz
|
|
276
|
+
curl -LO https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.0-alpha.130/SHA256SUMS
|
|
274
277
|
sha256sum --check SHA256SUMS
|
|
275
278
|
```
|
|
276
279
|
|
|
277
280
|
```powershell
|
|
278
281
|
$expected = (Get-Content .\SHA256SUMS).Split()[0]
|
|
279
|
-
$actual = (Get-FileHash .\dsh-github-copilot-0.4.0-alpha.
|
|
282
|
+
$actual = (Get-FileHash .\dsh-github-copilot-0.4.0-alpha.130.tgz -Algorithm SHA256).Hash.ToLowerInvariant()
|
|
280
283
|
if ($actual -cne $expected) { throw 'Release checksum mismatch' }
|
|
281
284
|
```
|
|
282
285
|
|
package/README.zh.md
CHANGED
|
@@ -24,7 +24,7 @@ Models 和 Chat 共用不透明、随主题适配的账号下拉层;原生菜
|
|
|
24
24
|
|
|
25
25
|
添加账号时,设备授权链接、可选择的网址、一次性授权码、复制授权码和取消操作会同时显示。GitHub 授权完成后,会单独显示身份与可用模型验证阶段。添加账号不会更改全局默认;准备好后仍需显式执行现有的**切换**操作。技术诊断收在次级折叠区;账号/历史 turn 缺少身份时不会暴露不透明账号 ID,也不会根据当前设置推断历史身份。
|
|
26
26
|
|
|
27
|
-
**包版本:`0.4.0-alpha.
|
|
27
|
+
**包版本:`0.4.0-alpha.130`(准备中)。支持宿主:官方 DSH / Windows Desktop `0.2.0-rc.2`。** 较早 DSH pin 仅是历史证据,不是当前安装目标。已发布、已安装到 profile、已被运行中的 Host 加载,是三个不同状态。执行下方带版本的命令前须核验正式发布与资产;这些说明不证明已发布或已安装。
|
|
28
28
|
|
|
29
29
|
## 你可以做什么
|
|
30
30
|
|
|
@@ -43,9 +43,10 @@ Models 和 Chat 共用不透明、随主题适配的账号下拉层;原生菜
|
|
|
43
43
|
[本地诊断试点](./docs/plugin-diagnostics.md)记录有界的账号/Checking 与压缩
|
|
44
44
|
汇总,**默认关闭**。安装并加载已发布版本后,进入插件详情设置页 →
|
|
45
45
|
**Local diagnostics → Read status → Enable local collection**,开启本地持久化;
|
|
46
|
-
|
|
47
|
-
|
|
48
|
-
|
|
46
|
+
不上传,不启用定时分析。包内另提供显式离线分析器,只处理调用者指定的持久化单元
|
|
47
|
+
或经审阅的聚合视图,并且只新建本地报告文件;不会扫描、上传或更改采集设置。
|
|
48
|
+
暂停保留证据,清除需单独确认。Client/Host 分开统计,未覆盖路径、报告丢失与存储
|
|
49
|
+
故障明确显示。描述性计数不是历史重建、错误率,也不表示优化效果已被验证。
|
|
49
50
|
|
|
50
51
|
| 任务 | 入口 |
|
|
51
52
|
|---|---|
|
|
@@ -83,10 +84,10 @@ node package/scripts/check-search-composition.mjs --profile-dir /absolute/profil
|
|
|
83
84
|
**独立具名 profile**:
|
|
84
85
|
|
|
85
86
|
```sh
|
|
86
|
-
dsh plugin --profile web add https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.0-alpha.
|
|
87
|
+
dsh plugin --profile web add https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.0-alpha.130/dsh-github-copilot-0.4.0-alpha.130.tgz
|
|
87
88
|
```
|
|
88
89
|
|
|
89
|
-
**Desktop** 原生包管理器在发布后接受 `dsh-github-copilot@0.4.0-alpha.
|
|
90
|
+
**Desktop** 原生包管理器在发布后接受 `dsh-github-copilot@0.4.0-alpha.130`。官方 rc.2 **Desktop 随附的专属 CLI**也支持管理保留 profile;全局/普通 `dsh` shim 不等价。使用前核验实际安装入口,参见[Desktop CLI 核验](./docs/npm-distribution.md#desktop-bundled-cli-on-official-rc2)及独立的[具名 profile 离线流程](./docs/npm-distribution.md#controlled-offline-cli-maintenance-for-standalone-profiles)。两种路径都不授权绕过包源政策、修改 peer 或删除配置。
|
|
90
91
|
|
|
91
92
|
经批准 reload/restart 后:
|
|
92
93
|
|
|
@@ -155,7 +156,7 @@ Copilot 搜索要求当前账号/协议证据及能力 proof。固定/fallba
|
|
|
155
156
|
|
|
156
157
|
**Credits**展示已验证账号计费周期数据,不是上下文 tokens 或会话成本。过期、组织共享及不可用数据保留真实语义。仅额度请求在保持 TLS 验签下合并 Node 与系统 CA;不改变登录、模型、搜索或整个 Desktop 的信任配置。
|
|
157
158
|
|
|
158
|
-
原生上下文占用与 Turn Usage 由 Core 所有。插件原样转发 usage
|
|
159
|
+
原生上下文占用与 Turn Usage 由 Core 所有。插件原样转发 usage,包括失败/取消时的零样本。普通请求进行中或暂时没有新采样时保持安静;只有明确的失败零采样或无效采样事件才显示可关闭的独立上下文警告。保留的计数只标记为历史证据,不推断当前占用或替代百分比。**Turn Usage incomplete**解释缺失样本/生命周期及已记录本地阻断,不编造零用量或部分总和。取消可以保留 usage,但不保证收到供应方最终回执。[用量边界](./docs/copilot-usage.md)。
|
|
159
160
|
|
|
160
161
|
插件恢复 timeout/replay 结构化错误前会保留原生 usage,包括非零采样。失败的零采样仍可能让原生圆环显示 `0%`,不代表请求上下文为空。重试条目的耗时表示退避等待,不是失败请求耗时;用量修复不等于解决供应方 HTTP 408,也不改变重试策略。
|
|
161
162
|
|
|
@@ -167,7 +168,7 @@ Copilot 搜索要求当前账号/协议证据及能力 proof。固定/fallba
|
|
|
167
168
|
|
|
168
169
|
**“降级续聊”也覆盖本 Session 的原生托管 Responses 压缩,包括自动摘要**:开启后不需要额外手动恢复命令,也不必先失败再重试。发出的输入省略旧加密 reasoning 及其内嵌摘要,隐藏上下文可能丢失;可见消息、工具调用/结果关系和原历史保留,仅由原生事务提交更小的检查点。输入区提示降级,并区分已提交、失败和取消。关闭时,明确的回放作用域拒绝提供同一个带损失说明的开启入口;未知错误不授权降级。`/copilot-compact visible-history` 保留为已选用恢复引擎的一次性高级入口。参见[授权与恢复限制](./docs/manual-compaction-recovery.md#explicit-visible-history-summary-recovery);这不启用缺失的引擎,也不修复容量、额度或超时问题。
|
|
169
170
|
|
|
170
|
-
|
|
171
|
+
输入区在原有八秒结果窗口内分别说明**压缩已完成**和**后续请求已成功**,不会把普通请求进度或暂时没有新采样变成常驻警告。后续明确的采样事件可独立出现,并可展示标记清楚的历史计数,但绝不推算占用百分比。插件不额外发送测试请求、不增加重试,保留原生圆环、Usage 记账及可展开的压缩历史。参见[上下文证据](./docs/copilot-usage.md#historical-context-evidence)。
|
|
171
172
|
|
|
172
173
|
可见历史压缩进行中时提示持续可见。确认成功后从首次观察起八秒自动消失;失败、取消、状态不可用和开启提示保留至手动**关闭**(或原有**取消**)。关闭仅隐藏当前 Session/操作/状态的提示,不改变授权、历史或原生证据,不发送或重试。Client 注册范围内的有界状态使临时重挂载和会话切换不会重置期限;注册销毁或记录淘汰后不保留。
|
|
173
174
|
|
|
@@ -219,7 +220,7 @@ Credits 账号面板显示当前账号和 **切换**,下拉菜单只列已有
|
|
|
219
220
|
|
|
220
221
|
[可见历史续聊模式](./docs/session-continuation.md)放在账号切换旁,不再常驻输入框上方。功能首次成功激活后创建的非继承 Session 默认开启;已有 Session、继承历史仍需明确授权。全局默认只影响新 Session,Session 开关跨账号及重启保留,直到关闭。关闭时切换到不同账号,提供持续开启、保持关闭或取消,不再提供仅下一轮模式。启用后的每个新 turn 省略旧加密推理及其内嵌摘要,同账号也适用;当前轮新推理、可见消息、工具记录和磁盘历史不变。授权不自动发送或重试,不解决额度或上下文超限。精确回放失败使用同一个持久策略,用户另行点击原生重试。当前 Core 没有公开 Models 直达 API,Chat 不展示不可用的管理入口;完整管理仍在设置 → 模型 → GitHub Copilot → 管理。
|
|
221
222
|
|
|
222
|
-
|
|
223
|
+
上下文证据与回放恢复以紧凑、居中提示显示在输入框上方,宽度遵循原生输入框。模型、项数和状态刷新收进默认折叠的技术详情;有损恢复仍需明确确认。上下文采样只在明确事件时告警,可按 Session/事件关闭,且不会断言原生仪表当前值;原生统计不变。切换账号不会让旧加密推理自动变得可跨账号使用。简短 scope 错误指向显式恢复或新会话;有界、脱敏的请求结构计数留在 Host 诊断中,不挤占主错误。**已授权**只表示授权已准备好,不表示消息已发送或恢复已成功。
|
|
223
224
|
|
|
224
225
|
## 所有权与深入阅读
|
|
225
226
|
|
|
@@ -259,14 +260,14 @@ Agent 从 `node scripts/agent.mjs describe --json`、`doctor --json`及`plan <ta
|
|
|
259
260
|
GitHub Releases 和 npm 分发同一原始已校验 tarball。固定版本并核验 Release SHA-256 或 npm `dist.integrity`;不重打包不可变 Release、不移动/复用 tag。
|
|
260
261
|
|
|
261
262
|
```sh
|
|
262
|
-
curl -LO https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.0-alpha.
|
|
263
|
-
curl -LO https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.0-alpha.
|
|
263
|
+
curl -LO https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.0-alpha.130/dsh-github-copilot-0.4.0-alpha.130.tgz
|
|
264
|
+
curl -LO https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.0-alpha.130/SHA256SUMS
|
|
264
265
|
sha256sum --check SHA256SUMS
|
|
265
266
|
```
|
|
266
267
|
|
|
267
268
|
```powershell
|
|
268
269
|
$expected = (Get-Content .\SHA256SUMS).Split()[0]
|
|
269
|
-
$actual = (Get-FileHash .\dsh-github-copilot-0.4.0-alpha.
|
|
270
|
+
$actual = (Get-FileHash .\dsh-github-copilot-0.4.0-alpha.130.tgz -Algorithm SHA256).Hash.ToLowerInvariant()
|
|
270
271
|
if ($actual -cne $expected) { throw 'Release checksum mismatch' }
|
|
271
272
|
```
|
|
272
273
|
|
package/deployment-baseline.json
CHANGED
|
@@ -8,7 +8,7 @@
|
|
|
8
8
|
},
|
|
9
9
|
"package": {
|
|
10
10
|
"name": "dsh-github-copilot",
|
|
11
|
-
"version": "0.4.0-alpha.
|
|
11
|
+
"version": "0.4.0-alpha.130"
|
|
12
12
|
},
|
|
13
13
|
"evidence": {
|
|
14
14
|
"kind": "source-and-synthetic-test-inventory",
|
|
@@ -406,7 +406,7 @@
|
|
|
406
406
|
{"file": "src/index.ts", "marker": "installContextEvidence(ctx)"},
|
|
407
407
|
{"file": "src/client.ts", "marker": "registerContextEvidenceUi"},
|
|
408
408
|
{"file": "src/context-evidence.ts", "marker": "githubCopilotContextEvidence"},
|
|
409
|
-
{"file": "src/context-evidence-ui.ts", "marker": "
|
|
409
|
+
{"file": "src/context-evidence-ui.ts", "marker": "ContextIncidentPresentation"},
|
|
410
410
|
{"file": "src/replay-recovery-ui.ts", "marker": "conversation.input.dock"},
|
|
411
411
|
{"file": "src/composer-notice-style.ts", "marker": "var(--dsh-content-font-size-secondary, 13px)"},
|
|
412
412
|
{"file": "docs/copilot-usage.md", "marker": "historical input sample, not current occupancy"}
|
|
@@ -416,7 +416,10 @@
|
|
|
416
416
|
{"file": "tests/context-evidence.spec.ts", "name": "replays failed zero samples without discarding the last valid input sample"},
|
|
417
417
|
{"file": "tests/context-evidence.spec.ts", "name": "separates committed compaction, subsequent request success and applicable input sampling"},
|
|
418
418
|
{"file": "tests/context-evidence.spec.ts", "name": "tracks unchanged-header native steps and reads only the settled message source leaves"},
|
|
419
|
+
{"file": "tests/context-evidence.spec.ts", "name": "keeps ordinary repeated steps and unsampled success quiet after compaction"},
|
|
419
420
|
{"file": "tests/context-evidence-ui.spec.ts", "name": "labels counts as historical rather than current occupancy in %s"},
|
|
421
|
+
{"file": "tests/context-evidence-ui.spec.ts", "name": "reacts to only the current open Session and pending selection, preserving the native meter"},
|
|
422
|
+
{"file": "tests/context-evidence-ui.spec.ts", "name": "keeps unknown projection evidence diagnostic-only"},
|
|
420
423
|
{"file": "tests/replay-recovery-ui.spec.ts", "name": "uses native auxiliary typography for the entire notice and inherited controls in an independent dock row"},
|
|
421
424
|
{"file": "tests/fixtures/session-context-core.fixture.ts", "name": "cold-folds native model selections independently without replacing the controller projection"},
|
|
422
425
|
{"file": "tests/preview-route.spec.ts", "name": "forwards native SDK failed zero usage without changing the shared accounting stream"},
|
package/docs/copilot-usage.md
CHANGED
|
@@ -40,13 +40,13 @@ The time beside **Retried model request** is the recorded retry backoff, not the
|
|
|
40
40
|
|
|
41
41
|
The separate, strict `githubCopilotContextEvidence` session projection reads only routing and numeric usage from ordinary durable events. It keeps the last applicable input-plus-cache sample when a failed all-zero attempt is replayed. Model changes, compaction, surface replacement, conflicting source attribution and invalid metadata revoke the sample. It never reads message content or opaque replay, registers under a Core key, changes the native pressure projection, or rewrites durable history.
|
|
42
42
|
|
|
43
|
-
An additive composer disclosure identifies
|
|
43
|
+
An additive composer disclosure identifies only a concrete failed-zero or invalid-sample incident for the current open Copilot Session. Ordinary request progress, a newly opened step and absence of a fresh sample do not create a warning. Any retained count is explicitly a **historical input sample, not current occupancy**; no capacity or percentage is inferred, and the copy does not assert what the separate native meter currently displays. The native context ring and account Credits control remain separate and unchanged. Missing, malformed or otherwise unknown projection/slot/runtime evidence produces a named diagnostic instead of a success-shaped UI or guessed count.
|
|
44
44
|
|
|
45
|
-
Compaction feedback shares this disclosure
|
|
45
|
+
Compaction feedback shares this disclosure without turning sampling absence into a second warning. **Compaction completed** requires a matching native checkpoint and successful end, or the account-bound Host's confirmed native commit. The existing eight-second result can separately report a subsequent request outcome; running, failed, cancelled and unconfirmed compaction outcomes remain distinct. Once that transient result expires, ordinary post-compaction steps stay quiet unless they produce a concrete sampling incident. The native expandable **Context compacted** history row remains unchanged.
|
|
46
46
|
|
|
47
|
-
The independent projection retains only the latest compaction bracket
|
|
47
|
+
The independent projection retains only the latest compaction bracket, subsequent ordinary-request evidence and latest sequenced sampling incident. A normal successful settlement after that bracket is reported separately from an applicable input-plus-cache sample. It observes public step/header and same-step source/terminal metadata, including unchanged-header steps and retries; summary output is never a subsequent chat success. Missing usage can coexist with request success without becoming an incident. A failed zero or malformed/conflicting usage sample creates an incident; a later applicable valid sample clears it. Model changes, compaction and surface replacement revoke the old incident rather than allowing it to reappear for another route. A recorded post-compaction count is still historical, not exact current occupancy. No extra test message, automatic retry, content/replay read, durable event or replacement percentage is added. Projection state version 3 requests a native refold, not history conversion.
|
|
48
48
|
|
|
49
|
-
The transient commit/loss status follows the eight-second completion expiry and manual Close rules. Its registration-owned presentation bound moves with the notice into the context UI.
|
|
49
|
+
The transient commit/loss status follows the eight-second completion expiry and manual Close rules. Its registration-owned presentation bound moves with the notice into the context UI. A separate bounded Client presentation remembers dismissal by Session and incident sequence across ordinary remounts and Session switches. Dismissal hides only that incident; a newer independent incident can notify, and a later applicable valid sample clears the projection incident. Registration teardown or bounded eviction may discard presentation-only dismissal. Native compaction history remains expandable throughout.
|
|
50
50
|
|
|
51
51
|
Local synthetic tests establish native-stream preservation, historical-fold and presentation behavior only. Exact published-adapter and public-registry acceptance, complete CI, publication and loaded Desktop state must be verified separately. No live provider call or Session restart is needed for these tests.
|
|
52
52
|
|
|
@@ -118,6 +118,70 @@ factory in its own isolated realm, sharing the actual public Cordis identity.
|
|
|
118
118
|
It does not substitute tagged source for published bytes or attach to a live
|
|
119
119
|
Client module registry; factory qualification is not Desktop activation proof.
|
|
120
120
|
|
|
121
|
+
## Explicit offline analysis (#368)
|
|
122
|
+
|
|
123
|
+
The package provides a separate, read-only analyzer for one explicitly selected
|
|
124
|
+
aggregate file. Build the package first, then provide an absolute input path, an
|
|
125
|
+
input mode, and a new local output path. The output is created exclusively and
|
|
126
|
+
is never printed to stdout or sent over the network:
|
|
127
|
+
|
|
128
|
+
```sh
|
|
129
|
+
node scripts/analyze-diagnostics.mjs --input "ABSOLUTE_UNIT_FILE.json" --mode persisted-unit --profile-name "PROFILE_NAME" --output "NEW_LOCAL_REPORT.json"
|
|
130
|
+
```
|
|
131
|
+
|
|
132
|
+
Replace the quoted placeholders before running; the input must be an absolute
|
|
133
|
+
path whose basename matches the profile-qualified unit filename.
|
|
134
|
+
|
|
135
|
+
For an explicitly reviewed Client/Host Remote view export, use
|
|
136
|
+
`--mode reviewed-view` and omit `--profile-name`. The persisted-unit mode
|
|
137
|
+
requires the unit basename and unit envelope to match the supplied 1–48
|
|
138
|
+
character ASCII DSH profile name; the name is mapped using the same public
|
|
139
|
+
profile-qualified storage-domain convention as the collector. The operator
|
|
140
|
+
must identify the file and profile. The tool never searches DSH homes,
|
|
141
|
+
enumerates storage units, opens a storage-domain writer or RPC, reads Settings,
|
|
142
|
+
credentials or history, or falls back between modes.
|
|
143
|
+
|
|
144
|
+
Both modes reuse the collector's strict Zod snapshot/view vocabulary. The
|
|
145
|
+
reader rejects symlinks and non-files, caps input at 8 MiB, opens only for
|
|
146
|
+
reading, decodes fatal UTF-8, and checks file identity, size and modification
|
|
147
|
+
metadata before and after reading. These checks bound and detect ordinary
|
|
148
|
+
concurrent changes; they do not attest the active Host's backend and cannot
|
|
149
|
+
eliminate every filesystem race. Errors expose fixed diagnostic codes, not
|
|
150
|
+
paths, rejected values or raw filesystem details. The strict versioned report
|
|
151
|
+
contains only validated dimensions, bounded counts and explicit gaps. An
|
|
152
|
+
existing output is never overwritten.
|
|
153
|
+
|
|
154
|
+
Populations stay separate by build version, Client/Host layer and operation,
|
|
155
|
+
including logical/physical pairs. Starts and terminal counters are reported
|
|
156
|
+
independently because UTC-hour aggregation and retention can censor either
|
|
157
|
+
side; pending-start subtraction and exact operation failure rates are never
|
|
158
|
+
calculated. Only terminal observations enter duration bins. Stage-age bins are
|
|
159
|
+
cumulative operation ages, not exclusive phase timings. Client pending samples
|
|
160
|
+
are repeated historical observations, not an outstanding-work gauge; persisted
|
|
161
|
+
Host pending rows describe the stored snapshot, not current live work.
|
|
162
|
+
|
|
163
|
+
Outcomes remain separate, including policy rejection, revocation,
|
|
164
|
+
environment-fault, unknown and interrupted. Safe sums that exceed JavaScript's
|
|
165
|
+
exact integer range become `null` with an overflow gap. Fixed semantic candidate
|
|
166
|
+
fingerprints contain only coverage version, layer, operation, metric and
|
|
167
|
+
allowlisted reason—never identity hashes. Candidates do not prove a regression,
|
|
168
|
+
persistent fault, unique impact or root cause. Reports do not claim calibrated
|
|
169
|
+
thresholds, trends, percentiles, effectiveness or live collection status from
|
|
170
|
+
a persisted-only file. Empty, stale, paused, dirty, saturated, dropped,
|
|
171
|
+
evicted, interrupted and clock-discontinuous evidence remains explicit;
|
|
172
|
+
missing account-switch or compaction observations are gaps, not zero failures.
|
|
173
|
+
A physical summary-call success is explicitly not a native checkpoint commit;
|
|
174
|
+
only the logical compaction population can label a matching checkpoint and end
|
|
175
|
+
as observed success.
|
|
176
|
+
|
|
177
|
+
The first locally qualified persisted snapshot produced a private descriptive
|
|
178
|
+
report outside the repository. It is not a release artifact, CI fixture, issue
|
|
179
|
+
attachment or proof that alpha.128 is installed, loaded, collecting now, or
|
|
180
|
+
representative of current behavior. Do not publish that report or its counts
|
|
181
|
+
without separate sharing approval. Synthetic tests never read production
|
|
182
|
+
storage. There is no scheduler, automatic analysis, upload, issue creation,
|
|
183
|
+
repair or live-profile mutation in this milestone.
|
|
184
|
+
|
|
121
185
|
## Archived phase-0 qualification and proposals
|
|
122
186
|
|
|
123
187
|
The remaining sections preserve the reviewed phase-0 inventory. Their proposed
|