Jevia v0.1.9

Jevia 0.1.9

This patch improves automatic recording reliability, routing context, and history memory usage.

• Protect literal native task text, including attach, serve, web, and leading-dash prompts.
• Keep signalled, timed-out, and unlaunched verifier outcomes unknown; optional checks and feedback stay optional.
• Include the selected harness's model candidates in routing, and bound each outgoing history window to 64 KiB without truncating saved history.
• Stream routing projections, stats, and JSONL maintenance. A local synthetic SQLite stats test reduced peak RSS from about 124 MiB to 48 MiB with identical output; results depend on workload and driver buffers.
• Preserve pending recording journals during archive, validate maintenance inputs, and keep SQL exports within restorable record limits.
• Expand actual native CLI contract tests: normal Codex hook review, cancellation, provider rejection, literal tasks, resume/model changes, OpenCode foreground subagents, and automatic history reuse.

Native tests use pinned CLIs with local model-response fixtures. They verify recording contracts, not live-model task-solving accuracy or all interactive/background workflows.

Install or upgrade

cargo install jevia --version 0.1.9 --locked

Platform binaries and SHA-256 checksums are attached to this release, along with an SPDX SBOM and GitHub build/SBOM attestations.

Compatibility

• CLI and Rust core: 0.1.9. Node SDK: 0.1.3, unchanged and compatible.
• Record schema 6, SQL schema 1, and recording/verification defaults are unchanged.
• Rust 1.92+; Node SDK 20+.
• The experimental Rust core adds prepared-history APIs and JevError::UnknownHarness; update exhaustive error matches as needed.
• Older cache fingerprints miss safely. Existing history is not rewritten. Back up history before explicit maintenance, especially oversized legacy SQL records.

Follow-ups: #170, #171, #172, #173.

Full changelog · Changes since v0.1.8

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 (--launch opens the native
  hook browser) and jevia 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 --pure mode.
• 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 --locked

The 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.

Jevia 0.1.7

Jevia 0.1.7

CLI/core 0.1.7 and the separately versioned Node SDK 0.1.3 are published.

Highlights

• Stream JSONL run lookups, updates, and basic health counts. A synthetic
  100,000-record feedback probe reduced peak memory from about 74 MiB to 12 MiB;
  full-file validation and rewrite I/O remain linear in history size.
• Read known outcomes and passive observations from a consistent snapshot.
  SQLite and PostgreSQL 16+ gain an additive passive-history performance index.
• Bound cache/history lock waits and replay work; keep agent supervision
  responsive, rotate replay fairly, and preserve journals for safe retries.
• Keep private native recording artifacts out of Git, report detected hook loss
  conservatively, and add preview-first recording-artifact inspection/cleanup.
• Add opt-in routing explanations and escape controls in human-readable
  metadata, application error chains, warnings, and displayed paths.
• Add versioned storage check --json diagnostics and SDK
  checkStorageReport(); existing text checks remain compatible.
• Replace the yanked locked yoke-derive 0.8.3 with 0.8.4.

Upgrade notes

Record schema 6, SQL schema 1, configuration, and the Rust core API are unchanged
from 0.1.6. Recording and history reuse stay automatic; feedback and extra
verification stay optional. Native activity is not proof of task success.

Existing SQL stores work without the new index. Back up history and explicitly
run jevia storage init during a quiet maintenance window if you want to add it;
ordinary routing and diagnostics do not create or replace indexes. PostgreSQL
before 16 retains the compatible paginated fallback.

SDK checkStorageReport() requires CLI 0.1.7 or newer. Existing SDK methods
keep their documented minimum versions. Rust 1.92 and Node.js 20 remain the
minimum supported versions. The npm package does not install the CLI automatically.

Install

cargo install jevia --version 0.1.7 --locked
npm install jevia@0.1.3

Release binaries include SHA-256 checksums, an SPDX SBOM, and signed GitHub
build/SBOM attestations. The default web installer advances through a separate
PR only after the platform installer and attestation smoke tests pass.

See the changelog,
CLI reference,
and SDK documentation.

Jevia 0.1.6

Jevia 0.1.6

CLI/core 0.1.6 and the separately versioned Node SDK 0.1.2 are published.

Highlights

• Automatic execution recording for jevia run, with supported Claude Code, Codex, and OpenCode native adapters. Extra verification and feedback are optional; observed activity is not proof that a task succeeded.
• Durable live checkpoints, recoverable journals, whole-session counters, and shutdown-failure protection.
• Explicit lock release despite duplicated/inherited Unix descriptors, preventing false-active recovery failures and delayed history/cache unlocks.
• Read-only jevia harness health <name> diagnostics and passive model activity/coverage in jevia stats.
• Optional SDK recordExecution() for finished application-owned work, with application provenance, bounded input, exact-retry idempotency, and JSONL/SQLite/PostgreSQL support. Recorded history informs subsequent routing and its cache keys automatically.
• Contract tests against pinned real harnesses and local model endpoints without bypassing normal hook trust.

