@hackage / shikumi-cache

Content-addressed response caching for shikumi (EP-6)

Changelog

Changelog

Unreleased

0.1.2.0 - 2026-07-05

Added
  • CacheConfig, defaultCacheConfig, and cachedLLMWith for a shared policy layer across cache backends, including optional TTL-based entry expiry.
  • Shikumi.Cache.Backend.Effort for best-effort backend error handling and stripMessageTimestamps for canonical cache-key inspection.
Changed
  • Cache keys now include endpoint identity, default/per-call headers, provider compatibility settings, and omit message construction timestamps. This bumps currentKeyVersion to shikumi-cache/v2, invalidating old cache entries and old trace replay keys.
  • cachedLLM no longer stores in-band provider error responses, and persistent backend lookup/store failures degrade to cache misses or no-ops.
  • Refreshed the internal shikumi bound for the 0.3 series.

0.1.1.0 - 2026-06-28

Changed
  • Refreshed the internal shikumi bound for the 0.2 series.
  • Updated SQLite backend internals to match the record-patterns conventions used across the package set.

0.1.0.1 - 2026-06-21

Changed
  • Constrained the baikai dependency to the 0.2 series and refreshed internal shikumi bounds.

0.1.0.0 - 2026-06-13

Added
  • Initial Hackage release of provider-neutral response caching for shikumi.
  • Content-addressed cache keys, in-memory and SQLite cache backends, cached LLM interpretation, and response JSON support shared by backend packages.