[cbhandsun]

本次将已实现的上下文恢复合入主线，供用户在 Windows 以脚本启动并保留托盘管理器自用。默认仍使用客户端原生压缩，精确恢复可选；主入口、生产代码及依赖锁与已构建并交付的 1a5ae1c 候选相同。

安全与持久约束保持：认证、私有恢复后独立公开生成、精确版本 ACK、SQLite FULL/DELETE、开库失败拒绝静默回退，以及已有记录的原到期时间。公开 release.yml 签名要求不变。旧失败证据保留，不启动新 24 小时验收，不消耗真实模型额度。

用户于 2026-10-29 明确选择：先受控自用，五秒恢复性能后续优化，暂不作为本轮合并前置。原五秒测试、期限和失败记录均不修改，不把失败标为通过。00feb44 的两次 coverage 仍为 failure：真实 Chat long-persistent 请求分别 5002ms / 5009ms 超时；不能解释为准备超时。有效 24 小时及真实 provider 使用尚未验收。

最近修复仅针对验收夹具：

• 文件/目录身份以 BigInt 保留完整精度，避免 Number 截断误判。
• 回收 COMMIT 前崩溃夹具将初始建库和两次保存的准备阶段与原五秒 sweep 阶段分开；保留原数据、退出 37、COMMIT marker 和同目录重开断言。等待 child close 后才清理。
• 最新局部验证：16 pass、2 项原有 Windows 平台 skip，Lint、格式、CI/模块治理通过。aaddfec 的 Windows 四个 unit 分片、node-quality、Rust、integration 均 success；已读取四份完整单测日志，新准备/五秒 sweep/进程退出回滚与重开回归实际通过，未见 not ok。push Verify 40854174517 与 PR Verify 40854183904 均完整 8/8 success；已读取两份完整 coverage 日志，未见 not ok 或非零失败计数。独立正式链 40854174909 现已完整 12/12 success，source 与十份业务完整日志均已核对；先前固定 1a5 的安装/迁移/回滚与合成客户端资格只覆盖其已记载范围。

Windows 旧 E 盘目录 local master 有本地修改，现有托盘实例仍保留；更新必须保留配置、数据、目录身份与冻结失败目录，不整根改名、不覆盖本地工作。合并不代表已切换运行实例，也不代表 Codex 真实模型验收完成。

[chatgpt-codex-connector]

Codex Review Summary

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

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-29T10:13:31.839540Z	aaddfec	Draft marked ready

ℹ️ 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

https-proxy/lib/proxy/handlers/upstream-terminal-frame.js

Lines 111 to 115 in aaddfec

	const hit = scanLine(line);
	if (hit) {
	settled = true;
	matched = hit;
	if (typeof onTerminal === 'function') onTerminal(hit);

Wait for the complete SSE frame before closing the stream

If a TCP chunk ends after the terminal data: line's first newline and the blank-line delimiter arrives in the next chunk, this immediately invokes onTerminal. Both callers in core-request-handler.js then end the client response and destroy the upstream, dropping the delimiter. The forwarded terminal event is therefore incomplete, so clients that dispatch SSE events only on a blank line never receive response.completed or [DONE] and can report an incomplete response despite successful generation. This is reproducible with a terminal frame split between its two trailing newlines; defer completion until the entire SSE event has been forwarded.

ℹ️ 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".