Upgrade notes

Back up history and upgrade all readers/writers sharing a store together to CLI/core 0.1.6 and SDK 0.1.2. New records use schema 6; schemas 1–5 remain readable. SQL database schema 1 is unchanged. Older clients reject newer records: do not downgrade against updated history.

Omitted auto_verify now defaults to false (CLI 0.1.4–0.1.5 defaulted to true). Existing explicit verifiers and opt-in settings remain enabled.

This experimental patch adds Rust struct fields and enum variants and is not source-compatible with every 0.1.5 library caller. Review direct struct construction and exhaustive matches. Minimum versions remain Rust 1.92 and Node.js 20.

Install

cargo install jevia --version 0.1.6 --locked
npm install jevia@0.1.2

The npm package requires the CLI and does not download it automatically. Release binaries include checksums, an SPDX SBOM, and signed GitHub build/SBOM attestations. The default web installer advances through a separate PR only after its platform smoke tests pass.

See the changelog, CLI reference, and SDK recording guide.

v0.1.5

What's Changed

• chore(website): pin installer to v0.1.4 by @Kinfe123 in #73
• docs: explain storage locations and custom paths by @Kinfe123 in #74
• feat: expand the landing-page harness rotation by @Kinfe123 in #38
• docs: show persisted run record by @Kinfe123 in #75
• ci: automate installer release verification by @Kinfe123 in #76
• feat: add native Windows installer by @Kinfe123 in #77
• feat: add guided harness presets by @Kinfe123 in #78
• chore: defer incompatible dependency majors by @Kinfe123 in #82
• ci: attest release artifacts by @Kinfe123 in #83
• ci: test current installers on release rebuilds by @Kinfe123 in #84
• ci: add CodeQL scanning by @Kinfe123 in #85
• security: resolve code scanning findings by @Kinfe123 in #86
• chore(release): prepare v0.1.5 by @Kinfe123 in #87

Full Changelog: v0.1.4...v0.1.5

v0.1.4

Jevia 0.1.4

An outcome-integrity, automatic-verification, and SDK reliability patch. Storage formats, Rust 1.92, and Node.js 20 minimums are unchanged.

Highlights

• Validate live and cached route decisions before persistence or reuse.
• Automatically discover root Rust or Node tests when a harness has no explicit verifier, with preview, opt-out, deadlines, and process-tree cleanup.
• Explicitly complete externally executed runs with jevia runs complete.
• Redact provider, transport, CLI, and SDK diagnostics while exposing safe error categories.
• Publish jevia@0.1.1 with storage setup/checks, external completion, stricter protocol validation, command deadlines, and privacy-safe errors.
• Upgrade process-wrap to 10.0.1 after the full cross-platform matrix passed.

Install or upgrade

curl -fsSL https://jevia.dev/install.sh | sh

Or install from crates.io with Rust 1.92+:

cargo install jevia --version 0.1.4 --locked

For Node.js integrations:

npm install jevia@0.1.1

Native macOS and Linux binaries for ARM64 and x64 are attached with verified SHA-256 checksums.

Full changes: v0.1.3...v0.1.4

v0.1.3

Jevia 0.1.3

A reliability and privacy patch for the CLI. Storage formats and the Rust 1.92 minimum are unchanged.

Fixes

• Keep supervising background children after their parent exits; preserve cancellation and timeout handling through process-tree cleanup.
• Retry transient permission-denied process-group probes without claiming that children have stopped.
• Preserve valid JSONL history that is missing its final newline when appending new runs, including concurrent cache hits.
• Redact malformed configuration, history, and cache values from CLI parser errors while retaining safe location and repair guidance.

Install or upgrade

cargo install jevia --version 0.1.3 --locked

Native binaries for macOS and Linux (Intel/AMD and ARM64) are attached with SHA-256 checksums. The website installer is pinned to 0.1.3 after artifact verification:

curl -fsSL https://jevia.vercel.app/install.sh | sh

The Node SDK's literal-argument handling fix is also in this source revision. The first npm release is available as jevia@0.1.0; its version is independent of the Rust CLI. Install the CLI first, then run npm install jevia.

Full changes: v0.1.2...v0.1.3

v0.1.2

Jevia 0.1.2 is published on crates.io: jevia and jevia-core.

Highlights

