v0.62.0 Release Recap

v0.62.0 is a non-breaking operations release that brings published backup catalog drift into the combined doctor report.

What Changed

Area	New in v0.62.0	Why it matters
Doctor drift check	contextdb doctor --published-backup-index PATH --published-backup-url URL	Compares the local lifecycle index with published backup metadata during the normal health run
Shared drift logic	Reuses lifecycle index publish drift reporting	Keeps doctor output aligned with the dedicated backup catalog drift command
Failure detail	published_backup_drift check includes difference counts and field-level drift details	Gives operators a fast signal when published backup metadata no longer matches local catalog state
Feature metadata	doctor-published-backup-drift	Lets live deployments advertise the combined doctor drift capability

Compatibility

This release only adds an optional doctor flag and feature metadata. Existing doctor checks, lifecycle index publish drift commands, freshness checks, backup commands, and API surfaces are unchanged.

Operator Flow

contextdb doctor \
  --published-backup-index /var/lib/contextdb/backups/contextdb-backups.index.json \
  --published-backup-url https://ops.example.test/contextdb/backups/index

Use this when the live service should prove both metadata freshness and local-vs-published catalog agreement from one doctor report.

Verification

Release gates for this slice:

Gate	Status
go test -count=1 ./...	Passed
contextdb doctor --published-backup-index ... --published-backup-url ... smoke	Passed
npm run docs:build	Passed
git diff --check	Passed