Release v0.2.0
Historical release notes. See v0.2.2 for the current release.
rupi v0.2.0 is the audited durability and recovery release, published on
2026-09-19. It packages the mainline after nine audit rounds and the Round 9
sign-off: no P0 or P1 findings remain from that cycle.
What changed since v0.1.0
Crash-safe sessions and recovery
- Session leases, legacy-store migration, checkpoint projections, and model-visible message reconstruction now recover conservatively across interruption.
- Externalized assistant/tool payloads restore through their durable references.
- Interrupted or decoded-but-unexecuted tool calls close their projection lifecycle;
uncertain mutating work remains
Unknownand is never blindly replayed. - Canonical trace, semantic session state, WAL intents, blobs, and checkpoint capsules remain separate and inspectable.
Bounded transports and cancellation
- Provider and MCP relays use bounded, cancellable request paths.
- DNS resolution uses one process-wide worker plus one queued job, so a wedged platform resolver cannot create unbounded detached threads.
- HTTP/MCP interruption fails closed and preserves exact request identity and parentage.
Safety and portability
- Filesystem confinement, symlink checks, output limits, redaction, cancellation, and Windows handle behavior received additional regression coverage through the audit cycle.
- The runtime preserves explicit failure, refusal, and
Unknownstates instead of turning missing evidence into a success or an observed failure.
Documentation and release metadata
- Workspace crates are versioned as
0.2.0. - The release provides an
x86_64-pc-windows-msvcbinary archive with a SHA-256 sidecar; other targets can use the Cargo source build. - Public guides now use the current configuration schema, CLI flags, event vocabulary, storage layout, MCP activation flow, and provenance rules.
- The release includes the Round 9 audit report and refreshed schema/compatibility references.
Verification
The release branch runs the repository checks required by CI and the release checklist:
cargo fmt --all --check
cargo check -p rupi-core --all-features
cargo clippy --workspace --all-targets -- -D warnings
cargo test --workspace
cargo doc --workspace --no-deps
mdbook build book
bash bench/startup.sh --json bench/results/startup-ci.json
Observed on the release host (Windows, 2026-09-19):
- Startup: cold median
120.68 ms(fresh-inode mode), warm median6.71 ms. - Keystrokes: worst measured case
35.83 us; rendering: worst case3.42 us. - Restore: 1,000 turns with checkpoints in
3.06 ms.
Benchmark numbers are host-dependent. The repository documents budgets and keeps the command output as the evidence rather than treating one machine's result as a promise.
Known boundaries
- Node/TypeScript extensions remain an explicit optional host and require Node 22.6+.
- MCP long-lived server push remains deferred; stdio and bounded Streamable HTTP POST activation are supported.
- Remote package/dependency installation, full custom Pi TUI widgets, telemetry, and automatic reconstructed-rationale production remain outside this release.
- Windows CI is supported by the workspace's portability tests, while the hosted CI matrix still runs on Linux, macOS, and Windows according to the workflow configuration.