dsh-github-copilot 0.4.0-alpha.91 → 0.4.0-alpha.93

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
@@ -83,6 +83,8 @@ Alpha.25 admits native `subagent/descriptor` v3, already v3 in the retained rc.1
83
83
 
84
84
  ## Non-negotiable invariants
85
85
 
86
+ - Explicit replay recovery (#279) 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. Two-stage confirmation may omit matching old encrypted items and their item summaries on future outgoing requests, never durable history or new reasoning. Active-turn writes, ambient-scope calls and automatic retries are forbidden. Expiry, disposal and proof discontinuity revoke evidence. See `docs/model-compatibility-acceptance.md`.
87
+
86
88
  - 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.
87
89
  - 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.
88
90
  - Solve protocol gaps inside the plugin using existing published extension points. Do not require a new Core capability/service or patch Core to keep a single route. The managed account-model route reuses the published adapter with one shared OAuth grant; label multiple routes honestly. Keep canonical Core models/configuration under their existing owner instead of rewriting them from the companion's pi catalog.
package/CHANGELOG.md CHANGED
@@ -1,5 +1,15 @@
1
1
  # Changelog
2
2
 
3
+ ## 0.4.0-alpha.93 (prepared)
4
+
5
+ - Add default-off, explicit session replay recovery after verified Responses scope rejection. Confirming the disclosed loss omits only matching old encrypted items and their summaries on later requests; stored history, tool pairs and new reasoning remain unchanged.
6
+ - Bind recovery to native Agent lookup, initiating request signals, model/account proof and bounded Host-lifetime evidence. Do not automatically retry or treat this as a 408 fix.
7
+
8
+ ## 0.4.0-alpha.92 (prepared)
9
+
10
+ - Match the historical context disclosure title to neighboring composer statistics using the existing secondary font-size/line-height tokens, normal weight and tertiary label color (#283).
11
+ - Preserve native disclosure interaction, localization, historical evidence, context metering and Usage ownership; this changes presentation only.
12
+
3
13
  ## 0.4.0-alpha.91 (prepared)
4
14
 
5
15
  - Prevent known continuing-step managed input pressure before native model-attempt admission through the public `agent/pre-step` seam (#280), using the initiating Agent's current compaction service and one native transaction.
package/README.md CHANGED
@@ -8,7 +8,7 @@
8
8
 
9
9
  GitHub Copilot account discovery, contextual Auto routing and hosted search for DSH. The plugin reuses DSH's published native adapter and one Host-owned OAuth account; it does not patch Core or maintain a second model catalog.
10
10
 
11
- **Current release: `0.4.0-alpha.91`. 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.
11
+ **Source candidate: `0.4.0-alpha.93` (unreleased). 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. The versioned commands below are for this candidate after publication, not evidence that its assets exist.
12
12
 
13
13
  ## What you can do
14
14
 
@@ -40,10 +40,10 @@ Supply any launcher patches with repeated `--patch /absolute/file`. Require `sup
40
40
  For a **standalone named profile**:
41
41
 
42
42
  ```sh
43
- dsh plugin --profile web add https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.0-alpha.91/dsh-github-copilot-0.4.0-alpha.91.tgz
43
+ dsh plugin --profile web add https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.0-alpha.93/dsh-github-copilot-0.4.0-alpha.93.tgz
44
44
  ```
45
45
 
46
- For **Desktop**, its native package manager accepts `dsh-github-copilot@0.4.0-alpha.91`. 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.
46
+ For **Desktop**, its native package manager accepts `dsh-github-copilot@0.4.0-alpha.93` 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.
47
47
 
48
48
  After an approved reload/restart:
49
49
 
@@ -132,7 +132,7 @@ Configuration is under `github-copilot`. Credentials, endpoint definitions and a
132
132
  | Selection unknown/unavailable | Distinguish lost evidence from read failure; Retry only rereads |
133
133
  | Missing/cancelled Turn Usage | Read [usage limitations](./docs/copilot-usage.md); do not infer zero billing |
134
134
  | History fails on `github-copilot/auto-model-decision` | Use [detached, check-first recovery](./docs/automatic-model-routing.md#recovering-affected-histories); never replace live history without stopped writers and approval |
135
- | AUTH, Responses replay-scope or TLS failure | Review [request diagnostics](./docs/model-compatibility-acceptance.md#authentication-replay-and-request-diagnostics) and [usage TLS boundaries](./docs/copilot-usage.md#account-data-boundary); never discard opaque replay, reset credentials or disable TLS as an automatic repair |
135
+ | AUTH, Responses replay-scope or TLS failure | Review [request diagnostics](./docs/model-compatibility-acceptance.md#authentication-replay-and-request-diagnostics) and [usage TLS boundaries](./docs/copilot-usage.md#account-data-boundary). After an exact scope rejection, the session's **Replay recovery** offers default-off, explicit loss confirmation for matching old encrypted items and their summaries. It never rewrites stored history or retries automatically, and is not a 408 fix. Never reset credentials or disable TLS as an automatic repair. |
136
136
  | Hosted search unavailable | Check account/protocol/probe diagnostics; a legacy override stays authoritative until explicitly reset |
137
137
 
138
138
  ## Ownership and further reading
@@ -173,14 +173,14 @@ Commit attribution uses `Assisted-by` with the actual tool, never the model prov
173
173
  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.
174
174
 
175
175
  ```sh
176
- curl -LO https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.0-alpha.91/dsh-github-copilot-0.4.0-alpha.91.tgz
177
- curl -LO https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.0-alpha.91/SHA256SUMS
176
+ curl -LO https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.0-alpha.93/dsh-github-copilot-0.4.0-alpha.93.tgz
177
+ curl -LO https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.0-alpha.93/SHA256SUMS
178
178
  sha256sum --check SHA256SUMS
179
179
  ```
180
180
 
181
181
  ```powershell
182
182
  $expected = (Get-Content .\SHA256SUMS).Split()[0]
183
- $actual = (Get-FileHash .\dsh-github-copilot-0.4.0-alpha.91.tgz -Algorithm SHA256).Hash.ToLowerInvariant()
183
+ $actual = (Get-FileHash .\dsh-github-copilot-0.4.0-alpha.93.tgz -Algorithm SHA256).Hash.ToLowerInvariant()
184
184
  if ($actual -cne $expected) { throw 'Release checksum mismatch' }
185
185
  ```
186
186
 
package/README.zh.md CHANGED
@@ -8,7 +8,7 @@
8
8
 
9
9
  为 DSH 提供 GitHub Copilot 账号模型发现、上下文 Auto 选模和 hosted search。插件复用 DSH 公开的原生适配器与一个 Host 端 OAuth 账号,不修改 Core,也不维护第二套模型目录。
10
10
 
11
- **当前版本:`0.4.0-alpha.91`。支持宿主:官方 DSH / Windows Desktop `0.2.0-rc.2`。** 较早 DSH pin 仅是历史证据,不是当前安装目标。已发布、已安装到 profile、已被运行中的 Host 加载,是三个不同状态。
11
+ **源码候选版本:`0.4.0-alpha.93`(尚未发布)。支持宿主:官方 DSH / Windows Desktop `0.2.0-rc.2`。** 较早 DSH pin 仅是历史证据,不是当前安装目标。已发布、已安装到 profile、已被运行中的 Host 加载,是三个不同状态。下方带版本的命令适用于候选版本发布后,不代表对应资产已经存在。
12
12
 
13
13
  ## 你可以做什么
14
14
 
@@ -40,10 +40,10 @@ node package/scripts/check-search-composition.mjs --profile-dir /absolute/profil
40
40
  **独立具名 profile**:
41
41
 
42
42
  ```sh
43
- dsh plugin --profile web add https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.0-alpha.91/dsh-github-copilot-0.4.0-alpha.91.tgz
43
+ dsh plugin --profile web add https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.0-alpha.93/dsh-github-copilot-0.4.0-alpha.93.tgz
44
44
  ```
45
45
 
46
- **Desktop** 原生包管理器接受 `dsh-github-copilot@0.4.0-alpha.91`。官方 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 或删除配置。
46
+ **Desktop** 原生包管理器在发布后接受 `dsh-github-copilot@0.4.0-alpha.93`。官方 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 或删除配置。
47
47
 
48
48
  经批准 reload/restart 后:
49
49
 
@@ -132,7 +132,7 @@ HTTP/SSE liveness 默认区分 5 分钟字节 idle 和有界的 10 分钟助手
132
132
  | 选模未知/不可读 | 区分记录丢失与读取失败;Retry 只重读 |
133
133
  | 缺失/取消后的 Turn Usage | 查看[用量限制](./docs/copilot-usage.md),不推断零计费 |
134
134
  | 历史加载报 `github-copilot/auto-model-decision` | 使用[独立副本、先检查的恢复](./docs/automatic-model-routing.md#recovering-affected-histories);未经批准且未停写不得替换实际历史 |
135
- | AUTH、Responses replay scope 或 TLS 错误 | 查看[请求诊断](./docs/model-compatibility-acceptance.md#authentication-replay-and-request-diagnostics)及[额度 TLS 边界](./docs/copilot-usage.md#account-data-boundary),不自动丢 replay、重置凭据或关闭 TLS |
135
+ | AUTH、Responses replay scope 或 TLS 错误 | 查看[请求诊断](./docs/model-compatibility-acceptance.md#authentication-replay-and-request-diagnostics)及[额度 TLS 边界](./docs/copilot-usage.md#account-data-boundary)。精确 scope 拒绝后,会话的**回放恢复**可在明确接受损失后启用,仅跳过匹配的旧加密项及项内摘要,默认关闭。不改磁盘历史、不自动重试,也不是 408 修复。不自动重置凭据或关闭 TLS。 |
136
136
  | Hosted search 不可用 | 检查账号/协议/probe 诊断;旧 override 保留至显式 reset |
137
137
 
138
138
  ## 所有权与深入阅读
@@ -173,14 +173,14 @@ Agent 从 `node scripts/agent.mjs describe --json`、`doctor --json`及`plan <ta
173
173
  GitHub Releases 和 npm 分发同一原始已校验 tarball。固定版本并核验 Release SHA-256 或 npm `dist.integrity`;不重打包不可变 Release、不移动/复用 tag。
174
174
 
175
175
  ```sh
176
- curl -LO https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.0-alpha.91/dsh-github-copilot-0.4.0-alpha.91.tgz
177
- curl -LO https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.0-alpha.91/SHA256SUMS
176
+ curl -LO https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.0-alpha.93/dsh-github-copilot-0.4.0-alpha.93.tgz
177
+ curl -LO https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.0-alpha.93/SHA256SUMS
178
178
  sha256sum --check SHA256SUMS
179
179
  ```
180
180
 
181
181
  ```powershell
182
182
  $expected = (Get-Content .\SHA256SUMS).Split()[0]
183
- $actual = (Get-FileHash .\dsh-github-copilot-0.4.0-alpha.91.tgz -Algorithm SHA256).Hash.ToLowerInvariant()
183
+ $actual = (Get-FileHash .\dsh-github-copilot-0.4.0-alpha.93.tgz -Algorithm SHA256).Hash.ToLowerInvariant()
184
184
  if ($actual -cne $expected) { throw 'Release checksum mismatch' }
185
185
  ```
186
186
 
@@ -8,7 +8,7 @@
8
8
  },
9
9
  "package": {
10
10
  "name": "dsh-github-copilot",
11
- "version": "0.4.0-alpha.91"
11
+ "version": "0.4.0-alpha.93"
12
12
  },
13
13
  "evidence": {
14
14
  "kind": "source-and-synthetic-test-inventory",
@@ -679,6 +679,27 @@
679
679
  {"file": "tests/preview-route.spec.ts", "name": "does not retain a replay-scope failure across independent dispatches of one native prepared lease: %s"}
680
680
  ]
681
681
  },
682
+ {
683
+ "id": "managed-explicit-replay-recovery",
684
+ "required": true,
685
+ "scope": "managed-responses-initiating-session-only-explicit-loss-confirmation",
686
+ "liveEndpointAcceptance": "diagnostic-ablation-only-not-installed-feature-acceptance",
687
+ "sourceMarkers": [
688
+ {"file": "src/replay-recovery.ts", "marker": "class ReplayRecoveryStore"},
689
+ {"file": "src/replay-recovery-host.ts", "marker": "extends TypertRemoteService"},
690
+ {"file": "src/replay-recovery-host.ts", "marker": "COPILOT_REPLAY_RECOVERY_TURN_ACTIVE"},
691
+ {"file": "src/replay-recovery-remote.ts", "marker": "githubCopilotReplayRecovery.setEnabled"},
692
+ {"file": "src/replay-recovery-ui.ts", "marker": "Accept loss and enable"}
693
+ ],
694
+ "tests": [
695
+ {"file": "tests/replay-recovery.spec.ts", "name": "keeps default replay and requires a revision-bound confirmation"},
696
+ {"file": "tests/replay-recovery.spec.ts", "name": "preserves source, fresh reasoning, tools, other models and other owners"},
697
+ {"file": "tests/replay-recovery-host.spec.ts", "name": "requires the native initiating session and signal, rejects active-turn writes and revokes late requests"},
698
+ {"file": "tests/replay-recovery-ui.spec.ts", "name": "requires an explicit loss confirmation, never submits a message and sends the read revision"},
699
+ {"file": "tests/preview-route.spec.ts", "name": "offers exact failed replay only to its initiating session and recovers after explicit confirmation"},
700
+ {"file": "tests/fixtures/remote-core.fixture.ts", "name": "binds explicit replay recovery through native Client and %s Host gateways"}
701
+ ]
702
+ },
682
703
  {
683
704
  "id": "managed-http-auth-rejection-recovery",
684
705
  "required": true,
@@ -76,6 +76,60 @@ empty summary/content, no encrypted content and no unknown fields. Durable
76
76
  history, public summaries, opaque bytes, nested IDs, phase and `call_id` pairing
77
77
  stay unchanged.
78
78
 
79
+ The source-checkout follow-up for #279 adds bounded structure evidence to an
80
+ exact verified scope rejection: total items, direct ID fields, reference items,
81
+ encrypted reasoning items, unrecognized items, `previous_response_id`/`store`
82
+ state and presence of the two native session/request headers. It observes the
83
+ final HTTP dispatch, not the earlier SDK payload before caller replacement.
84
+ Only fixed labels and counts enter the existing error; no IDs, header values,
85
+ message text, arguments, results or opaque bytes are retained. The shared
86
+ 16 MiB/depth/work diagnostic limits apply; unavailable evidence never becomes
87
+ zero counts. Historical errors without this suffix have no such evidence.
88
+ Structure counts alone do not repair cross-turn scope rejection: zero direct
89
+ IDs does not prove encrypted replay is portable.
90
+
91
+ ### Explicit session replay recovery
92
+
93
+ After an exact verified managed Responses scope rejection, **Replay recovery**
94
+ in that session's composer can offer the failed request's old encrypted items.
95
+ Open it, read the evidence, wait for the active turn to finish, choose **Review
96
+ activation**, then **Accept loss and enable**. It does not send a message or
97
+ retry the failed request. The user chooses whether to submit a subsequent turn.
98
+ The default remains complete native replay.
99
+
100
+ This is lossy recovery, not a supplier-scope repair. Only complete normalized
101
+ encrypted reasoning items whose entire serialized fingerprints match that
102
+ failed request are omitted from later outgoing requests in the same session
103
+ and model. Their hidden state **and their item summaries** are no longer sent;
104
+ displayed messages, tool calls/results and stored history are not modified.
105
+ New or changed reasoning items remain native-owned. Another scope failure
106
+ requires fresh confirmation rather than broadening enabled omission silently.
107
+
108
+ Evidence is bounded to 64 sessions, 512 distinct items per session, and one
109
+ hour in the current Host. Only hashes, a model label and confirmation metadata
110
+ are retained, never opaque payloads. The Client receives count/model/state and
111
+ an opaque revision only. Token/account/metadata proof discontinuity, expiry,
112
+ session disposal or Host restart revokes evidence; an old error on disk cannot
113
+ create a candidate. Re-read status after these changes. Disabling affects
114
+ future requests and does not undo answers already generated.
115
+
116
+ Admission requires the initiating native Agent request signal and exact
117
+ session; unbound requests, compaction, titles, classifier requests, other
118
+ models and other sessions cannot borrow consent. Active-turn writes are
119
+ rejected. Public native Client/Host gateways enforce explicit Agent lookup;
120
+ no ambient Client session projection is added. No Core changes, credentials
121
+ reset, history rewrite, general wire adapter or automatic business retry is
122
+ introduced. This is not a remedy for HTTP 408, quota or context limits.
123
+
124
+ Two explicitly authorized real-history diagnostic calls reproduced HTTP 401
125
+ with 12 old encrypted items and returned HTTP 200 after omitting exactly those
126
+ items in a disposable request copy, preserving all 80 tool pairs. This
127
+ implicates the old item set, not any specific item, token rotation or backend
128
+ expiry rule. Sequential calls cannot freeze hidden supplier state. Synthetic
129
+ request-chain and native gateway tests qualify the opt-in mechanism; they do
130
+ not establish that every rejected history is recoverable or that an installed
131
+ runtime has enabled it.
132
+
79
133
  After actual HTTP 408, a newly prepared attempt in the same native step can
80
134
  reuse exact normalized payload only when transcript/every other field agree,
81
135
  with matching references and no conflicts. Evidence is bound to Session/model/