Researcher: ROADMAP hot path still has superseded ReDiffuse preflight instruction

[DeliciousBuding]

Owner: Researcher

问题

Research/ROADMAP.md 的热路径里同时存在两个互相冲突的“当前执行”口径：2026-05-25 的最新修正说不释放 GPU、active_gpu_question = none；但紧接着的 2026-05-23 下一阶段综合仍写着“立即执行 ReDiffuse STL-10 preflight”并把 active_gpu_question 设为 ReDiffuse。

证据

• AGENTS.md:29-33 的 Current Operating State 明确写：latest update 是 2026-05-25 feature-packet boundary correction，active_gpu_question = none; next_gpu_candidate = none。
• ROADMAP.md:21-24 在 2026-05-25 Stable Diffusion ReDiffuse source-label 边界审计中写：不请求数据、不下载权重、不重跑 pipeline，当前 slots 全部 none。
• ROADMAP.md:45-49 在 2026-05-25 Feature-Packet 消费边界修正中再次写：不从本次边界修正释放 GPU 训练或新下载，当前 slots 全部 none。
• 但 ROADMAP.md:85-98 的 2026-05-23 下一阶段综合仍保留：立即执行：下载 ReDiffuse 补充材料，提取 STL-10 划分，开始 CPU 侧预检，并写 active_gpu_question = ReDiffuse DDPM/STL-10 preflight。

影响

Fresh-session intake 会从 ROADMAP.md 读取路线。如果 Agent 或 Researcher 只看到前 100 行内的 2026-05-23 决策块，可能误以为应该继续 ReDiffuse STL-10 preflight 或释放后续 GPU；这与 2026-05-25 的 no-GPU / candidate-only 修正相冲突。这个问题会直接影响下一轮研究资源调度和交接判断。

建议修复

• 把 ROADMAP.md:85-98 的 2026-05-23 “立即执行 / active_gpu_question = ReDiffuse...” 改成明确的历史状态或 superseded 状态。
• 保留有价值的扫描结论和候选排序，但删除或替换当前式命令语气，避免和 2026-05-25 最新 slots 冲突。
• 如果 ReDiffuse split-manifest 仍是长期候选，应写成“candidate watch / no selected GPU job”，而不是当前执行项。

验收标准

• Research/ROADMAP.md 热路径中只有一个当前 active_gpu_question 口径，且与 AGENTS.md 一致。
• 2026-05-23 段落不会再指示立即执行已被 2026-05-25 修正取消的 ReDiffuse preflight。
• python -X utf8 scripts/run_pr_checks.py 仍通过。

[DeliciousBuding]

综合审计报告（COO follow-up）

结论：这是 Research 热路径交接问题，不是普通文档措辞。ROADMAP.md 前 100 行内同时保留了 2026-05-25 的 no-GPU / none slots 最新口径，以及 2026-05-23 的“立即执行 ReDiffuse STL-10 preflight”旧口径，会误导 fresh-session Researcher。

严重性：Medium

为什么真实有意义：

• Research agent intake 明确要求从 ROADMAP/AGENTS 重新锚定，不从聊天记忆开始。
• 同一热路径内的冲突会直接影响 GPU/CPU 资源调度和是否继续 ReDiffuse 预检。
• 这违反根级“发现引用不存在/过期入口时直接改到当前真实入口”的知识卫生规则。

证据链：

• AGENTS.md:29-33：Current Operating State 写 latest update 是 2026-05-25 feature-packet boundary correction，active_gpu_question = none; next_gpu_candidate = none。
• ROADMAP.md:21-24：2026-05-25 ReDiffuse source-label audit 写不请求数据、不下载权重、不重跑 pipeline，slots 全部 none。
• ROADMAP.md:45-49：2026-05-25 feature-packet boundary correction 再次写不释放 GPU 训练或新下载，slots 全部 none。
• ROADMAP.md:85-98：2026-05-23 下一阶段综合仍写“立即执行：下载 ReDiffuse 补充材料，提取 STL-10 划分，开始 CPU 侧预检”，并设置 active_gpu_question = ReDiffuse DDPM/STL-10 preflight。

应修复的产品/研究边界：

• 保留 2026-05-23 的扫描价值，但把执行语气改成历史/superseded 状态。
• 前 100 行只能保留一个当前 active_gpu_question 口径，并与 AGENTS.md 一致。
• ReDiffuse 可继续作为 candidate watch，但不能在 hot path 中表现为当前 selected work。

验收测试建议：

• Research/ROADMAP.md hot path 中没有当前式 ReDiffuse preflight 指令。
• active_gpu_question 当前口径与 AGENTS.md 一致。
• python -X utf8 scripts/run_pr_checks.py 通过。

执行分派：

• 已派 gpt-5.5 xhigh worker 到独立 worktree：D:\Code\DiffAudit\.worktrees\research-roadmap-hotpath
• 分支：fix/research-roadmap-hotpath
• 该 worker 处理 Researcher: ROADMAP hot path still has superseded ReDiffuse preflight instruction #292，修复完成后会在本 issue 更新验证结果。

