CCB v8.3.0

Released: 2026-07-22

English

Managed Kimi and Claude requests now stay bound to their exact native turns,
preventing stale or queued output from being accepted as the current reply.
Qoder follows its real CLI session, resume, update, storage, and completion
contracts. This includes the integration completed in PR #270.
Managed Claude, Gemini, Droid, Qwen, and Copilot homes inherit supported
extensions and plugins only when CCB can prove ownership, preserving
user-managed assets and cleanup boundaries.

Active work accepts bounded follow-up steering on the exact job, while
project view, trace, doctor, heartbeat, sidebar, and Mobile expose correlated
execution phases and orphaned-inbound diagnostics.
Cancelled callback chains now record a terminal continuation result instead
of leaving child callbacks or delivery state active indefinitely.
Restart recovery reconciles callback continuation jobs with their durable
message attempts and inbound events, so an interrupted handoff cannot leave
a continuation permanently queued.
npm-managed installations delegate upgrades to npm, keeping the installed
package and its metadata atomic. This resolves Issue #268.
Marker-only CCB worktrees are removed only after proving that no user payload
is present; ambiguous or legacy worktrees are retained for recovery. This
resolves Issue #271.
Mobile chat and terminal views remain in the selected project workspace and
preserve agent and window navigation.
The sidebar settings button now works reliably on WSL and macOS: desktop
opener state is retained in project panes, host-native openers are preferred,
failed open attempts fall through, and the UI shows a manual URL when no
opener succeeds.

CCB 8.3.0 requires no manual data migration. Existing installations can use
their normal update path; npm-managed installations can run
npm install -g @seemseam/ccb@8.3.0.
Linux, macOS, npm, and Android versions, download metadata, and checksums are
synchronized to this release.

托管的 Kimi 与 Claude 请求现在会严格绑定到对应的原生轮次，避免把旧输出或
尚未激活的排队输出误判为当前回复。
Qoder 现已按照真实 CLI 的会话、恢复、更新、存储与完成协议运行，其中包括
PR #270 完成的集成修复。
托管的 Claude、Gemini、Droid、Qwen 与 Copilot 主目录仅在 CCB 能证明资产
归属时继承受支持的扩展和插件，从而保护用户自行管理的资产与清理边界。

运行中的任务现在可对准确作业进行有边界的后续引导；项目视图、trace、
doctor、heartbeat、侧边栏与 Mobile 同步展示关联后的执行阶段，并提供孤立
入站任务诊断。
被取消的回调链现在会记录终止态的延续结果，不再让子回调或投递状态无限期
保持活动。
重启恢复现在会核对回调延续作业及其持久化消息 attempt 与入站事件，避免交接
中断后延续作业永久滞留在队列中。
由 npm 管理的安装会把升级交还给 npm，确保已安装包与元数据原子更新；该项
修复解决了 Issue #268。
只有在确认不存在用户数据后，CCB 才会删除仅含标记的工作树；存在歧义或来自
旧版本的工作树会保留以便恢复；该项修复解决了 Issue #271。
Mobile 的聊天与终端视图会留在当前选定的项目工作区，并保留 agent 与窗口
导航状态。
WSL 与 macOS 上的侧边栏设置按钮现在可以可靠工作：项目 pane 会保留桌面
打开器状态，优先调用宿主系统原生打开器，失败时继续尝试后备方式，并在所有
打开方式均失败时显示可手动访问的地址。

CCB 8.3.0 不需要手工迁移数据。现有安装可继续使用原有更新方式；由 npm
管理的安装可执行 npm install -g @seemseam/ccb@8.3.0。
Linux、macOS、npm 与 Android 的版本、下载元数据和校验和均已同步到本次
发布。