v0.82.0 Release Recap
v0.82.0 is a non-breaking backup operations release that folds published backup repair receipt verification into contextdb doctor.
What's New
| Area | New in v0.82.0 | Why it matters |
|---|---|---|
| Doctor receipt check | contextdb doctor --published-backup-receipt PATH --published-backup-index PATH | Lets operators verify repair receipts inside the combined health report |
| Receipt integrity | Reuses lifecycle index publish receipt verification | Confirms payload hash and catalog metadata still match the local lifecycle index |
| Health signal | published_backup_receipt_verify check | Makes receipt drift visible next to freshness, drift, KV, and store checks |
| Feature metadata | doctor-published-backup-receipt-verify | Lets live deployments advertise doctor receipt verification support |
Operator Flow
bash
contextdb doctor \
--published-backup-index "$CONTEXTDB_BACKUP_DIR/contextdb-backups.index.json" \
--published-backup-receipt "$CONTEXTDB_BACKUP_DIR/published-backup-repair.receipt.json" \
--reportThe check is local and read-only. It does not fetch the published endpoint unless you also pass --published-backup-url for freshness or drift checks.
Compatibility
This release is intentionally non-breaking. Existing doctor checks, publish receipt generation, standalone receipt verification, and published backup drift/freshness 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 repair flow in the Published Backup Repair Guard.