From b049574bccfa4a159885c2c56a65b05f9b6fd45b Mon Sep 17 00:00:00 2001
From: Codex <codex@local>
Date: Mon, 13 Jul 2026 10:23:55 +0200
Subject: [PATCH] docs: track sentinel hourly dispatch regression

---
 docs/MDTODO/web-sentinel-runtime-reliability.md | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/docs/MDTODO/web-sentinel-runtime-reliability.md b/docs/MDTODO/web-sentinel-runtime-reliability.md
index 0a1a2632..680d62b9 100644
--- a/docs/MDTODO/web-sentinel-runtime-reliability.md
+++ b/docs/MDTODO/web-sentinel-runtime-reliability.md
@@ -24,6 +24,9 @@ PR 合并后只等待自动发布链，使用受控 Web sentinel 原入口产生
 
 核对 [#1861](https://github.com/pikasTech/unidesk/issues/1861) 的小时级实际探测 cadence 与 10 分钟 scheduler heartbeat/扫描间隔；若只读报告语义误导则纠正字段和文档，若 owning YAML 未生效则修正渲染，验收 CronJob 与报告明确区分二者，完成任务后将详细报告写入[任务报告](./details/web-sentinel-runtime-reliability/R1.4_Task_Report.md)。
 
+#### R1.4.1 [in_progress]
+
+解决 [UniDesk #1919](https://github.com/pikasTech/unidesk/issues/1919)：纠正此前‘实际已为小时级’的误判，沿 owning YAML、renderer、CronJob/Deployment、quick verify 与 AgentRun/HWLAB Session provenance 定位并消除约 10 分钟误派发；保留 10 分钟心跳/扫描时不得创建业务 Session，自动交付后覆盖完整小时窗口验收唯一小时级派发源，不新增第二 scheduler、补洞、合同、租约、安全机制或围栏，完成任务后将详细报告写入[任务报告](./details/web-sentinel-runtime-reliability/R1.4.1_Task_Report.md)。
 ## R2 [in_progress]
 
 推进 [UniDesk #1868](https://github.com/pikasTech/unidesk/issues/1868)：按当前多 runner、全局查询与 Dashboard 复杂度重构 Monitor 平台，评估并实施分散 SQLite 到 NC01 YAML-first Host PostgreSQL 的统一迁移；P0 先冻结架构、数据模型和切换边界，再实现、自动发布和原入口验收，不以迁移掩盖 [#1861](https://github.com/pikasTech/unidesk/issues/1861)，不保留永久双写或第二权威，完成任务后将详细报告写入[任务报告](./details/web-sentinel-runtime-reliability/R2_Task_Report.md)。