• Opt-in SQLite and PostgreSQL history backends, with JSONL remaining the default (#29).
• Routing outcome statistics that distinguish verified evidence from manual feedback and process exits (#30).
• Preview-first database setup, explicit migration, and backup-first SQL history retention (#31, #32).
• Streaming exports/imports and non-mutating deep history checks (#33, #34, #35).
• Preview-first harness setup with backups and explicit apply/replacement controls (#39).
• Offline harness preflight with structured JSON diagnostics, without launching agents or contacting APIs/databases (#41).
• Explicit configuration-lock release to prevent duplicate Unix descriptors retaining a completed setup's lock.

Install

cargo install jevia --version 0.1.2 --locked
jevia --version

Building from source requires Rust 1.92 or newer. Checksum-verified prebuilt binaries are provided for macOS and Linux on Intel and ARM.

Compatibility

Despite the patch version, the experimental jevia-core API adds the Config::storage field. Rust callers constructing Config directly must supply storage or use ..Config::default(); this is not source-compatible with every 0.1.1 caller.

Existing CLI configs without [storage] continue to use JSONL without migration. SQL is opt-in; changing backends does not silently move or synchronize history. SQL database schema 1 stores history record schemas 1–3, with no new history format version in this release. Back up configuration/history before upgrading or opting into SQL. Older CLIs cannot read SQL storage configuration: do not downgrade by switching to stale JSONL history.

Harness preflight performs static checks only. It does not certify provider authentication, model access, program launchability, or task correctness. No managed service or dashboard is included.

Verification

155 local Rust tests including PostgreSQL passed, alongside formatting, strict Clippy, package dry runs, and Linux/macOS/Windows CI. Release verification also covers a clean registry installation, offline harness setup/preflight, SQLite setup, deep history checks, statistics, and export. No live provider request is needed for these smoke checks.

Both registry package checksums match the archives from tagged commit 54c41af842b053390a2684244f4dd16ee3cbb83c. All four prebuilt binaries were downloaded and their SHA-256 checksums verified. The Apple Silicon release binary also passed the offline CLI smoke checks.

v0.1.1

Jevia 0.1.1 is published on crates.io: jevia and jevia-core.

Highlights

• Run lifecycle inspection and explicit interruption recovery (#17).
• Opt-in non-interactive supervision with harness/verifier deadlines and cancellation (#19).
• Outcome provenance and audited manual feedback (#21).
• Cross-process coordination of equivalent routing cache misses (#22).
• Preview-first history repair and archival with exact-byte backups (#23).

Install

cargo install jevia --version 0.1.1 --locked

Prebuilt macOS and Linux binaries for Intel and ARM are attached with SHA-256 checksums. The website installer selects and verifies the matching binary.

Compatibility

New and updated histories use schema 3; schemas 1 and 2 remain readable. Older Jevia versions refuse schema 3 rather than discard metadata. Back up local history before upgrading if a downgrade may be needed. Legacy outcomes without provenance require explicit feedback confirmation before they inform routing. Rust consumers constructing record structs or exhaustively matching lifecycle states may need updates for new fields and variants.

Building from source requires Rust 1.92+. Interactive harness behavior remains the default; deadlines require --non-interactive.

Verification

66 Rust tests, formatting, strict Clippy, website tests/build, package dry runs, and Linux/macOS/Windows CI passed. Both published package checksums match the archives produced from commit 31fccabb635ff1e5b66b4b49bb10305a7c38da74. An isolated crates.io installation was verified with version/help, initialization, history/cache inspection, and maintenance previews. No live provider request was made.

All four prebuilt binaries were downloaded from this release and their SHA-256 checksums verified before publication.

v0.1.0

First experimental crates.io release of Jevia, an outcome-aware model router for coding agents.

Install

Requires Rust 1.92 or newer and Cargo.

cargo install jevia --version 0.1.0 --locked
jevia --version
jevia init
export TYPESAFE_API_KEY="your-key"
jevia check

The API key must be a real Jev credential. jevia check makes one live routing request; use jevia doctor for local checks without an API request.

Included

• Configurable capability tiers and deterministic confidence fallback.
• Local outcome history that informs later routing decisions.
• Shell-free harness adapters and optional verification commands.
• Concurrency-safe history and learning-aware routing cache.
• Local diagnostics, live setup checks, and JSON output for integrations.

Routing alone does not execute a task or prove success. Managed services and the dashboard are not part of this release.

Packages

• jevia 0.1.0
• jevia-core 0.1.0

Verification

43 workspace tests, formatting, Clippy, documentation build, and package dry runs passed. CI passed on Linux, macOS, and Windows. A fresh crates.io installation passed CLI smoke tests, and all 26 tests in the packaged CLI source passed.

Release preparation: #12.