Fixed
- Windows client bundles verify their pinned dependencies after ZIP
extraction. The manifest now binds npm symlinks to both their target and
resolved bytes, accepting the two observed regular-file materializations
while still rejecting tampering. The bundle test models both shapes instead
of assuming Linux symlink semantics. - Windows live launchers match the documented client installation. The
Codex launcher resolves the native binary vendored by the npm package when
codex.exeis absent fromPATH. Claude overlay cleanup no longer exits
early, traverses junctions, or leaks directories created during a session;
the runbook now names the PowerShell-Modeand-ProfileFileinterface. - A graceful Claude adapter shutdown records its disconnect before closing
the log. The terminal record includes the close code and reason and cannot
be mistaken for a reconnecting network drop. - Codex discovery no longer mistakes a transient in-memory thread for target
ambiguity.thread/loaded/listis process-wide, and Codex CLI 0.150.0 was
observed returning two loaded IDs on a clean TUI launch while only one had a
persisted rollout. The adapter now probes loaded IDs withthread/resume,
selects only when exactly one resumable candidate exists, and
still stays offline if more than one viable target remains. Expected
no-rollout JSON-RPC rejections no longer trigger a pointless App Server
reconnect. The fleet runbook also pins acceptance to measured Codex 0.149.x
until 0.150.0 passes the complete attended gate, and makes the separate MCP
bearer preflight and background adapter-log receipt explicit.
Image
docker pull ghcr.io/thek3nsai/ops-brain:v5.2.1
Multi-arch: linux/amd64, linux/arm64.