Skip to content

v0.2.2

Choose a tag to compare

@justram justram released this 25 Mar 02:17
· 31 commits to main since this release

pi-serini v0.2.2

Patch release focused on tightening the package-owned pi-search boundary, preserving structured failure metadata more cleanly, and locking the current ownership split in place with regression coverage.

Added

  • Added small stable machine-readable metadata to pi-search protocol errors:
    • code
    • toolName
    • target
    • schemaName
    • fieldPath
  • Added benchmark-harness artifact support for structured pi-search failure metadata when recoverable tool failures include it.
  • Added a whole-tree regression guard that fails if package-owned src/pi-search/ modules import repo-owned src/ layers.

Changed

  • Changed src/pi-search/extension.ts to remain the package-owned extension registration layer, while keeping the repo-local BM25 composition seam in src/extensions/pi_search.ts.
  • Changed shared JSONL ownership to src/runtime/jsonl.ts so it no longer sits under fake pi-search ownership.
  • Changed src/pi-search/protocol/parse.ts to attach structured metadata for malformed JSON and schema-invalid payloads.
  • Changed the package-owned Anserini adapter seam to depend on a pi-search-owned narrow helper transport interface instead of the repo-owned BM25 RPC client type.
  • Changed the package-owned prompt dump env gate from PI_BM25_DUMP_PROMPTS to PI_SEARCH_DUMP_PROMPTS.

Fixed

  • Fixed maintainer-facing docs to describe the current package-owned pi-search boundary and the thin repo-local BM25 wrapper honestly.

Scope

v0.2.2 does not introduce a new backend kind or a new benchmark architecture milestone.

This release is specifically about making the existing pi-search ownership boundary more honest and more durable by:

  • keeping structured protocol and harness metadata intentionally narrow and stable
  • reducing remaining cross-boundary coupling around the Anserini adapter seam
  • preventing future repo-owned import leaks from creeping back into package-owned pi-search
  • keeping maintainer docs aligned with the current in-repo package boundary