@deepseek-ai/dsh-session-telemetry 0.1.7-rc.2 → 0.2.0-rc.1

package/README.i18n.yaml

@@ -24,8 +24,8 @@
   en: e3cc8ee7774a0ad5
   zh: 3c039339870b8cf9
 /deepseek-ai-dsh-session-telemetry/use-this-package/what-gets-captured:
-  en: ed96f8ed3cf72fe8
-  zh: b7f2b546b8639f43
+  en: 5b7fbbe1c55997e8
+  zh: d62d9118fd8df2f4
 /deepseek-ai-dsh-session-telemetry/use-this-package/the-sharing-disclosure:
   en: 5c325a8aaadf17c7
   zh: 5c493d2333f82b28
@@ -36,8 +36,8 @@
   en: cad1e9d195916553
   zh: 2192f3ce5e2196bd
 /deepseek-ai-dsh-session-telemetry/understand-the-implementation/design-concept:
-  en: 3bac6e75e9e442eb
-  zh: 88062e9d93a782eb
+  en: 56c449be11e6bac1
+  zh: 6b62969e93313c3e
 /deepseek-ai-dsh-session-telemetry/understand-the-implementation/source-map:
   en: 5dc345ec3dda38b8
   zh: 189d673734a2c20e

package/README.md

@@ -39,6 +39,8 @@ A backend implements three members: `emit(record)` must be a non-blocking enqueu
 
 Capture runs in one of two modes. `live` capture follows session events as they are appended, replays already-live sessions at mount time, and records lifecycle markers; `on-demand` capture reads the canonical session log only when the backend requests a prefix through `captureSession(session, throughSeq?)`. Coordinator options select whether stored history is included. Every canonical session event maps to one ledger record in order. An `assistant/message` or `assistant/attempt` record carries its complete embedded compact stream, including failed and retried output. Each ledger record also carries `session.id`, `session.format_version`, the numeric event identity, optional header facts, and a pre-mapped severity (`error` for `tool/result.isError`, `turn/end` error reasons, and `agent-error`; `info` otherwise).
 
+Ledger records carry `sourceEvent` with the owning Session id and a copied event envelope excluding `data`. The redaction waterfall receives `body` as the only payload copy. Backends can reconstruct a complete exported event from the envelope and redacted body without bypassing redaction.
+
 ### The sharing disclosure
 
 <a id="the-sharing-disclosure"></a>
@@ -63,7 +65,7 @@ This section explains the capture design; the observable behavior is fully cover
 
 ### Design concept
 
-The seam is built on one boundary: the harness's aspect ends at `emit()`. Complete event capture, redaction, and the handoff cursor live here; batching, retry, queueing, and loss policy are the reporting SDK's, deliberately not modelled or wrapped. The design and rejected alternatives are pinned in the [revival Agent Note](../../../.agents/notes/implemented/feature/2026-07-23-session-telemetry-otel-revival.md).
+The capture package owns complete event capture, redaction, and handoff cursors. Redaction rules must preserve `sourceEvent` for OTel upload; returning a fresh record without it withholds the event with a diagnostic. Its cloned envelope excludes `data`, which is carried only in `body`. The OTel backend owns byte/count scheduling and uses SDK transport/retries. The [revival Agent Note](../../../.agents/notes/implemented/feature/2026-07-23-session-telemetry-otel-revival.md) owns capture and redaction rationale.
 
 ### Source map
 

package/README.zh.md

@@ -39,6 +39,8 @@ kind: "package-library"
 
 捕获以两种模式之一运行。`live` 捕获在追加时跟随会话事件、在挂载时回放已存活会话并记录生命周期标记；`on-demand` 捕获只在后端通过 `captureSession(session, throughSeq?)` 请求前缀时读取权威会话日志。协调器选项决定是否包含存储历史。每条权威会话事件都按顺序映射为一条 ledger 记录。`assistant/message` 或 `assistant/attempt` 记录会携带完整的嵌入式紧凑流，包括失败和重试输出。每条 ledger 记录还携带 `session.id`、`session.format_version`、数值型事件标识、可选 header 事实与预先映射的严重级别（`tool/result.isError`、`turn/end` 的错误原因与 `agent-error` 映射为 `error`；其余为 `info`）。
 
+ledger 记录携带 `sourceEvent`，其中包含所属 Session id 和不含 `data` 的事件信封副本。脱敏 waterfall 接收的 `body` 是唯一的载荷副本。后端可从信封和脱敏后的 body 重建完整导出事件，而不绕过脱敏。
+
 ### 共享披露
 
 <a id="the-sharing-disclosure"></a>
@@ -63,7 +65,7 @@ kind: "package-library"
 
 ### 设计理念
 
