Release Notes: v0.2.0¶
Date: 2026-09-16
Version 0.2.0 is the post-0.1.9 architecture release. It completes the segmented-index work, hardens the network server and integrations, and updates the persistence and search dependencies.
Indexing and retrieval¶
- Added validated segmented snapshots alongside the existing single-index layout; both remain supported.
- Added adaptive segmented routing as an opt-in mode with configurable query top-N and maximum top-N values. The existing fixed top-N behavior remains unchanged.
- Added inverted segment routing, deterministic candidate ordering, and consistent fallback execution/diagnostics.
- Added segment invariant validation for public constructors: unique segment IDs, non-empty segments, unique documents, and document/index consistency.
- Preserved exhaustive behavior for strategies that require corpus-wide comparison (coverage, team, typed evidence, connection enrichment, and explicitly all-segment queries).
- Published immutable snapshots independently from the mutable writer state, so searches continue using the previous snapshot during refresh.
- Added global BM25 statistics across selected segments and improved segment benchmark tooling and reporting.
Memory API and persistence¶
- Request fingerprints are now cryptographic digests over canonical request data instead of serialized message content.
- Idempotency fingerprints include
session_idas well as messages. - Requests validate all messages before mutation, preventing partial writes from late-invalid messages.
- Migrated binary persistence from
bincodetooxicodewith the Serde compatibility API. - Kept Tantivy pinned to 0.25 after 0.26 reduced measured recall and MRR; upgraded text2num to 2.8.
Server and security¶
- Added JWT and tenant/user isolation hardening; empty JWT secrets are treated as unconfigured.
- Moved blocking mutation and search work off the Axum async executor.
- Separated client validation errors (422) from internal operation failures (500).
- Added bounded request and integration input handling, including provider hooks, status lines, and MCP transport paths.
- Made non-strict malformed configuration fall back safely while strict mode continues to fail fast.
Agent integrations¶
- Fixed feature-gated integration compilation paths for session recording and MCP transport.
- Hardened provider hook parsing and subprocess transport behavior.
- Closed spaCy subprocess stdin correctly and drained stdout/stderr concurrently to avoid pipe deadlocks.
- Preserved provider-specific session recording, redaction, and lifecycle behavior across Claude Code, Codex, Gemini CLI, and AGY.
Compatibility and upgrade notes¶
- Single-index deployments remain supported; segmented and adaptive layouts are selected through pipeline/server configuration.
- Binary cores written by older releases should be rebuilt before use because the persistence codec changed during this release line.
- The remote query protocol and store schema versions remain independent of the package version.
- The deprecated 0.1.9
MemoryIndexquery wrappers remain available in 0.2.0 for source compatibility. New code should usequery_with_temporal_context; their removal is deferred to a later breaking release. - Raw
SegmentedMemoryIndexconstruction is now fallible because constructors validate segment IDs, document ownership, empty segments, and index contents. - Current
cargo auditoutput contains only transitive Tantivy warnings inlruandmemmap2; these are tracked for upstream fixes.
Verification¶
- Feature-enabled unit and integration tests pass.
- All-target/all-feature compilation passes.
- Segment benchmark coverage includes fixed-top-N, adaptive, and non-segmented comparisons.
The current Tantivy 0.25 benchmark artifact covers 133 multi-session queries. Fixed top-5 records 95.49% any-hit Recall@5 at 1.25 ms average latency; adaptive 5→12 records 96.24% any-hit Recall@5 at 4.36 ms; and the single-index baseline records 93.23% any-hit Recall@5 at 6.41 ms. See segment-multisession-v0.2.0.json.