xcb v0.20.12

Codex completed-turn failures now identify which protocol invariant failed, so unattended tasks can be diagnosed without relaxing their completion checks.

Changes

• Separate a provider-reported turn error from unfinished items in the fixed, sanitized diagnostic. Unresolved tool calls still fail first; no provider payload or item content is exposed. This is diagnostic only, not a fix for the underlying failure; inspect fresh failures after installation before changing completion handling.
• Refresh the xcb site and package description with control-plane messaging and the cited owner post.

Install

Install the native xcb binary from this release. The installer downloads the archive for your platform, checks it against its .sha256 file, and installs ~/.local/bin/xcb:

git clone --depth 1 --branch v0.20.12 https://github.com/hraness/xcb.git xcb
cd xcb && XCB_VERSION=0.20.12 ./scripts/install-native.sh

On Windows x86_64, this installs xcb.exe from the release's .zip into %LOCALAPPDATA%\Programs\xcb\bin. It is not code-signed, and Claude Code and Codex run only in the Linux build inside WSL2:

$env:XCB_VERSION = '0.20.12'; irm https://raw.githubusercontent.com/hraness/xcb/v0.20.12/scripts/install.ps1 | iex

Install the TypeScript SDK and xcb-compat CLI from the release tarball:

npm install https://github.com/hraness/xcb/releases/download/v0.20.12/hraness-xcb-0.20.12.tgz

Verify

• Checksums: SHA256SUMS lists the SHA-256 of hraness-xcb-0.20.12.tgz, and each xcb-0.20.12-<platform>.tar.gz and xcb-0.20.12-windows-x86_64.zip has its own .sha256 file.
• Source commit: b2e7266f8f1626c17d6890d7ac346217bfc8cee2
• Build provenance: gh attestation verify xcb-0.20.12-<platform>.tar.gz -R hraness/xcb. The publishing guide describes how each file is built and checked.