-seam 建立在一个边界之上：harness 的职责止于 `emit()`。完整事件捕获、脱敏与 handoff 游标都在这里；批处理、重试、排队与丢失策略属于上报 SDK，本包有意不建模也不包装。设计与被否决的替代方案见[复活 Agent Note](../../../.agents/notes/implemented/feature/2026-07-23-session-telemetry-otel-revival.zh.md)。
+捕获包负责完整事件捕获、脱敏和交接游标。脱敏规则必须保留 `sourceEvent` 才能通过 OTel 上传；返回不含它的新记录会阻止该事件上传并产生诊断。复制的 envelope 不含 `data`，数据仅由 `body` 携带。OTel 后端负责字节/条数调度并使用 SDK 传输和重试。[恢复遥测决策记录](../../../.agents/notes/implemented/feature/2026-07-23-session-telemetry-otel-revival.zh.md) 说明捕获和脱敏依据。
 
 ### 源码地图
 

package/lib/index.js

@@ -134,13 +134,18 @@ var SessionTelemetryCoordinator = class {
 	}
 	/** Copy, redact, and hand one canonical event to the backend. */
 	captureEvent(session, event) {
+		const { data, ...envelope } = event;
 		this.deliver(session, {
 			record: this.redact({
+				sourceEvent: {
+					sessionId: session.id,
+					envelope: structuredClone(envelope)
+				},
 				channel: "ledger",
 				time: event.time,
 				severity: severityOf(event),
 				attributes: identityOf(session, event),
-				body: structuredClone(event.data)
+				body: structuredClone(data)
 			}),
 			seq: event.seq
 		});
@@ -253,7 +258,7 @@ function identityOf(session, event) {
 * forwarding), live versus on-demand canonical-log capture, and the HMR
 * cursor. Everything downstream of
 * {@link SessionTelemetryBackend.emit} — batching, retry, queueing, and loss policy — is the
-* reporting SDK's territory and is deliberately not modelled here. The
+* backend's responsibility and is deliberately not modelled here. The
 * design and its trade-offs are pinned in
 * .agents/notes/implemented/feature/2026-07-23-session-telemetry-otel-revival.md.
 *

package/lib/types/index.d.ts

@@ -7,13 +7,14 @@
  * forwarding), live versus on-demand canonical-log capture, and the HMR
  * cursor. Everything downstream of
  * {@link SessionTelemetryBackend.emit} — batching, retry, queueing, and loss policy — is the
- * reporting SDK's territory and is deliberately not modelled here. The
+ * backend's responsibility and is deliberately not modelled here. The
  * design and its trade-offs are pinned in
  * .agents/notes/implemented/feature/2026-07-23-session-telemetry-otel-revival.md.
  *
  * @module @deepseek-ai/dsh-session-telemetry
  */
 import { Context, Service } from '@deepseek-ai/cordis';
+import type { SessionEvent, SessionId } from '@deepseek-ai/dsh-session';
 declare module '@deepseek-ai/cordis' {
     interface Context {
         sessionTelemetry: SessionTelemetryBackend;
@@ -57,6 +58,11 @@ export type SessionTelemetrySeverity = 'info' | 'warn' | 'error';
  * identity so they can never be mistaken for ledger rows.
  */
 export interface SessionTelemetryRecord {
+    /** Canonical envelope without data; body carries the separately redacted payload. Absent for operational records. */
+    sourceEvent?: {
+        sessionId: SessionId;
+        envelope: Omit<SessionEvent, 'data'>;
+    };
     /** Ledger (session-log mirror) or ops (operational signal) channel; backends keep the two under separate instrumentation scopes. */
     channel: 'ledger' | 'ops';
     /** Unix epoch milliseconds — the source event's append time for ledger records, the emission time for ops records. */

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@deepseek-ai/dsh-session-telemetry",
   "description": "SessionTelemetryBackend seam for the DeepSeek Harness: session-event capture, projection, redaction, and handoff to a reporting backend",
-  "version": "0.1.7-rc.2",
+  "version": "0.2.0-rc.1",
   "publishConfig": {
     "access": "public"
   },
@@ -27,13 +27,13 @@
   ],
   "license": "MIT",
   "peerDependencies": {
-    "@deepseek-ai/dsh-session": "0.1.7-rc.2",
+    "@deepseek-ai/dsh-session": "0.2.0-rc.1",
     "@deepseek-ai/cordis": "~4.0.4",
-    "@deepseek-ai/dsh-agent": "0.1.7-rc.2"
+    "@deepseek-ai/dsh-agent": "0.2.0-rc.1"
   },
   "devDependencies": {
-    "@deepseek-ai/dsh-agent": "0.1.7-rc.2",
-    "@deepseek-ai/cordis": "~4.0.4",
-    "@deepseek-ai/dsh-session": "0.1.7-rc.2"
+    "@deepseek-ai/dsh-agent": "0.2.0-rc.1",
+    "@deepseek-ai/dsh-session": "0.2.0-rc.1",
+    "@deepseek-ai/cordis": "~4.0.4"
   }
 }