docs(agent-notes): frame telemetry default-off as public beta transition

Problem now explains that DSH is entering public beta and default-off is
the appropriate stance for that phase — consistent with internal testing
having default-on for diagnostics. Update Consequences to match.

.agents/notes/implemented/feature/2026-08-10-telemetry-default-off.i18n.yaml

@@ -2,5 +2,5 @@
 # side as of the last confirmed-consistent state. Both languages carry equal authority;
 # after editing either side, bring the other along and re-record with:
 #   pnpm run verify-translation-pairing --write .agents/notes/implemented/feature/2026-08-10-telemetry-default-off.md
-2026-08-10-telemetry-default-off.md: e4a075fb6eee606057ffe1b953af525169d9cb80
-2026-08-10-telemetry-default-off.zh.md: 4f3b27e76fcd895269b0934f3623ce355e377913
+2026-08-10-telemetry-default-off.md: fce146cf1c075630ca498de3e511d96fe1a328a8
+2026-08-10-telemetry-default-off.zh.md: 84746d7e8661467e7ea49a940bef8b894cd3f3fc

.agents/notes/implemented/feature/2026-08-10-telemetry-default-off.md

@@ -6,7 +6,7 @@ English | [中文](2026-08-10-telemetry-default-off.zh.md)
 
 ## Problem
 
-DeepSeek Harness has two outbound telemetry feeds. The session OTel backend could export complete session content, tool data, prompts, and workspace paths when its mode was omitted, while the dsh-sdk launcher feed reported by default. A fresh installation therefore permitted outbound reporting without a positive deployment choice.
+DeepSeek Harness is entering its public beta phase. During internal testing, telemetry was enabled by default — the session OTel backend and the dsh-sdk launcher both reported without a positive deployment choice — to help diagnose reported issues. For public beta, outbound reporting must require an explicit opt-in from the deployment.
 
 ## Decision
 
@@ -28,4 +28,4 @@ The versioned Web welcome notice states that Session Log upload is off by defaul
 
 ## Consequences
 
-Fresh profiles and projects make no telemetry network request. Internal deployments select one mode for both feeds: `FEEDBACK_ONLY` permits only feedback-triggered Session Log sharing, while `FULL` also enables launcher reporting. The existing hard opt-out remains effective, and uploading modes retain their endpoint validation, redaction responsibility, batching, and shutdown behavior.
+All public beta profiles and projects make no telemetry network request by default — a break from the internal-testing default of reporting when configured. Internal deployments that still need reporting select one mode for both feeds: `FEEDBACK_ONLY` permits only feedback-triggered Session Log sharing, while `FULL` also enables launcher reporting. The existing hard opt-out remains effective, and uploading modes retain their endpoint validation, redaction responsibility, batching, and shutdown behavior.

.agents/notes/implemented/feature/2026-08-10-telemetry-default-off.zh.md

@@ -6,7 +6,7 @@ Status: implemented
 
 ## 问题
 
-DeepSeek Harness 有两路出站遥测数据流。会话 OTel 后端在省略 `mode` 时可能导出完整会话内容、工具数据、提示词和工作区路径，而 dsh-sdk 启动器数据流默认上报。因此，全新安装无需部署方明确选择便允许向外上报。
+DeepSeek Harness 正在进入公测阶段。在内测阶段，遥测默认开启——会话 OTel 后端和 dsh-sdk 启动器均无需部署方明确选择即可上报——以帮助诊断上报的问题。进入公测后，出站上报必须由部署方显式启用。
 
 ## 决策
 
@@ -28,4 +28,4 @@ dsh-sdk 启动器读取同一变量，不解析 `cordis.yml`，也不启动 Cord
 
 ## 后果
 
-全新 profile 和项目不发出任何遥测网络请求。内部部署为两路数据流选择一个模式：`FEEDBACK_ONLY` 只允许由反馈触发的 Session Log 共享，`FULL` 还会启用启动器上报。现有硬性退出继续生效，上传模式也保留 endpoint 校验、脱敏责任、批处理和关闭行为。
+所有公测 profile 和项目默认不发出任何遥测网络请求——与内测阶段配置后即上报的默认行为不同。仍需上报的内部部署为两路数据流选择一个模式：`FEEDBACK_ONLY` 只允许由反馈触发的 Session Log 共享，`FULL` 还会启用启动器上报。现有硬性退出继续生效，上传模式也保留 endpoint 校验、脱敏责任、批处理和关闭行为。