@lark-project/meegle 1.0.26 → 1.0.27

package/CHANGELOG.md

@@ -8,6 +8,12 @@ versioned section on each npm release.
 
 ## [Unreleased]
 
+## [v1.0.27] - 2026-10-19
+
+### Changed
+
+- Clarified that failed-command diagnostics can be associated with authenticated accounts, tenants and existing request logs for troubleshooting. The updated notice is shown once to existing users without changing their local collection setting. Disabling reporting clears pending local diagnostics but does not delete uploaded data or disable normal service request logging.
+
 ## [v1.0.26] - 2026-10-14
 
 ### Added

package/README.md

@@ -1032,7 +1032,11 @@ Dynamic discovery accepts nullable JSON Schema types such as `"type": ["string",
 
 ## Failed-command diagnostics
 
-Failed-command diagnostics are enabled by default. On first use, Meegle CLI writes a one-time notice to stderr and saves its record, including in CI, Agent and redirected invocations; stdout remains reserved for command results. After the notice is successfully written and saved, Meegle CLI collects sampled diagnostics for final root commands that fail. Successful commands are not collected in schema v1. Collection never includes command argument values, tokens, file paths, request or response bodies, or error messages.
+Failed-command diagnostics are enabled by default. On first use and when the notice is updated, Meegle CLI writes the current notice once to stderr and saves its record, including in CI, Agent and redirected invocations; stdout remains reserved for command results. After the notice is successfully written and saved, Meegle CLI collects sampled diagnostics for final root commands that fail. Successful commands are not collected in schema v1.
+
+Diagnostics include command and option names (without values), failure stages and error codes, client version and system information, timestamps, durations, and request correlation identifiers. Diagnostic events do not contain argument values, credentials, file paths, business content, request or response bodies, or raw error messages.
+
+Where authentication information is available, the server associates diagnostics with account and tenant identifiers. Diagnostics can be correlated with existing service request logs to identify the relevant account and target space for troubleshooting. Diagnostics are therefore not anonymous. Excluding argument values from diagnostic events does not mean that related information is absent from existing service request logs.
 
 The foreground command selects a diagnostic event and hands it to a detached maintenance process. That process queues the event without scanning historical events, then performs cleanup, policy refresh and upload when due. The foreground does not wait for queue/sequence locks, event writes or network delivery. Command return is not confirmation that its event has been queued. Policy is refreshed at most every 12 hours (with a 1-hour retry after an unhealthy refresh). Pending events are isolated by profile and host. Background cleanup removes expired events and the oldest excess events to meet the global limits of 7 days, 1,000 events and 5 MiB. Writes can temporarily exceed these limits until maintenance runs. While the current profile/host has queued events, subsequent commands can trigger global cleanup once a minute, independently of credentials and the one-hour upload retry interval. Recording a new failure during upload cooldown does not retry the network request. Policy refresh also triggers maintenance. Switching to an empty queue does not itself schedule cleanup of inactive profiles. No resident daemon runs after the CLI exits.
 
@@ -1050,6 +1054,8 @@ meegle telemetry enable
 meegle telemetry status   # defaults to {"enabled": true} or {"enabled": false}
 ```
 
+Running `meegle telemetry disable` stops future diagnostic reporting and clears the pending local queue. It does not delete uploaded diagnostics or disable normal server-side logging of service requests. The local queue's seven-day retention limit does not specify the retention period for server-side diagnostics or service logs.
+
 Explicit `enable` first writes and saves the current notice if it has not been recorded, then enables the local switch. Notice output or persistence failure returns an error without reporting successful enablement. `status` returns only whether collection is currently allowed, considering the local switch, disclosure record, environment override and locally stored policy snapshot for the current profile/host. It does not resolve credentials or refresh policy over the network, and supports `--format json|table|ndjson` (or `-o`). `enabled=true` does not confirm that any diagnostic has been uploaded.
 
 Set `MEEGLE_TELEMETRY=disabled` to disable it for the current environment and suppress automatic disclosure. Explicit `enable` can still complete disclosure and enable the local switch, but does not override the environment variable or remote policy restrictions. The CLI journey event is separate from MCP server telemetry; when available, a structured backend `logid` is included only as a correlation reference.

