dsh-github-copilot 0.4.2-alpha.4 → 0.4.2-alpha.5

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/AGENTS.md CHANGED
@@ -128,7 +128,7 @@ Alpha.25 admits native `subagent/descriptor` v3, already v3 in the retained rc.1
128
128
  - `src/serialize.ts`, `src/sse.ts`, `src/failure.ts`: protocol conversion and bounded error handling.
129
129
  - `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.
130
130
  - `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.
131
- - `src/request-body-evidence.ts`: verified-408-only, bounded numeric original-JSON span accounting through the existing fetch hook. Conversation/tool definitions/top-level system/residual partition total bytes; structural image and opaque replay spans are disjoint conversation subsets, never decoded contents. Unknown/limited evidence stays explicit. Fetch-to-header time excludes clone inspection and is not upload duration. With gzip, report original JSON composition and prepared HTTP-body bytes separately; neither establishes delivered bytes. No success-path analysis, retained body, automatic mitigation or supplier-limit claim.
131
+ - `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.
132
132
  - `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.
133
133
  - `tests/`: unit and integration evidence; mirror the source area being changed.
134
134
  - `deployment-baseline.json`: declared machine-readable compatibility and capability evidence inventory.
package/CHANGELOG.md CHANGED
@@ -1,5 +1,18 @@
1
1
  # Changelog
2
2
 
3
+ ## 0.4.2-alpha.5 (prepared)
4
+
5
+ - Measure large request JSON composition up to 32 MiB with a cooperative,
6
+ bounded span scanner instead of a full payload object graph. Preserve
7
+ disjoint image/replay byte subsets, native original spans and explicit
8
+ cancellation/time/work limits; replay validation keeps its 16 MiB boundary.
9
+ - Start opted-in large-body counting after Fetch invocation without holding
10
+ up ordinary response/stream delivery. Fence late numeric updates to their
11
+ own retained row across pause/re-enable, clear, teardown and eviction.
12
+ - Reuse bounded composition work in exact verified-408 guidance. Preserve
13
+ native bytes, response/error, retries, Usage, timeout and default-off gzip;
14
+ composition evidence does not establish a proxy or supplier fault.
15
+
3
16
  ## 0.4.2-alpha.4 (prepared)
4
17
 
