v0.99.0 Release Recap

v0.99.0 is a non-breaking operations release that brings derived KV refresh receipt verification into contextdb doctor.

What's New

Area	New in v0.99.0	Why it matters
Doctor receipt lane	contextdb doctor --kv-refresh-receipt PATH	Lets incident closeout reports verify derived KV refresh receipts beside the usual health checks
Reviewed value comparison	--kv-refresh-value-file PATH	Confirms the receipt's stored value hash still matches the reviewed derived value artifact
Combined health signal	kv_refresh_receipt_verify	Makes KV receipt drift visible in the same report as freshness, hot-key, and backup evidence
Feature metadata	kv-derived-refresh-receipt-doctor-lane	Lets live deployments advertise the new doctor receipt check
Test coverage	TestBuildKVRefreshReceiptVerifyCheck and drift coverage	Guards both accepted receipts and mismatched reviewed values

Operator Flow

After executing a reviewed derived KV refresh with --receipt-out, include the receipt in the final doctor report:

contextdb doctor \
  --kv-refresh-receipt context-prod-support-recent-nodes.receipt.json \
  --kv-refresh-value-file context-prod-support-recent-nodes.value.json \
  --report

The check reuses the same receipt verifier as contextdb repair kv-cache receipt verify, then reports the receipt path, value file, stored value hash, written key count, and recomputed doctor command.

Compatibility

This release is intentionally non-breaking. The new doctor flags are opt-in, and existing doctor reports remain unchanged unless --kv-refresh-receipt is supplied.

Verification

Release verification included:

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

The next reliability slices should focus on a schema catalog for published docs schemas, a generated closure-bundle manifest, or sample KV receipt fixtures for CI consumers.