v0.95.0 Release Recap

v0.95.0 is a non-breaking operations release that adds a published backup repair closure lane for doctor receipt verification.

What's New

Area	New in v0.95.0	Why it matters
Doctor receipt closure lane	docs/deployment/published-backup-repair-guard.md	Gives operators one checklist from freshness and drift diagnosis through verified closeout
Backup runbook cross-link	docs/deployment/backup-runbook.md	Points backup operators to the receipt closure lane when published catalog metadata is stale or drifted
Docs regression test	TestPublishedBackupRepairGuardDocumentsDoctorReceiptClosureLane	Keeps the required doctor, publish, receipt, receipt verify, and closeout commands present in the runbook
Feature metadata	doctor-backup-receipt-runbook-lane	Lets live deployments advertise the closure lane through introspection

Operator Flow

Use the lane when a published backup catalog incident needs durable closeout evidence:

contextdb doctor \
  --published-backup-index "$CONTEXTDB_BACKUP_DIR/contextdb-backups.index.json" \
  --published-backup-url "$CONTEXTDB_LIFECYCLE_INDEX_PUBLISHED_URL" \
  --max-published-backup-age 24h \
  --report

Then execute with --receipt-out, verify the receipt directly, fold receipt verification into contextdb doctor, and rerun doctor with freshness and drift checks before closing the repair.

Compatibility

This release is intentionally non-breaking. Runtime behavior is unchanged; the release adds an operator-facing closure lane and a docs regression test around existing receipt and doctor commands.

Verification

Release verification included:

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

The next reliability slice should focus on a derived KV refresh receipt verifier or publishing the retry fatigue preset schema for docs consumers.