Repository navigation
Jevia 0.1.8
Jevia 0.1.8
CLI/core 0.1.8 fixes real-harness recording gaps, improves capture diagnostics,
and hardens storage and recovery. The separately versioned Node SDK remains
at 0.1.3 and works with this CLI release.
Harness recording
- Enable automatic Claude Code capture from live-tested 2.1.212 within major 2.
- Report actual event coverage and counts instead of calling process-only
metadata a successful native recording. - Add preview-first
jevia harness review codex(--launchopens the native
hook browser) andjevia harness health codex --require-events. - Allow bounded cold-start time for hooks and version probes; align child PWD
with the selected project and preserve OpenCode's explicit--puremode. - Record deduplicated OpenCode tool-failure facts without storing error text
or inferring that the overall task failed.
Storage, recovery, and performance
- Reject FIFO and other special history inputs without waiting for writers.
- Bound streamed JSONL lines and encoded output to 8 MiB, rejecting oversized
records without truncation or partial replacement. - Bound Jev routing response bodies to 1 MiB, including streamed responses.
- Stream guided database setup and batch recording-cleanup history lookups;
skip unnecessary rescans while preserving per-file safety checks. - Recover larger recording directories with bounded rotating replay; contain
version-probe process trees and validate SQL history-index definitions. - Avoid repeated history scans during cache-lock waits, then refresh routing
evidence after waiting.
Compatibility and known limits
Record schema 6, SQL schema 1, configuration, and public Rust core API remain
unchanged from 0.1.7. Recording/history reuse stay automatic; feedback and extra
verification remain optional. Rust 1.92 and Node.js 20 remain the minimums.
Existing JSONL lines over 8 MiB now require explicit inspection and reduction;
they are never silently skipped or truncated. Back up history before maintenance.
Native activity is not proof of task correctness or complete model attribution.
Codex still requires the user's normal hook-trust review. Real-provider capture
was observed for Claude, Codex, and OpenCode; the successful Codex live test used
an explicitly approved one-run trust bypass, not the ordinary persisted-trust
flow. Production Jevia does not inject that bypass. Unsupported harnesses retain
process-level recording. health --require-events inspects saved history, not a
fresh launch or the correctness of a solution.
Post-publication verification
The exact crates.io CLI was installed into an isolated directory and passed
version/help, initialization, empty-history, cache, storage-health, and missing-key
doctor checks. SDK JSONL/SQLite integrations passed against that installed binary.
A live Claude run through the published CLI recorded five real session/turn/tool
events with zero discarded inputs; harness health --require-events passed.
Its outcome remained unknown, with no manual feedback or additional verification.
Install
cargo install jevia --version 0.1.8 --lockedThe npm SDK remains available with npm install jevia@0.1.3; it does not bundle
or automatically install the CLI.
Release binaries include SHA-256 checksums, an SPDX SBOM, and signed GitHub
build/SBOM attestations. The default web installer advances separately after
the macOS, Linux, and Windows installer/attestation smoke tests pass.