Repository navigation
v0.5.1 is the release where a fresh install gets working tools.
Tool kits
A kit is a directory of tool packages with a verlet.kit.toml manifest naming the tools it exposes. verlet kit install <kit-dir> builds and proves each member, publishes the operations content-addressed, and records the install; the daemon picks installed kits up at the next startup, with no manifest editing.
This release ships the first kit: the pi kit, five file tools (read, write, edit, find, grep) compiled to wasm and exposed to models under those plain names. Build it from the repo with scripts/build-pi-kit-dist.sh.
The chat setup window now offers kits directly: an "Install tools" row, plus a one-time offer right after you configure your first model. One Enter installs the recommended kit; the receipt lands in the transcript.
Dependencies
bashkit 0.14.3 to 0.17.1, tuika 0.8.0 to 0.11.1, turso 0.7.0-pre.19 to 0.8.0-pre.7. The bashkit jump changes shell behavior: the yaml builtin is gone (its replacement needs a feature this build does not enable), bzip2-family commands arrive, heavy scripts can fail earlier under bashkit's internal resource budgets, and malformed $(...) fails closed.
The bump also hardened Verlet's own shell boundary: non-UTF-8 pipeline output can no longer expand past the 64 MiB retention ceiling unflagged, truncation reported by nested tool and proxy outputs survives into the final result, and shell grammar keywords can no longer be claimed as tool names.
Fixes
The Linux verification lane no longer kills its own container (child process groups are terminated with a direct killpg syscall), Cargo lane locks are container-keyed, and socket-release assertions absorb close-notify latency.
Full details in CHANGELOG.md.