5
18
  - Add independently opt-in, content-free managed-adapter physical request
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, 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
- **Stable release: [`0.4.1`](https://github.com/cloga/dsh-github-copilot/releases/tag/v0.4.1); prepared prerelease: `0.4.2-alpha.4`.** `0.4.2-alpha.1` was not published: its release preflight failed, and its immutable tag will not be reused. Supported host: official DSH / Windows Desktop `0.2.0-rc.2`. The stable version is also published on npm's `latest` dist-tag; prereleases remain on their channel tags. Stability-channel promotion does not expand the qualified host baseline or prove live account, model, search or Desktop health. Earlier DSH pins are historical evidence, not supported installation targets. Published, installed in a profile and loaded by a running Host are separate states.
11
+ **Stable release: [`0.4.1`](https://github.com/cloga/dsh-github-copilot/releases/tag/v0.4.1); prepared prerelease: `0.4.2-alpha.5`.** `0.4.2-alpha.1` was not published: its release preflight failed, and its immutable tag will not be reused. Supported host: official DSH / Windows Desktop `0.2.0-rc.2`. The stable version is also published on npm's `latest` dist-tag; prereleases remain on their channel tags. Stability-channel promotion does not expand the qualified host baseline or prove live account, model, search or Desktop health. Earlier DSH pins are historical evidence, not supported installation targets. Published, installed in a profile and loaded by a running Host are separate states.
12
12
 
13
13
  **Upgrade from 0.4.0:** that first stable release can interrupt concurrent managed requests with `COPILOT_PREVIEW_CREDENTIAL_CHANGED` during normal same-account native OAuth renewal. In 0.4.1, a proven plugin-owned refresh with unchanged account, endpoint and entitlements preserves already-dispatched HTTP streams; subsequent requests use freshly validated auth and metadata. Unknown/external credential notifications, revocation, cancellation and provider rejections remain explicit—not a promise of invisible recovery or automatic retry. See [the refresh boundary](./docs/copilot-accounts.md#native-oauth-refresh-and-dispatched-requests-385).
14
14
 
@@ -49,6 +49,11 @@ for 24 hours, with model, JSON/wire byte counts, timings, HTTP status and termin
49
49
  categories. No bodies, headers, credentials or Session/turn IDs are collected.
50
50
  Local body-write completion does not prove supplier receipt; these diagnostics
51
51
  do not fix timeouts or alter retry/Usage behavior.
52
+ Large JSON bodies up to 32 MiB can receive bounded, cooperative composition
53
+ counts without a full payload parse; the approximately 20.4 MiB class no longer
54
+ necessarily hits the old 16 MiB diagnostic blind spot. Time/work/cancellation
55
+ limits remain explicit, and settled rows may acquire counts on a later read.
56
+ No gzip, history trimming or extra retry is enabled. See [request observations](./docs/plugin-diagnostics.md#content-free-physical-request-observations-392).
52
57
  The package also has an explicit offline analyzer
53
58
  for a caller-selected persisted unit or reviewed aggregate view; it writes only
54
59
  to a new local report file and never scans, uploads or changes collection. Pause
@@ -111,10 +116,10 @@ Supply any launcher patches with repeated `--patch /absolute/file`. Require `sup
111
116
  For a **standalone named profile**:
112
117
 
113
118
  ```sh
114
- dsh plugin --profile web add https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.2-alpha.4/dsh-github-copilot-0.4.2-alpha.4.tgz
119
+ dsh plugin --profile web add https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.2-alpha.5/dsh-github-copilot-0.4.2-alpha.5.tgz
115
120
  ```
116
121
 
117
- For **Desktop**, its native package manager accepts an exact npm spec, for example `dsh-github-copilot@0.4.2-alpha.4`; stable versions publish on npm's `latest` dist-tag and prereleases on their channel tags. The official rc.2 **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.
122
+ For **Desktop**, its native package manager accepts an exact npm spec, for example `dsh-github-copilot@0.4.2-alpha.5`; stable versions publish on npm's `latest` dist-tag and prereleases on their channel tags. The official rc.2 **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.
118
123
 
119
124
  After an approved reload/restart:
120
125
 
@@ -290,14 +295,14 @@ Commit attribution uses `Assisted-by` with the actual tool, never the model prov
290
295
  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.
291
296
 
292
297
  ```sh
293
- curl -LO https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.2-alpha.4/dsh-github-copilot-0.4.2-alpha.4.tgz
294
- curl -LO https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.2-alpha.4/SHA256SUMS
298
+ curl -LO https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.2-alpha.5/dsh-github-copilot-0.4.2-alpha.5.tgz
299
+ curl -LO https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.2-alpha.5/SHA256SUMS
295
300
  sha256sum --check SHA256SUMS
296
301
  ```
297
302
 
298
303
  ```powershell
299
304
  $expected = (Get-Content .\SHA256SUMS).Split()[0]
300
- $actual = (Get-FileHash .\dsh-github-copilot-0.4.2-alpha.4.tgz -Algorithm SHA256).Hash.ToLowerInvariant()
305
+ $actual = (Get-FileHash .\dsh-github-copilot-0.4.2-alpha.5.tgz -Algorithm SHA256).Hash.ToLowerInvariant()
301
306
  if ($actual -cne $expected) { throw 'Release checksum mismatch' }
302
307
  ```
303
308
 
package/README.zh.md CHANGED
@@ -8,7 +8,7 @@
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);待发布预览版:`0.4.2-alpha.4`。** `0.4.2-alpha.1` 的发布预检失败,因此未发布;其不可变 tag 不会复用。支持宿主:官方 DSH / Windows Desktop `0.2.0-rc.2`。稳定版也发布到 npm 的 `latest` dist-tag;预发布版本仍使用各自渠道 tag。稳定渠道不扩大已验证的宿主基线,也不证明实时账号、模型、搜索或 Desktop 健康状态。较早 DSH pin 仅是历史证据,不是当前安装目标。已发布、已安装到 profile、已被运行中的 Host 加载,是三个不同状态。
11
+ **稳定版:[`0.4.1`](https://github.com/cloga/dsh-github-copilot/releases/tag/v0.4.1);待发布预览版:`0.4.2-alpha.5`。** `0.4.2-alpha.1` 的发布预检失败,因此未发布;其不可变 tag 不会复用。支持宿主:官方 DSH / Windows Desktop `0.2.0-rc.2`。稳定版也发布到 npm 的 `latest` dist-tag;预发布版本仍使用各自渠道 tag。稳定渠道不扩大已验证的宿主基线,也不证明实时账号、模型、搜索或 Desktop 健康状态。较早 DSH pin 仅是历史证据,不是当前安装目标。已发布、已安装到 profile、已被运行中的 Host 加载,是三个不同状态。
12
12
 
13
13
  **从 0.4.0 升级:**首个正式版在同账号正常原生 OAuth 刷新时,可能以 `COPILOT_PREVIEW_CREDENTIAL_CHANGED` 中止并行托管请求。0.4.1 仅在插件拥有的原生刷新被精确验证,且账号、端点与权限连续时,保留已发出的 HTTP 流;后续请求重新验证认证与模型元数据。未知/外部凭据通知、撤销、取消与供应商拒绝仍明确报错,不承诺所有刷新无感,也不自动重试。参见[刷新边界](./docs/copilot-accounts.md#native-oauth-refresh-and-dispatched-requests-385)。
14
14
 
@@ -38,7 +38,11 @@ Session/turn ID、对话内容,也不推断执行/结果,不自动调参
38
38
  **Enable request observations** 开关保留最多 128 条托管适配器的物理请求观测,保留 24 小时:
39
39
  仅包含模型、JSON/传输字节数、耗时、HTTP 状态和终止分类,不记录正文、headers、
40
40
  凭据或 Session/turn ID。本地写出完成不证明供应方收到了请求;诊断不会修复超时,
41
- 也不改变重试或 Usage。包内另提供显式离线分析器,
41
+ 也不改变重试或 Usage。最高 32 MiB 的大 JSON 请求可通过有界、协作式扫描获得组成计数,
42
+ 不完整解析 payload 对象图;约 20.4 MiB 的请求不再必然落入旧 16 MiB 诊断盲区。
43
+ 耗时/工作量/取消限制仍明确可见,已结束的记录可能在之后读取时才补齐计数。
44
+ 不自动启用 gzip、截断历史或增加重试,参见[请求观测](./docs/plugin-diagnostics.md#content-free-physical-request-observations-392)。
45
+ 包内另提供显式离线分析器,
42
46
  只处理调用者指定的持久化单元或经审阅的聚合视图,并且只新建本地报告文件;不会扫描、
43
47
  上传或更改采集设置。暂停保留证据,清除需单独确认。Client/Host 分开统计,未覆盖路径、
44
48
  报告丢失与存储故障明确显示。描述性计数不是历史重建、错误率,也不表示优化效果已被验证。诊断页默认显示按 UTC 日期、
@@ -95,10 +99,10 @@ node package/scripts/check-search-composition.mjs --profile-dir /absolute/profil
95
99
  **独立具名 profile**:
96
100
 
97
101
  ```sh
98
- dsh plugin --profile web add https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.2-alpha.4/dsh-github-copilot-0.4.2-alpha.4.tgz
102
+ dsh plugin --profile web add https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.2-alpha.5/dsh-github-copilot-0.4.2-alpha.5.tgz
99
103
  ```
100
104
 
101
- **Desktop** 原生包管理器接受精确 npm spec,例如 `dsh-github-copilot@0.4.2-alpha.4`;稳定版发布到 npm `latest` dist-tag,预发布版使用对应渠道 tag。官方 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 或删除配置。
105
+ **Desktop** 原生包管理器接受精确 npm spec,例如 `dsh-github-copilot@0.4.2-alpha.5`;稳定版发布到 npm `latest` dist-tag,预发布版使用对应渠道 tag。官方 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 或删除配置。
102
106
 
103
107
  经批准 reload/restart 后:
104
108
 
@@ -274,14 +278,14 @@ Agent 从 `node scripts/agent.mjs describe --json`、`doctor --json`及`plan <ta
274
278
  GitHub Releases 和 npm 分发同一原始已校验 tarball。固定版本并核验 Release SHA-256 或 npm `dist.integrity`;不重打包不可变 Release、不移动/复用 tag。
275
279
 
276
280
  ```sh
277
- curl -LO https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.2-alpha.4/dsh-github-copilot-0.4.2-alpha.4.tgz
278
- curl -LO https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.2-alpha.4/SHA256SUMS
281
+ curl -LO https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.2-alpha.5/dsh-github-copilot-0.4.2-alpha.5.tgz
282
+ curl -LO https://github.com/cloga/dsh-github-copilot/releases/download/v0.4.2-alpha.5/SHA256SUMS
279
283
  sha256sum --check SHA256SUMS
280
284
  ```
281
285
 
282
286
  ```powershell
283
287
  $expected = (Get-Content .\SHA256SUMS).Split()[0]
284
- $actual = (Get-FileHash .\dsh-github-copilot-0.4.2-alpha.4.tgz -Algorithm SHA256).Hash.ToLowerInvariant()
288
+ $actual = (Get-FileHash .\dsh-github-copilot-0.4.2-alpha.5.tgz -Algorithm SHA256).Hash.ToLowerInvariant()
285
289
  if ($actual -cne $expected) { throw 'Release checksum mismatch' }
286
290
  ```
287
291
 
@@ -8,7 +8,7 @@
8
8
  },
9
9
  "package": {
10
10
  "name": "dsh-github-copilot",
11
- "version": "0.4.2-alpha.4"
11
+ "version": "0.4.2-alpha.5"
12
12
  },
13
13
  "evidence": {
14
14
  "kind": "source-and-synthetic-test-inventory",
@@ -297,6 +297,8 @@
297
297
  {"file": "src/diagnostics-types.ts", "marker": "DIAGNOSTICS_MAX_BYTES = 2 * 1024 * 1024"},
298
298
  {"file": "src/diagnostics-collector.ts", "marker": "noteClientGaps"},
299
299
  {"file": "src/request-diagnostics.ts", "marker": "REQUEST_DIAGNOSTICS_MAX_ROWS = 128"},
300
+ {"file": "src/request-body-composition.ts", "marker": "bytes: 32 * 1024 * 1024"},
301
+ {"file": "src/request-body-composition.ts", "marker": "concurrent: 4"},
300
302
  {"file": "src/request-diagnostics.ts", "marker": "REQUEST_DIAGNOSTICS_RETENTION_MS = 24 * 60 * 60 * 1000"},
301
303
  {"file": "src/config.ts", "marker": "requestDiagnosticsEnabled: z.boolean().default(false).hidden().volatile()"},
302
304
  {"file": "src/diagnostics-host.ts", "marker": "diagnosticsDomainForProfile"},
@@ -308,6 +310,9 @@
308
310
  "tests": [
309
311
  {"file": "tests/diagnostics-collector.spec.ts", "name": "is disabled until enabled, records success denominators and settles once"},
310
312
  {"file": "tests/request-diagnostics.spec.ts", "name": "requires independent consent, captures status/timing and never infers upload or retry count"},
313
+ {"file": "tests/request-body-composition.spec.ts", "name": "partitions a 20.4 MiB request without parsing its payload object graph"},
314
+ {"file": "tests/preview-transport-failures.spec.ts", "name": "does not wait for large-request composition before native success and updates the exact settled row"},
315
+ {"file": "tests/request-diagnostics.spec.ts", "name": "updates only its own retained record after native settlement, never across clear/pause/eviction"},
311
316
  {"file": "tests/preview-transport-failures.spec.ts", "name": "records verified 408 once without changing the native error, serialized input or dispatch count"},
312
317
  {"file": "tests/diagnostics-client.spec.ts", "name": "rejects stale status responses and settles an unmounted Checking operation once"},
313
318
  {"file": "tests/diagnostics-card.spec.ts", "name": "requires a confirmed durable enable and a separate destructive clear confirmation"},
@@ -106,7 +106,7 @@ Original serialized value spans partition total bytes into `input`/`messages`, t
106
106
 
107
107
  Responses tool pictures are also image blocks: the native SDK serializes them under `function_call_output.output[]`, separately from ordinary message `content[]`. Older plugin diagnostics incorrectly classified those spans as remaining history, so an old report of zero image bytes does not establish an image-free request. The corrected diagnostic applies only to newly observed failures; stored failures and history are not rewritten. Unknown output arrays remain residual, and the fix changes neither total bytes nor native image admission, offload budgets, replay or transport.
108
108
 
109
- Analysis accepts at most 16 MiB of UTF-8 JSON, with a pre-parse depth/token bound (64 levels / 131072 tokens), followed by at most 65536 values and 128 serialized key characters. Missing, malformed, unsupported, size-limited and work-limited evidence has a named unavailable state with no partial success-shaped totals. Limits bound diagnostic cost and are **not supplier request limits or admission controls**. A reported 9 MiB body may be analyzed, but its size does not establish why a timeout occurred. If image blocks dominate, an explicitly selected smaller `chatMaxRequestImageBytes` can authorize native image offload; if compressible history dominates, explicit native compaction can help. Tool definitions and opaque replay may remain; small failing requests still warrant network/service investigation. Neither choice is performed automatically or guaranteed to reduce 408 frequency.
109
+ Analysis up to 16 MiB retains the existing span validator. Larger verified-408 JSON bodies use a cooperative span scanner up to 32 MiB without allocating a full payload object graph or decoding image/replay content. Its 65,536-character yields, two-second monotonic deadline and four concurrent scan slots bound additional work; both paths retain 64-level depth, 131072-token, 65536-value and 128-serialized-key-character limits. Separately opted-in physical request observations may already have started that same work after Fetch invocation, without holding up ordinary native response delivery. Verified-408 guidance may await it and preserves Fetch-to-header timing measured before analysis. Missing, malformed, unsupported, size/work/time-limited or cancelled evidence remains explicitly unavailable, never partial success-shaped totals. Replay validation and recovery keep the original 16 MiB limits. These limits are **not supplier request limits or admission controls**. A measured approximately 20.4 MiB body does not establish why a timeout occurred. If image blocks dominate, an explicitly selected smaller `chatMaxRequestImageBytes` can authorize native image offload; if compressible history dominates, explicit native compaction can help. Tool definitions and opaque replay may remain; small failing requests still warrant network/service investigation. Neither choice is performed automatically or guaranteed to reduce 408 frequency.
110
110
 
111
111
  This implementation is preventive, not a general rescue summarizer. A manual summary whose full input already exceeds the hard budget fails before model transport. It does not silently trim, fabricate a partial checkpoint, or claim that refusing the request recovered the history. Giant fixed prefixes or an indivisible latest unit can also prevent useful reduction.
112
112
 
@@ -166,10 +166,26 @@ original JSON and dispatched wire byte counts, encoding, bounded composition
166
166
  partitions, local header/elapsed timing, HTTP status and fixed terminal/reason
167
167
  categories. Existing public native upload observations add ALPN, local body-write
168
168
  timing and writable-buffer bytes only when available. Unsupported/ambiguous
169
- transport evidence stays explicitly unavailable. Composition is bounded to
170
- 16 MiB and fixed parser work limits; larger bodies retain byte counts with
171
- `size-limit`, never an invented composition or unlimited body parse. These are
172
- diagnostic work limits, not provider request limits.
169
+ transport evidence stays explicitly unavailable. Bodies up to 16 MiB retain the
170
+ existing synchronous span validator. Larger JSON bodies, including the reported
171
+ approximately 20.4 MiB class, use a cooperative span scanner up to 32 MiB without
172
+ building a payload object graph or decoding image/replay values. It yields every
173
+ 65,536 scanned characters, checks a two-second monotonic work deadline and caps
174
+ concurrent scans at four. Both paths retain 64-level depth, 65,536-value,
175
+ 131,072-token and 128-serialized-key-character limits. Size, work, time and
176
+ cancellation limits remain named unavailable states without partial totals.
177
+ These are diagnostic work limits, not provider request limits.
178
+
179
+ For opted-in observations, large-body counting starts after Fetch invocation
180
+ and does not delay ordinary native response/stream delivery. A retained row can
181
+ receive its numeric composition after terminal settlement; until then its
182
+ initial `size-limit` remains explicit. Refresh/read/export obtains the currently
183
+ available evidence, not a promise of completion. Pause/re-enable, clear,
184
+ teardown, retention and eviction fence late updates, and the counting work
185
+ retains its source string only for that bounded scan. Actual caller cancellation
186
+ can stop it. Verified-408 guidance may await that same bounded work; without
187
+ request consent only an exact verified failure starts the larger scan.
188
+ Replay validation/recovery keeps its original 16 MiB boundary unchanged.
173
189
 
174
190
  Random stream UUIDs group only dispatches within one native SDK stream.
175
191
  `dispatchIndex` is physical Fetch order, **not** Core's retry number or an
@@ -177,6 +193,10 @@ end-to-end Session/turn correlation. No account/Session/turn IDs or hashes,
177
193
  URLs, headers, raw errors, prompts, tool parameters/results, attachment or replay
178
194
  content, credentials or token accounting are retained. Review timestamps/model
179
195
  metadata before explicit sharing; nothing is uploaded automatically.
196
+ Comparing JSON/wire sizes and partitions within a stream can reveal repeated
197
+ large payload sizes or growth, not duplicate contents, a Core retry count,
198
+ delivery to a proxy/supplier or the reason for a rejection. No request hashes
199
+ are collected and no automatic size-based mitigation is introduced.
180
200
 
181
201
  An exact verified HTTP408 `user_request_timeout` is classified as
182
202
  `request-body-timeout`; other provider/transport errors remain fixed unknown
package/lib/client.js CHANGED
@@ -6614,7 +6614,9 @@ Set the \`cycles\` parameter to \`"ref"\` to resolve cyclical schemas with defs.
6614
6614
  "size-limit",
6615
6615
  "work-limit",
6616
6616
  "invalid-json",
6617
- "unsupported-shape"
6617
+ "unsupported-shape",
6618
+ "cancelled",
6619
+ "time-limit"
6618
6620
  ]),
6619
6621
  totalBytes: integer$1.optional()
6620
6622
  }).strict()]);
@@ -7174,7 +7176,7 @@ Set the \`cycles\` parameter to \`"ref"\` to resolve cyclical schemas with defs.
7174
7176
  };
7175
7177
  //#endregion
7176
7178
  //#region package.json
7177
- var version = "0.4.2-alpha.4";
7179
+ var version = "0.4.2-alpha.5";
7178
7180
  //#endregion
7179
7181
  //#region lib/types/diagnostics-client.js
7180
7182
  let owner;