v8.7.2

English

Fixes and reliability

• Fix repeated resume <session-id> arguments in Codex recovery commands. CCB now recognizes its generated hook-trust flag while rewriting continuations, preserving the session and launch permission settings. This addresses a locally reproduced crash signature reported in [#356].
• Recover abandoned OMP editor sockets when Bun reports ENOENT instead of ECONNREFUSED. Socket ownership and identity checks remain enforced.
• Recognize right-padding after Codex's empty composer placeholder instead of treating it as an unsent draft.
• Show cached input-guard waiting reasons in ccb queue --detail, including elapsed draft wait and whether clearing was attempted. Unknown input remains blocked; the fixed 180-second wait and FIFO ordering are unchanged.

Upgrade and verification

• Update CCB, then stop and start the affected project when its work can safely be interrupted so the new daemon code and provider extensions are loaded. Keep .ccb and provider session history; do not edit runtime.json or clear conversations as an upgrade step. Inspect outstanding jobs before restarting; do not blindly resubmit accepted requests.
• Real Linux Codex-to-Codex tests covered fresh sessions, retained-session relaunch, and queued delivery after automatic crash recovery. Recovery retains its existing 90-second stability window.
• OMP crash recovery and real 180-second draft/FIFO delivery were verified. Normal OMP model responses could not be validated because the configured service returned an insufficient-balance error.
• Android version metadata follows the existing coordinated release pipeline; this release adds no mobile UI feature.

Known limitations

• [#356] also reports non-delivery while the target pane appears healthy. The fixes above do not establish that every such case has the same cause. The issue remains open for reporter verification with queue, runtime and composer evidence.
• Final composer inspection and terminal input are not atomic. Unknown observations are never treated as permission to clear or send.

中文

修复与稳定性

• 修复 Codex 恢复命令重复追加 resume <session-id>。CCB 在重写会话继续命令时识别自身生成的 hook-trust 参数，保留会话及启动权限设置，修复了本地复现的 [#356] 所述崩溃特征。
• 修复 Bun 对废弃 OMP 编辑器 socket 返回 ENOENT 而非 ECONNREFUSED 时无法恢复的问题，继续执行 socket 所有权及身份检查。
• 修复 Codex 空输入提示右侧填充空格被误认为未发送草稿的问题。
• ccb queue --detail 显示缓存的输入保护等待原因、草稿等待时长及是否尝试清空。未知输入继续阻止发送，固定 180 秒等待及 FIFO 顺序不变。

升级与验证

• 更新 CCB 后，在受影响项目的工作可安全中断时停止并重新启动项目，使新 daemon 代码和 provider 扩展生效。保留 .ccb 和 provider 会话历史；升级不需要编辑 runtime.json 或清空对话。重启前检查未完成任务，不要盲目重新提交已接受的请求。
• Linux 真实 Codex→Codex 测试覆盖新会话、保留会话重启、崩溃自动恢复后的排队投递；恢复仍保留现有 90 秒稳定观察期。
• 已验证 OMP 崩溃恢复及真实 180 秒草稿等待/FIFO 投递。由于配置的服务返回余额不足，未验证正常 OMP 模型回复。
• Android 版本元数据沿用现有同步发布流程；本版没有新增手机界面功能。

已知限制

• [#356] 还报告了目标 pane 看似健康时不投递的情况。上述修复不能证明这些情况全部同因；issue 保持开放，等待报告者提供队列、运行状态及输入框证据复测。
• 最后一次输入框检查与终端输入不是原子操作。无法判断输入框时，不会据此清空或发送。