v0.75.0 Release Recap

v0.75.0 is a non-breaking operations release that adds dry-run repair command hints to derived KV freshness failures.

What's New

Area	New in v0.75.0	Why it matters
Doctor detail	`recommended_repair_command` for `kv_derived_freshness` failures	Gives operators the exact dry-run refresh command to review after stale, missing, or malformed derived KV values
KV repair flow	`contextdb repair kv-cache --derive recent-nodes --report` hint	Keeps refreshes aligned with the existing dry-run-first derived KV workflow
Operator docs	Freshness and derivation recipes mention the hint	Makes the stale-cache path discoverable from both doctor and repair docs
Feature metadata	`doctor-kv-derived-repair-hint`	Lets live deployments advertise derived KV repair hint support

Run doctor with derived KV freshness:

bash

CONTEXTDB_DATA_DIR=/var/lib/contextdb \
  contextdb doctor --kv-derived-key context:prod:support:recent-nodes --max-kv-derived-age 2h

When the check fails, review the dry-run command in recommended_repair_command:

bash

contextdb repair kv-cache \
  --key context:prod:support:recent-nodes \
  --derive recent-nodes \
  --derive-namespace support \
  --report

Add --execute only after reviewing the derived value and confirming the namespace, labels, node count, and generated timestamp.

This release is intentionally non-breaking. Doctor remains read-only, and the recommended command is dry-run by default.

Release verification included:

bash

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

Read the full workflow in Operations and KV Derivation Recipes.