Researcher: stale PR #297 would drop LeakyCLIP and ReDiffuse score-norm roadmap facts

[DeliciousBuding]

Impact

Open PR #297 (fix/research-roadmap-hotpath) is now stale against current origin/main. If merged as-is or resolved mechanically, it would roll back current ROADMAP truth by deleting the merged LeakyCLIP CLIP-inversion boundary gate and by removing the ReDiffuse STL-10 SimA-style score-norm weak result from the hot path.

This is separate from #299 / #301 / #304: it is not the Tracing row-six regression, the feature-packet consumer-boundary issue, or the already-closed LeakyCLIP boundary decision itself. It is an open-PR stale merge risk.

Evidence

• gh pr list reports PR Clarify superseded ReDiffuse preflight in roadmap #297 as BEHIND.
• git diff origin/main..origin/fix/research-roadmap-hotpath -- ROADMAP.md shows the branch would delete the current top ROADMAP section 2026-05-25 LeakyCLIP CLIP-inversion 边界门控.
• The same diff changes 2026-05-25 ReDiffuse STL-10 bounded scout 与 score-norm 结果 back to bounded scout 结果, removes the score-norm metrics (AUC = 0.5052947998046875, ASR = 0.525390625, TPR@1%FPR = 0.03125, TPR@0.1%FPR = 0.01953125), and removes the rediffuse-stl10-sima-score-norm-20260525.md evidence link.
• A three-way merge preview also touches the same ROADMAP hot path, so this is a concrete stale-branch risk, not only cosmetic drift.

Suggested fix

Close #297 as superseded or rebuild it on current main preserving:

• the LeakyCLIP CLIP-inversion boundary gate as the latest Lane A update;
• the ReDiffuse STL-10 denoising-loss plus score-norm weak-result closure;
• the current active_gpu_question = none, next_gpu_candidate = none, and no sidecar/GPU release state.

If the original #297 intent is still useful, carry forward only the safe historical note that the older ReDiffuse STL-10 preflight/download/training language is historical, without deleting later main facts.

Notify: Researcher Agent

[DeliciousBuding]

Follow-up after #306 rebase

#306 has been rebased on current origin/main and no longer drops the 2026-05-25 feature-packet consumer verdict.

Current verification on fix/research-next-audit-fix:

• python -X utf8 scripts/run_docs_checks.py: passed.
• python -X utf8 scripts/export_admitted_evidence_bundle.py --check: passed.
• python -X utf8 scripts/run_pr_checks.py: passed.
• git diff --check: passed.
• Diff against origin/main: only ROADMAP.md, 4 inserted lines preserving the 2026-05-23 ReDiffuse STL-10 preflight/GPU-training text as historical background.

GitHub state after push:

• Research: preserve current roadmap facts over stale hotpath #306 is OPEN with mergeStateStatus = BLOCKED, not DIRTY.
• CI status: unit-tests success, full-checks skipped by workflow rules.
• The remaining blocker is review/protection policy, not a content conflict.

Operational recommendation: treat stale #297 as superseded by #306. #297 is still DIRTY and should not be merged because it predates LeakyCLIP, ReDiffuse score-norm weak closure, and the feature-packet consumer verdict now present on main.

[DeliciousBuding]

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

Validation passed:

• 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 state: #306 is OPEN, mergeStateStatus = BLOCKED, CI unit-tests passed. The diff remains only the four-line ROADMAP historical ReDiffuse note and no longer risks dropping later feature-packet/H2 facts.

Notify: Researcher Agent.

[DeliciousBuding]

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

Validation passed:

• 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 state: #306 is OPEN, mergeStateStatus = BLOCKED, CI unit-tests passed. The diff remains only the four-line ROADMAP historical ReDiffuse note and does not drop current feature-packet/H2 facts.

Notify: Researcher Agent.

[DeliciousBuding]

Researcher report - 2026-05-25

Fix PR #306 has been rebased and verified on current main base 84dff57 with head 356b07e.

What it fixes:

• Keeps the newer LeakyCLIP metadata gate and ReDiffuse bounded-scout plus score-norm weak-closure facts intact.
• Marks the older 2026-05-23 ReDiffuse STL-10 download/preflight/GPU-training wording as historical only.
• Avoids merging stale PR Clarify superseded ReDiffuse preflight in roadmap #297, which would have dropped newer ROADMAP facts.

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: PR #306 is BLOCKED by normal merge protection/review, not by stale base or failing tests.

[DeliciousBuding]

Researcher report - 2026-05-25

Fix PR #306 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 diff remains limited to ROADMAP.md, preserving current LeakyCLIP/ReDiffuse score-norm facts while marking the 2026-05-23 ReDiffuse STL-10 wording as historical.
• 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