From 47a343b0ca663de9cf2d947d6704d468d4a84db1 Mon Sep 17 00:00:00 2001 From: Codex Date: Sat, 11 Jul 2026 23:03:59 +0200 Subject: [PATCH] =?UTF-8?q?docs:=20=E5=90=AF=E5=8A=A8=E4=B8=89=E9=A1=B9?= =?UTF-8?q?=E6=9E=B6=E6=9E=84=E4=BB=BB=E5=8A=A1?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- docs/MDTODO/github-gitea-durable-source-authority.md | 4 ++-- docs/MDTODO/observability-trace-reliability.md | 4 ++-- docs/MDTODO/pr-merge-driven-automatic-delivery.md | 4 ++-- 3 files changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/MDTODO/github-gitea-durable-source-authority.md b/docs/MDTODO/github-gitea-durable-source-authority.md index 39cea141..02e6a028 100644 --- a/docs/MDTODO/github-gitea-durable-source-authority.md +++ b/docs/MDTODO/github-gitea-durable-source-authority.md @@ -31,11 +31,11 @@ 依据 [UniDesk #1784](https://github.com/pikasTech/unidesk/issues/1784) 的只读审计，确认修复需要 owning YAML 到 managed mirror renderer/controller/automatic reconcile 的架构变更；按用户边界保持 issue open 并跳过，禁止人工 mirror、手工 CI/CD 补跑或 GitHub fallback，完成任务后将详细报告写入[任务报告](./details/github-gitea-durable-source-authority/R2.1_Task_Report.md)。 -## R3 +## R3 [in_progress] 解决 [UniDesk #1784](https://github.com/pikasTech/unidesk/issues/1784)：建立 owning YAML → managed repository/cache/ref 的单一持久源码 authority，让 AgentRun resource bundle 依赖自动物化、恢复和重试；禁止 direct GitHub fallback、人工 mirror 或第二 source authority，完成任务后将详细报告写入[任务报告](./details/github-gitea-durable-source-authority/R3_Task_Report.md)。 -### R3.1 +### R3.1 [in_progress] 冻结 [#1784](https://github.com/pikasTech/unidesk/issues/1784) 与 [AgentRun #294](https://github.com/pikasTech/agentrun/issues/294) 的 repositoryDependency 合同：明确 owning YAML schema、repository/ref owner、readiness、生命周期、失败分类和迁移边界；desired 只来自 YAML，不从运行面反解，完成任务后将详细报告写入[任务报告](./details/github-gitea-durable-source-authority/R3.1_Task_Report.md)。 diff --git a/docs/MDTODO/observability-trace-reliability.md b/docs/MDTODO/observability-trace-reliability.md index d8e78e88..55b532b0 100644 --- a/docs/MDTODO/observability-trace-reliability.md +++ b/docs/MDTODO/observability-trace-reliability.md @@ -3,11 +3,11 @@ 范围：长期跟踪跨服务 OTel trace context、业务 trace 与诊断 trace 隔离、Span Link、诊断重复性和 trace 证据稳定性。单个故障或 GitHub issue 作为 MDTODO ITEM 进入本文件，不为一次性 trace 或根因新建 MDTODO FILE。 -## R1 +## R1 [in_progress] 解决 [UniDesk #1801](https://github.com/pikasTech/unidesk/issues/1801)：隔离业务 trace 与 diagnostic trace，使诊断读取保持可观测但不再向被诊断业务 trace 补记 span；不得通过静默过滤隐藏真实 span，不改变已验收的纯 Kafka + SSE 实时/刷新链路，完成任务后将详细报告写入[任务报告](./details/observability-trace-reliability/R1_Task_Report.md)。 -### R1.1 +### R1.1 [in_progress] 冻结 [#1801](https://github.com/pikasTech/unidesk/issues/1801) 的 trace-context 合同：业务 trace 只承载原业务执行证据，diagnostic trace 使用独立 traceId，并通过 OTel Span Link 和明确关联字段引用目标 trace；定义跨 UniDesk/AgentRun 的 propagation、采样、错误和兼容边界，完成任务后将详细报告写入[任务报告](./details/observability-trace-reliability/R1.1_Task_Report.md)。 diff --git a/docs/MDTODO/pr-merge-driven-automatic-delivery.md b/docs/MDTODO/pr-merge-driven-automatic-delivery.md index dca02dc7..bbf7b900 100644 --- a/docs/MDTODO/pr-merge-driven-automatic-delivery.md +++ b/docs/MDTODO/pr-merge-driven-automatic-delivery.md @@ -44,11 +44,11 @@ 记录 [AgentRun PR #301](https://github.com/pikasTech/agentrun/pull/301) 自动 Pipeline Succeeded、GitOps result 与 Argo/runtime provenance 未收敛的证据；确认涉及自动 GitOps/provenance 架构后保持 [UniDesk #1802](https://github.com/pikasTech/unidesk/issues/1802) open 并跳过实现，完成任务后将详细报告写入[任务报告](./details/pr-merge-driven-automatic-delivery/R3.1_Task_Report.md)。 -## R4 +## R4 [in_progress] 解决 [UniDesk #1802](https://github.com/pikasTech/unidesk/issues/1802) 并对齐 [UniDesk #1769](https://github.com/pikasTech/unidesk/issues/1769)：建立 source commit → immutable snapshot → artifact digest → GitOps commit → Argo revision → runtime digest 的单一、不可伪造自动交付 provenance；GitHub PR merge 仍是唯一触发，禁止人工补交付，完成任务后将详细报告写入[任务报告](./details/pr-merge-driven-automatic-delivery/R4_Task_Report.md)。 -### R4.1 +### R4.1 [in_progress] 冻结 [#1802](https://github.com/pikasTech/unidesk/issues/1802) / [#1769](https://github.com/pikasTech/unidesk/issues/1769) 的交付合同：定义 admission-owned outer-event provenance、标准 terminal roles/results、父子运行归属、commit/digest 关联和 fail-closed 判定，明确 YAML owner 与 controller 职责，完成任务后将详细报告写入[任务报告](./details/pr-merge-driven-automatic-delivery/R4.1_Task_Report.md)。