v0.71.0 Release Recap

v0.71.0 is a non-breaking durability release that adds an opt-in doctor freshness check for graph-derived KV cache values.

What's New

Area	New in v0.71.0	Why it matters
Doctor check	contextdb doctor --kv-derived-key KEY	Reads derived KV metadata and verifies that cached generated values are still fresh
Freshness policy	--max-kv-derived-age DURATION	Lets operators decide how old derived session context may be before refresh
Failure detail	kv_derived_freshness check	Reports stale, missing, malformed, or non-derived values without mutating the cache
Feature metadata	doctor-kv-derived-freshness	Lets live deployments advertise derived KV freshness support

Compatibility

This release only adds optional doctor flags and feature metadata. Existing --kv-key presence checks, KV repair plans, derived recent-node values, TTL behavior, and --execute writes are unchanged.

Operator Flow

contextdb doctor \
  --kv-derived-key context:prod:support:recent-nodes \
  --max-kv-derived-age 2h

The check validates that the value is JSON, has a contextdb.kv.derived.* kind, includes a valid generated_at, and is not older than the configured max age.

Verification

Release gates:

Gate	Result
go test -count=1 ./cmd/contextdb	Passed
go test -count=1 ./...	Passed
npm run docs:build	Passed
git diff --check	Passed