@deepseek-ai/dsh-session-telemetry 0.2.0-rc.1 → 0.2.1-alpha.1

package/README.i18n.yaml

@@ -36,8 +36,8 @@
   en: cad1e9d195916553
   zh: 2192f3ce5e2196bd
 /deepseek-ai-dsh-session-telemetry/understand-the-implementation/design-concept:
-  en: 56c449be11e6bac1
-  zh: 6b62969e93313c3e
+  en: 2eeafa2e73202e92
+  zh: 003b796d53af7577
 /deepseek-ai-dsh-session-telemetry/understand-the-implementation/source-map:
   en: 5dc345ec3dda38b8
   zh: 189d673734a2c20e
@@ -48,8 +48,8 @@
   en: c213358e20f27173
   zh: 84a5501335891f0b
 /deepseek-ai-dsh-session-telemetry/further-exploration:
-  en: 12c383ffe3448557
-  zh: e78cbffe565ce340
+  en: de4295bc2bbfb076
+  zh: efaacf0686d460a6
 /deepseek-ai-dsh-session-telemetry/model-experience:
   en: 6a6b429828997572
   zh: bde61df9dab8f840
@@ -60,5 +60,5 @@
   en: dc950b1f59a057ec
   zh: 6f353d426b03abb1
 /deepseek-ai-dsh-session-telemetry/known-limitations-and-deferred-work/dev-note:
-  en: e10a3d2c84d710a6
-  zh: 910927bba4d34a85
+  en: e67f633dc6fe7773
+  zh: 3bb0c20c93f16f98

package/README.md

@@ -65,7 +65,7 @@ This section explains the capture design; the observable behavior is fully cover
 
 ### Design concept
 
-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.
+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 [historical revival Agent Note](../../../.agents/notes/archived/feature/2026-07-23-session-telemetry-otel-revival.md) records capture and redaction rationale.
 
 ### Source map
 
@@ -93,7 +93,7 @@ Read these pages when the seam contract is not enough. They move from the shippe
 
 - [OpenTelemetry telemetry backend](../session-telemetry-otel/README.md) — the shipped backend deployments load, with mode and exporter configuration.
 - [Session telemetry subsystem](../../../docs/subsystems/session-telemetry.md) — the capability split and type declarations.
-- [Session telemetry revival decision](../../../.agents/notes/implemented/feature/2026-07-23-session-telemetry-otel-revival.md) — rationale, trade-offs, and rejected alternatives.
+- [historical Session telemetry revival decision](../../../.agents/notes/archived/feature/2026-07-23-session-telemetry-otel-revival.md) — rationale, trade-offs, and rejected alternatives.
 - [Session package map](../README.md) — adjacent persistence, projection, title, and telemetry packages.
 
 -----
@@ -127,5 +127,3 @@ These limits define the delivery and data-protection guarantees a deployment get
 None.
 
 </details>
-
-**Runtime invariant:** No companion is published. The package's whole output is the backend handoff — a synchronous `emit()` call outside every authoritative event stream — and its capture side never appends session events, so no event/data relation exists for an independent companion to observe.

package/README.zh.md

@@ -65,7 +65,7 @@ ledger 记录携带 `sourceEvent`，其中包含所属 Session id 和不含 `dat
 
 ### 设计理念
 
-捕获包负责完整事件捕获、脱敏和交接游标。脱敏规则必须保留 `sourceEvent` 才能通过 OTel 上传；返回不含它的新记录会阻止该事件上传并产生诊断。复制的 envelope 不含 `data`，数据仅由 `body` 携带。OTel 后端负责字节/条数调度并使用 SDK 传输和重试。[恢复遥测决策记录](../../../.agents/notes/implemented/feature/2026-07-23-session-telemetry-otel-revival.zh.md) 说明捕获和脱敏依据。
+捕获包负责完整事件捕获、脱敏和交接游标。脱敏规则必须保留 `sourceEvent` 才能通过 OTel 上传；返回不含它的新记录会阻止该事件上传并产生诊断。复制的 envelope 不含 `data`，数据仅由 `body` 携带。OTel 后端负责字节/条数调度并使用 SDK 传输和重试。[历史恢复遥测决策记录](../../../.agents/notes/archived/feature/2026-07-23-session-telemetry-otel-revival.md) 说明捕获和脱敏依据。
 
 ### 源码地图
 
@@ -93,7 +93,7 @@ ledger 记录携带 `sourceEvent`，其中包含所属 Session id 和不含 `dat
 
 - [OpenTelemetry 遥测后端](../session-telemetry-otel/README.zh.md)——部署方加载的随附后端，含模式与导出器配置。
 - [会话遥测子系统](../../../docs/subsystems/session-telemetry.zh.md)——能力拆分与类型声明。
-- [会话遥测复活决策](../../../.agents/notes/implemented/feature/2026-07-23-session-telemetry-otel-revival.zh.md)——理由、权衡与被否决的替代方案。
+- [历史会话遥测复活决策](../../../.agents/notes/archived/feature/2026-07-23-session-telemetry-otel-revival.md)——理由、权衡与被否决的替代方案。
 - [会话包映射](../README.zh.md)——相邻的持久化、投影、标题与遥测包。
 
 -----
@@ -127,5 +127,3 @@ ledger 记录携带 `sourceEvent`，其中包含所属 Session id 和不含 `dat
 无。
 
 </details>
-
-**运行时不变式：** 不发布伴生入口。本包的全部输出都是后端交接，即在所有权威事件流之外同步调用 `emit()`；捕获侧不追加会话事件，因此不存在可供独立 companion 观察的事件与数据关系。

package/lib/index.js

@@ -258,9 +258,9 @@ 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
-* 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.
+* backend's responsibility and is deliberately not modelled here. Capture and
+* backend responsibilities are documented in the
+* [Session telemetry reference](../README.md#understand-the-implementation).
 *
 * @module @deepseek-ai/dsh-session-telemetry
 */

package/lib/types/index.d.ts

@@ -7,9 +7,9 @@
  * 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
- * 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.
+ * backend's responsibility and is deliberately not modelled here. Capture and
+ * backend responsibilities are documented in the
+ * [Session telemetry reference](../README.md#understand-the-implementation).
  *
  * @module @deepseek-ai/dsh-session-telemetry
  */

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.2.0-rc.1",
+  "version": "0.2.1-alpha.1",
   "publishConfig": {
     "access": "public"
   },
@@ -27,13 +27,13 @@
   ],
   "license": "MIT",
   "peerDependencies": {
-    "@deepseek-ai/dsh-session": "0.2.0-rc.1",
-    "@deepseek-ai/cordis": "~4.0.4",
-    "@deepseek-ai/dsh-agent": "0.2.0-rc.1"
+    "@deepseek-ai/dsh-session": "0.2.1-alpha.1",
+    "@deepseek-ai/cordis": "~4.0.5-alpha.1",
+    "@deepseek-ai/dsh-agent": "0.2.1-alpha.1"
   },
   "devDependencies": {
-    "@deepseek-ai/dsh-agent": "0.2.0-rc.1",
-    "@deepseek-ai/dsh-session": "0.2.0-rc.1",
-    "@deepseek-ai/cordis": "~4.0.4"
+    "@deepseek-ai/dsh-agent": "0.2.1-alpha.1",
+    "@deepseek-ai/cordis": "~4.0.5-alpha.1",
+    "@deepseek-ai/dsh-session": "0.2.1-alpha.1"
   }
 }