package/README.zh-CN.md

@@ -999,7 +999,11 @@ Policy 拒绝遵循显式结构化输出格式，并使用稳定错误码 `CLIEN
 
 ## 失败命令诊断
 
-Meegle CLI 默认开启失败命令诊断。首次运行时会向 stderr 输出一次性告知并保存记录，包括 CI、Agent 和输出重定向等非交互环境；stdout 保留给命令结果。告知成功输出并保存后，会按策略采集最终执行失败的根命令诊断；V1 不采集成功命令。采集内容不包含命令参数值、Token、文件路径、请求/响应 Body 或错误消息。
+Meegle CLI 默认开启失败命令诊断。首次运行及告知内容更新时，会向 stderr 输出一次当前版本的告知并保存记录，包括 CI、Agent 和输出重定向等非交互环境；stdout 保留给命令结果。告知成功输出并保存后，会按策略采集最终执行失败的根命令诊断；V1 不采集成功命令。
+
+诊断信息包括命令与选项名称（不含值）、失败阶段和错误码、客户端版本与系统信息、发生时间、耗时及请求关联标识。诊断事件不包含参数值、凭据、文件路径、业务正文、请求/响应 Body 或原始错误文本。
+
+服务端会根据可用的认证信息关联账号及租户标识，并可结合已有业务请求日志定位相关账号和目标空间，用于排查故障。因此，诊断信息并非匿名数据；诊断事件不包含参数值，不代表已有业务请求日志中没有相关信息。
 
 前台命令筛选诊断事件后，交给独立维护进程。后台不扫描历史事件即可完成单条入队，再按原有条件进行清理、策略刷新与上报。前台不等待队列锁、序号锁、事件写盘或网络投递；命令返回不代表事件已经入队。有效策略最多每 12 小时刷新一次；刷新不健康时每 1 小时重试。待上报事件按 profile + host 隔离，后台按 7 天、1000 条、5 MiB 的全局限制清理过期和最旧事件；维护运行前允许临时超限。当前 profile/host 有积压时，后续命令最多每分钟触发一次全局清理，不依赖凭证，也不受上报一小时重试间隔限制。上报冷却期间仍可记录新错误，但不会因此重试网络请求。策略到期也会触发维护；切到空队列本身不会触发其他 profile 的清理。CLI 退出后没有常驻守护进程。
 
@@ -1017,6 +1021,8 @@ meegle telemetry enable
 meegle telemetry status   # 默认输出 {"enabled": true} 或 {"enabled": false}
 ```
 
+执行 `meegle telemetry disable` 会关闭后续诊断上报，并清空本地待上传队列；不会删除已上传的诊断数据，也不会关闭正常业务请求的服务端日志记录。本地队列的 7 天保留上限不代表服务端诊断数据或业务日志的保存期限。
+
 显式执行 `enable` 时，如果尚未完成当前版本的告知，会先输出并保存告知，再开启本地开关；告知输出或保存失败时返回错误，不提示开启成功。`status` 仅返回当前是否允许采集，综合本地开关、告知记录、环境变量和当前 profile/host 的本地策略快照判断，不查询凭证或联网刷新策略；支持 `--format json|table|ndjson`（或 `-o`）。`enabled=true` 不代表某条诊断已经上传成功。
 
 设置 `MEEGLE_TELEMETRY=disabled` 可在当前环境关闭，并跳过自动告知；显式 `enable` 仍可完成告知和开启本地开关，但不会覆盖该环境变量或远端策略的限制。CLI 端到端事件与 MCP 服务端埋点彼此独立；存在后端 `logid` 时，只把它作为结构化关联字段。

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lark-project/meegle",
-  "version": "1.0.26",
+  "version": "1.0.27",
   "description": "Agent-First CLI for Meegle (Lark Project)",
   "license": "MIT",
   "homepage": "https://github.com/larksuite/meegle-cli#readme",