fix: colibri 0.12.0 build — stale pi_binary refs + Cargo.lock sync #156

Merged

clawdie merged 1 commit from fix-0.12-build-and-lock into main

2026-06-24 00:36:00 +02:00

clawdie commented

2026-06-23 17:29:46 +02:00

Owner

Why

colibri main (0.12.0) does not compile. The harness-neutral rename (c3e9118: pi_binary → agent_binary) left two stale references in autospawn_agent_if_configured:

error[E0425]: cannot find value `pi_binary` — crates/colibri-daemon/src/socket.rs:449
error[E0425]: cannot find value `pi_binary` — crates/colibri-daemon/src/socket.rs:493

Separately, Cargo.lock still pinned every workspace member at 0.11.0 while the manifests are 0.12.0, so --locked builds (used for release staging) refused the tree.

What

Rename the two remaining pi_binary → agent_binary.
Refresh Cargo.lock to 0.12.0 for all members.

Test (Linux, rustc 1.95.0)

cargo build --workspace — clean.
cargo test --workspace — ~230 tests, 0 failures.
cargo metadata --locked — back in sync.

This unblocks any 0.12.0 build/stage (FreeBSD or Linux). Note: this fixes the compile; the OOTB autospawn default (COLIBRI_AUTOSPAWN_BINARY=zot + --mode json while the spawner still uses stdin(Stdio::null())) is a separate runtime issue tracked next.

🤖 Generated with Claude Code

## Why colibri `main` (0.12.0) does not compile. The harness-neutral rename (`c3e9118`: `pi_binary → agent_binary`) left two stale references in `autospawn_agent_if_configured`: ``` error[E0425]: cannot find value `pi_binary` — crates/colibri-daemon/src/socket.rs:449 error[E0425]: cannot find value `pi_binary` — crates/colibri-daemon/src/socket.rs:493 ``` Separately, `Cargo.lock` still pinned every workspace member at `0.11.0` while the manifests are `0.12.0`, so `--locked` builds (used for release staging) refused the tree. ## What - Rename the two remaining `pi_binary` → `agent_binary`. - Refresh `Cargo.lock` to `0.12.0` for all members. ## Test (Linux, rustc 1.95.0) - `cargo build --workspace` — clean. - `cargo test --workspace` — **~230 tests, 0 failures**. - `cargo metadata --locked` — back in sync. This unblocks any 0.12.0 build/stage (FreeBSD or Linux). Note: this fixes the *compile*; the OOTB autospawn default (`COLIBRI_AUTOSPAWN_BINARY=zot` + `--mode json` while the spawner still uses `stdin(Stdio::null())`) is a separate runtime issue tracked next. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

clawdie added 1 commit 2026-06-23 17:29:48 +02:00

fix: colibri 0.12.0 build — stale pi_binary refs + Cargo.lock sync

CI / rust (pull_request) Has been cancelled

Details

CI / markdown (pull_request) Has been cancelled

Details

CI / port (pull_request) Has been cancelled

Details

CI / agent-jail-pkgs (pull_request) Has been cancelled

Details

a9d0aed89e

The harness-neutral rename (COLIBRI_AUTOSPAWN_PI → COLIBRI_AUTOSPAWN,
pi_binary → agent_binary) left two references to the old pi_binary name in
autospawn_agent_if_configured, so colibri-daemon failed to compile:

  error[E0425]: cannot find value `pi_binary` — socket.rs:449, 493

Rename both to agent_binary. Also refresh Cargo.lock: workspace members were
still pinned 0.11.0 while the manifests are 0.12.0, so --locked builds (used
for release staging) refused the tree.

Verified: full workspace builds clean and the entire test suite passes
(~230 tests, 0 failures); cargo metadata --locked is back in sync.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>