[jinghero]

摘要

• uv 有时已经运行成功并退出，Runtime 才来为它设置退出时的清理措施。Windows 拒绝了这一步，最后把一次成功运行报成了启动失败。现在先设置好，再让 uv 运行。
• 取消或关闭时，uv 和它启动的其他程序仍会一起结束。关闭过程中如果出错，会保留具体原因，方便排查。
• 补齐启动 uv 过程中收到取消的情况，不再把取消误报成启动失败。没有取消时，真正的启动错误仍照常报告。

验证

当前提交 369dffd，Windows amd64 / Go 1.26.11。

• 在真实 Windows 上安排“uv 先结束，再设置清理”的顺序，旧代码复现误报，新代码通过。实际 uv 0.12.3 和 0.13.7 都做了前后对照，成功时的输出和退出码保持正确。
• 取消时误报失败的审查意见 已在实际执行器复现：取消和等待超时原来被报为失败，修改后都正确报告为取消；未取消的真实错误仍报失败。三个场景都实际调用 Windows 的进程操作，并确认进程已结束、没有开始业务工作，原始和关闭过程的错误均保留。
• 新增取消及未取消检查各重复 100 轮通过；完整 uv 包、共享进程启动及命令行取消检查通过。格式、静态检查、构建通过。代码规范和任务要求分别独立复查，两边均未发现新问题。
• 本机完整测试仍有已在旧代码复现的环境问题，以及临时目录偶发清理失败。缺少 C 编译器，race 检查未运行；没有把这些算作通过。完整命令和结果见 T5.18 验收文档。

还没确认的事

这证明了 uv 存在上述问题，但用户现场只记录了“进程隔离失败”，还不能确定就是同一个原因。开机、休眠时为什么收不到 Runtime 的第一条消息，也仍需现场复测。

没有修改版本号或发布设置。

[chatgpt-codex-connector]

Codex Review Summary: ✅ Completed

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-11-12T12:07:35.081735Z	369dffd	Manual request

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 1ef8ac3ce0

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[jinghero]

@codex review

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. Bravo.

Reviewed commit: 369dffd44c

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".