v0.57.0 Release Recap

v0.57.0 is a non-breaking operations release that folds published backup catalog freshness into contextdb doctor.

What Changed

Area	New in v0.57.0	Why it matters
Doctor freshness check	contextdb doctor --published-backup-url URL	Adds published lifecycle index freshness to the combined health report
Freshness threshold	--max-published-backup-age 24h	Lets operators enforce the same age policy used by lifecycle freshness checks
Published metadata options	--published-backup-method, --published-backup-token, --published-backup-timeout	Supports authenticated or non-GET metadata endpoints
Feature metadata	doctor-published-backup-freshness	Lets live deployments advertise the combined doctor freshness check

Compatibility

This release only adds optional doctor flags. Existing doctor checks, snapshot lifecycle commands, REST APIs, storage formats, and SDK contracts are unchanged.

Operator Flow

contextdb doctor \
  --published-backup-url https://ops.example/contextdb/lifecycle-index.json \
  --max-published-backup-age 24h

The report includes a published_backup_freshness check with status, generated time, observed age, and the configured maximum age.

Verification

Release gates for this slice:

Gate	Status
go test -count=1 ./...	Passed
npm run docs:build	Passed
git diff --check	Passed