[Root Cause] root-cause-board (auto-maintained, do not close manually) | [根因] root-cause-board（自动维护，勿手动关闭） #6379

Activity

1. ranxianglei

   added

   root-cause-batch

   on Nov 12, 2026
2. ranxianglei

   changed the title [-][根因] root-cause-board（自动维护，勿手动关闭）[/-] [+][Root Cause] root-cause-board (auto-maintained, do not close manually) | [根因] root-cause-board（自动维护，勿手动关闭）[/+] on Nov 12, 2026
3. ranxianglei

   closed this as not plannedon Nov 12, 2026
4. ranxianglei commented on Nov 12, 2026

   

   ranxianglei

   on Nov 12, 2026

   OwnerAuthor

   More actions

   🤖 Powered by ework · qwen3.8-27b

   [bot] 🏷

   (ai: vllm-qwen/qwen3.8-27b)

   查重:#6379 不是「某 bug 的重复 PR」,而是分类管道产物——一个「板的板」(meta-board)。它的正文汇聚的是 4 个子根因板(#6266 panel-ui / #6267 storage / #6268 kernel-compression / #6269 conflict-watch),不是代码缺陷;每个子板的「根因」字段本身就是 "auto-maintained root-cause aggregation board for the X family"。

   结论:不开捆绑 PR。 以下均基于当前 live 状态逐一核实(非旧评论记忆):

   1. owner 已判定这 4 个子板是重复、要关闭重建。 4 个子板各自的最新评论(2026-11-12 10:26Z,owner @ranxianglei)逐字:「本单为分类板重复创建,按 owner 指令全部关闭并统一重建(2026-11-12)。新聚合单将使用稳定 token 去重,不再按标题匹配。」 —— 即这 4 个子板(以及汇聚它们的 [Root Cause] root-cause-board (auto-maintained, do not close manually) | [根因] root-cause-board（自动维护，勿手动关闭） #6379)是待关闭/重建的分类产物,不是待修代码。

   2. 真正的修复早已以 5 个独立 open PR 交付(经 GitHub API 逐一核实,均 open / 未合):

      • panel-ui [bug] UNRECOGNIZED PATHS flags non-POST requests to known endpoints (/responses, /) as "not a known protocol", and the c | [bug] UNRECOGNIZED PATHS 把非 POST 请求打到已知端点（/responses、/）判成 "not a known protocol"，且计数永不清零——4 次探活常驻面板 6 天 #5763 → PR [PR] fix(server): gate UNRECOGNIZED PATHS counter to model-calls + window it 24h (#5763) #5770「gate UNRECOGNIZED PATHS counter to model-calls + window it 24h」
      • storage storage: notice-store (#5548) pre-hydration receipts block the one-time legacy→kv migration #5761+[storage] Persist a schema reader floor so an older build refuses a store it cannot share (rolling upgrades / rollbacks) #5788 → PR [PR] fix(storage): persist a schema reader floor + unblock the notice-store migration #6347「persist a schema reader floor + unblock the notice-store migration」
      • kernel-compression T2 nudge repeatedly recommends block merges rejected by turn-integrity gate #5776 → PR [PR] fix: screen tier merge nudges against compression eligibility #5777「screen tier merge nudges against compression eligibility」(外部贡献者)
      • kernel-compression UNCOVERED HISTORY advertises a protected-boundary turn fragment that compress always rejects | [Bug] UNCOVERED HISTORY 报出的 run 是保护区边界的 turn 片段，compress 必然拒绝，且整批回滚把相邻的合法区间一起废掉 #5780 → PR [PR] fix(#5780): screen UNCOVERED HISTORY runs through the apply-side foldability judgment #5785「screen UNCOVERED HISTORY runs through the apply-side foldability judgment」
      • conflict-watch Compression conflict banner (bili v0.1.208, node v26.8.2, darwin-arm64) #5767+Compression conflict banner (bili v0.1.212, node v24.19.0, win32-x64) #5786 → PR [PR] fix(conflict-watch): stop native compaction landings from lighting the conflict banner (#5767, #5786) #6355「stop native compaction landings from lighting the conflict banner」

      (另有 [bug] acp_status 结果以整份报告内联进助手消息：text-trigger 车道每轮在客户端会话里留一块 ~40 行面板（上行每轮已剥离，成本全在可见面） #5762 / Request two capabilities: compression block "decommissioning" and summary "external rewrite" | 请求两个能力：压缩块「退役」与摘要「外部重写」 #5766 / feat(design): preserve in-progress implementation state across folds (coding sessions lose just-written details → re-read + self-contradiction loops) #5771 等仍处「需决策」,各有自己的线程,不属本批可修范围。)

   3. 捆绑成一个 PR 违反「一 issue 一 scope」。 这 5 个 PR 横跨 4 个不同失败域(server 观测面 / storage 持久层 / kernel 压缩 / conflict-watch 归因),无单一根因;AGENTS.md §4「One issue = one scope」与 §7.4 auto-merge 门禁「Single-module scoped fix」都禁止把 4 个机制塞进一个 PR。cherry-pick 合并还会与这 5 个在途 PR 撞车。

   编号说明:镜像 [PR] 行号与 GitHub PR 号是两套独立序列(同一 PR 两边号不同,例如 storage reader floor 这个 PR 在 GitHub 是 #6347、在镜像 [PR] 列表里却排在 #6348)。本回复引用的 PR 号全部经 GitHub API 核实,是 GitHub 号。

   待 owner 处置(我无法代劳):4 个子板 + 本 meta-board #6379 在镜像里仍为 open;按「agent 一律不关」政策我不执行关闭,等 owner 按 10:26Z 指令关闭 / 用稳定 token 重建聚合。

   ---

   八问

   1. 是什么问题:[Root Cause] root-cause-board (auto-maintained, do not close manually) | [根因] root-cause-board（自动维护，勿手动关闭） #6379 是「板的板」——汇聚 4 个子根因板的 meta-board,本身不是代码缺陷;每个子板的「根因」字段就是「分类板」(管道产物)。
   2. 什么原因导致的:根因归类板按标题匹配聚合,把 4 个不同失败域的子板又聚成一个 meta-board;owner 已判定这批是重复、改用稳定 token 去重重建。
   3. 影响范围与严重程度:无运行时影响(纯分类/调度产物);严重度 = 调度噪音(重复派发、可能诱导 agent 开违规的捆绑 PR)。
   4. 怎么修复的:不开捆绑 PR;真正的修复已在 5 个独立 open PR([PR] fix(server): gate UNRECOGNIZED PATHS counter to model-calls + window it 24h (#5763) #5770/[PR] fix(storage): persist a schema reader floor + unblock the notice-store migration #6347/[PR] fix: screen tier merge nudges against compression eligibility #5777/[PR] fix(#5780): screen UNCOVERED HISTORY runs through the apply-side foldability judgment #5785/[PR] fix(conflict-watch): stop native compaction landings from lighting the conflict banner (#5767, #5786) #6355),各归各机制;本批板等 owner 关闭/重建。
   5. 是否有回归问题:不涉及(未改任何代码)。
   6. 是否破坏缓存:不涉及。
   7. 是否改了设计方向:不涉及。
   8. 是否引入了新的配置:不涉及。

   收工判定:本线程不开 PR、不改代码——#6379 是分类产物而非代码缺陷,owner 已定 4 个子板关闭重建,实际修复已收敛在 5 个独立在途 PR。待 owner 关闭/重建这批板。