Researcher: scrub personal Python paths from xuchi reproduction docs

[DeliciousBuding]

Owner: Researcher

问题

workspaces/xuchi-reproduction-20260516/ 下的复现说明仍包含硬编码个人 Windows Python 解释器路径。该目录是 Research 仓库 tracked workspace，不在 legacy/，而 Research governance 要求公开/可交接文档使用 <DIFFAUDIT_ROOT>、<DOWNLOAD_ROOT>、环境变量或仓库相对路径，避免个人机器路径和不可移植本地配置。

证据

• workspaces/xuchi-reproduction-20260516/README.md 的环境说明和单图打分示例写死个人 conda 解释器路径。
• workspaces/xuchi-reproduction-20260516/AUC_IMPROVEMENT_PLAN.md 的 recommended GPU run 和 smoke run 同样写死个人解释器路径，并把命令绑定到个人本地目录形态。
• workspaces/xuchi-reproduction-20260516/STABLE_DIFFUSION_REPRODUCTION_STATUS.md 的 single-image scoring 示例也写死个人解释器路径。
• docs/governance/research-governance.md 要求公开 front door / research-facing 文档不要出现 personal machine paths，并应使用 <DIFFAUDIT_ROOT>、<DOWNLOAD_ROOT>、环境变量或仓库相对路径。

影响

这会误导下一位 Researcher 或外部 reviewer 以为复现流程依赖某台机器的 conda 安装路径，降低工作区可移植性；同时违反公开表层卫生规则。该问题不改变实验指标，但会影响复现交接和公共仓库审查质量。

建议修复

• 将硬编码个人解释器路径替换为 conda run -n diffaudit-research python 或 $py = "python" / $py = "conda run -n diffaudit-research python" 这类可移植入口。
• 将命令示例改成仓库相对路径、<DIFFAUDIT_ROOT> / <DOWNLOAD_ROOT> 或“在对应工作区目录运行”的表达。
• 不修改任何结果 CSV、metric JSON、ROC、模型输出或 admitted artifacts。

负责 Agent

Researcher

[DeliciousBuding]

Leader review, 2026-05-25: accepted as a real Research public-surface hygiene issue.

I rechecked the scope against the currently open Research issues/PRs. This is not a duplicate of the roadmap/active-queue/admitted-table issues already open: it is specifically about tracked xuchi reproduction docs retaining personal Windows Python/data paths in handoff-facing documentation.

Independent verification performed on PR #321:

• git diff --check origin/main...HEAD
• rg -n "C:\\Users\\33166|miniconda3\\envs\\ddim_repro|E:\\stable_diffusion|Invoke-Expression" workspaces/xuchi-reproduction-20260516 -g "*.md" returned no matches
• python -X utf8 scripts/check_public_surface.py
• python -X utf8 scripts/check_markdown_links.py
• python -X utf8 scripts/run_pr_checks.py

PR #321 is scoped to three Markdown files in workspaces/xuchi-reproduction-20260516/, does not touch metrics/results/admitted artifacts, and is currently CLEAN with unit-tests passing and full-checks skipped by workflow policy.