From 81927e4e520010f204139ddc6950514e886eab20 Mon Sep 17 00:00:00 2001 From: Codex Date: Sun, 12 Jul 2026 17:47:19 +0200 Subject: [PATCH] =?UTF-8?q?docs:=20=E7=99=BB=E8=AE=B0=E5=B7=A5=E5=85=B7?= =?UTF-8?q?=E4=B8=8E=20trace=20=E8=B0=83=E6=9F=A5=E4=BB=BB=E5=8A=A1?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- docs/MDTODO/cli-output-progressive-disclosure.md | 4 ++++ docs/MDTODO/observability-trace-reliability.md | 4 ++++ 2 files changed, 8 insertions(+) diff --git a/docs/MDTODO/cli-output-progressive-disclosure.md b/docs/MDTODO/cli-output-progressive-disclosure.md index c0f5ee5b..6ddaa62d 100644 --- a/docs/MDTODO/cli-output-progressive-disclosure.md +++ b/docs/MDTODO/cli-output-progressive-disclosure.md @@ -102,3 +102,7 @@ ### R5.3 补 text/JSON/YAML 同构测试与真实 cancel dry-run 复验，确认 Next 可直接执行且 reason hash 相同；提交独立 PR，完成任务后将详细报告写入[任务报告](./details/cli-output-progressive-disclosure/R5.3_Task_Report.md)。 + +## R6 + +解决 [UniDesk #1850](https://github.com/pikasTech/unidesk/issues/1850)：统一 trans 规范入口、host/workspace/k3s 的 cwd 与 scoped help，补齐验证成功非空摘要，并为 PR 自动交付及 Code Agent 跨服务诊断提供只读聚合视图；必须分层展示 durable authority 与 projection warning，禁止新增手工 trigger/sync/refresh、提高 stdout 阈值或用版本/commit 契约漂移阻塞业务。由独立子代理在 .worktree/tooling-usability、fix/tooling-usability 分支调查、实现、针对性验证并提交 PR，不自行合并，完成任务后将详细报告写入[任务报告](./details/cli-output-progressive-disclosure/R6_Task_Report.md)。 diff --git a/docs/MDTODO/observability-trace-reliability.md b/docs/MDTODO/observability-trace-reliability.md index e04bd969..19d70d46 100644 --- a/docs/MDTODO/observability-trace-reliability.md +++ b/docs/MDTODO/observability-trace-reliability.md @@ -18,3 +18,7 @@ ### R1.3 依赖 R1.2，用固定 warm-session trace 验证重复诊断不改变原业务 trace 的 terminal/instrumentation 判定，诊断 trace 仍完整可查；补跨服务合同和端到端验收，确认实时、刷新回放及纯 Kafka + SSE 事件顺序均无变化，完成任务后将详细报告写入[任务报告](./details/observability-trace-reliability/R1.3_Task_Report.md)。 + +## R2 + +调查第二轮业务 trace `trc_9352107b5e8a4125` / session `ses_d4473d6c-4d7a-4612-a102-254977698bc2` 的文件编辑、`apply_patch` 与 tool event 可见性：先解析对应 OTel trace/run/command，再对照 codex stdio notification、AgentRun durable events、`agentrun.event.v1`、`hwlab.event.v1` 和 HWLAB trace/read model，并使用受控的集群内或应用侧 CLI 执行 Kafka replay 校对，判定事件是源头未产生、AgentRun 映射遗漏、Kafka 转换丢失还是 HWLAB 投影丢失；不得手写 Kafka API、不得用重放追加产品 topic event、不得把投影滞后改写成业务失败，完成任务后将详细报告写入[任务报告](./details/observability-trace-reliability/R2_Task_Report.md)。