[DeliciousBuding]

修复进展

分支：fix/research-roadmap-hotpath
Worktree：D:\Code\DiffAudit\.worktrees\research-roadmap-hotpath
提交：66b54f0 docs: mark superseded ReDiffuse preflight as historical
远端分支：https://github.com/DeliciousBuding/DiffAudit-Research/tree/fix/research-roadmap-hotpath

改动摘要

• 只修改 ROADMAP.md。
• 将 2026-05-23 下一阶段研究综合 的 决策 段改为 历史决策状态（已被 2026-05-25 修正覆盖）。
• 保留 2026-05-23 的公开面扫描结论、ReDiffuse split manifest 候选价值和候选排序。
• 删除当前式 立即执行：下载 ReDiffuse 补充材料，提取 STL-10 划分，开始 CPU 侧预检 指令。
• 删除冲突的 active_gpu_question = ReDiffuse DDPM/STL-10 preflight，改为引用 2026-05-25 Feature-Packet 消费边界修正段的最新 none slots。
• 同时把 2026-05-25 Stable Diffusion ReDiffuse source-label 审计段从重复声明 slots 改为“不改变 2026-05-25 feature-packet 修正后的 none slots”，确保前 100 行只有一个显式当前 active_gpu_question 口径。

验证

• python -X utf8 scripts/run_pr_checks.py：通过。
  • Public surface guard passed.
  • Markdown link check passed.
  • unified-attack-defense-table.json validation OK.
  • recon-product-evidence-card.json check OK.
  • compileall 和 CLI parser smoke 未报错。
• 额外检查前 100 行：只剩 2026-05-25 Feature-Packet 消费边界修正段显式声明 active_gpu_question = none / next_gpu_candidate = none / CPU sidecar = none selected after feature-packet boundary correction。
• 额外检索旧冲突串：ReDiffuse DDPM/STL-10 preflight、下载 ReDiffuse 补充材料、开始 CPU 侧预检 已不再出现在 ROADMAP.md 的当前式执行指令中。

未完成项

• 未关闭 issue，等待 review / merge。
• 未创建 PR；当前只有已推送分支，可按需要从分支发 PR。

[DeliciousBuding]

PR is open for Researcher review: #297

The PR includes this issue in its close keywords and carries the verification evidence in the PR body.

[DeliciousBuding]

Status update: #297 has been superseded by #306.

Do not use #297 as the merge candidate anymore: it is DIRTY against current main and predates later LeakyCLIP / ReDiffuse score-norm / feature-packet consumer-verdict facts.

The replacement path is #306, which has been rebased on current main, verified locally, and now only adds the historical ReDiffuse note needed here. Keeping this issue open until #306 merges.

[DeliciousBuding]

Latest replacement-PR status: #306 has been rebased again on current origin/main at 6912fbc after #311 landed.

The replacement PR still only adds the four-line historical ReDiffuse note to ROADMAP.md; it does not drop the 2026-05-25 feature-packet consumer verdict or the newer H2 order-control facts. Validation passed via docs checks, admitted bundle check, PR checks, and git diff --check.

Keep this issue open until #306 merges.

[DeliciousBuding]

Latest replacement-PR status: #306 has been rebased again on current origin/main at 67e6ab6 after the H2 order-control scout result landed.

The replacement PR still only adds the four-line historical ReDiffuse note to ROADMAP.md; it does not drop the 2026-05-25 feature-packet consumer verdict or the newer H2 order-control facts. Validation passed via docs checks, admitted bundle check, PR checks, and git diff --check.

Keep this issue open until #306 merges.

[DeliciousBuding]

Researcher report - 2026-05-25

This issue is covered by PR #306. The branch now sits on current main base 84dff57 with head 356b07e.

Issue status:

• The superseded ReDiffuse preflight wording is retained only as historical context.
• The active execution posture remains the newer 2026-05-25 bounded scout plus score-norm weak closure.
• No experiment artifact, admitted table, Platform contract, or Runtime contract changes are included.

Verification:

• python -X utf8 scripts/run_docs_checks.py
• python -X utf8 scripts/export_admitted_evidence_bundle.py --check
• python -X utf8 scripts/run_pr_checks.py
• git diff --check
• GitHub unit-tests succeeded.

Current blocker: wait for PR #306 review/merge.

[DeliciousBuding]

Researcher report - 2026-05-25

This issue remains covered by PR #306. The branch has been rebased and verified on current main base 938ceb2 with head 465a71c.

Current status:

• GitHub unit-tests succeeded.
• Merge state is BLOCKED by normal review/protection only.
• The active execution posture remains the newer 2026-05-25 bounded scout plus score-norm weak closure.
• The older 2026-05-23 ReDiffuse STL-10 wording is retained only as historical context.
• No experiment artifact, admitted table, Platform contract, or Runtime contract changed.

Validation:

• python -X utf8 scripts/run_docs_checks.py
• python -X utf8 scripts/export_admitted_evidence_bundle.py --check
• python -X utf8 scripts/run_pr_checks.py
• git diff --check

Next action: wait for PR #306 review/merge.