v0.79.0 Release Recap
v0.79.0 is a non-breaking operations documentation release that adds a guarded execution recipe for stale graph-derived KV cache repairs.
What's New
| Area | New in v0.79.0 | Why it matters |
|---|---|---|
| Stale KV repair recipe | Doctor hint to dry-run to execute checklist | Gives operators a repeatable path from kv_derived_freshness failure to reviewed refresh |
| Payload review | Explicit checks for namespace, labels, count, generated timestamp, and compact node list | Keeps derived session context from being refreshed with the wrong scope |
| Confirmation step | Rerun doctor after --execute | Verifies the hot key is present and fresh after repair |
| Feature metadata | kv-derived-repair-execution-recipe | Lets live deployments advertise the execution recipe in docs and feature introspection |
Operator Flow
Start with doctor:
bash
contextdb doctor \
--kv-derived-key context:prod:support:recent-nodes \
--max-kv-derived-age 2h \
--reportWhen kv_derived_freshness fails, run the recommended_repair_command as a dry run, review the derived payload, then repeat with --execute --report. Rerun doctor with the same key and freshness window before closing the incident.
Compatibility
This release is intentionally non-breaking. It updates docs and feature metadata only; existing doctor checks, repair commands, derived payloads, and write behavior are unchanged.
Verification
Release verification included:
bash
go test -count=1 ./cmd/contextdb
go test -count=1 ./...
npm run docs:build
git diff --checkRead the full workflow in KV Derivation Recipes.