v0.66.0 Release Recap

v0.66.0 is a non-breaking operations release that makes published backup drift reports easier to act on without changing write behavior.

What's New

Area	New in v0.66.0	Why it matters
Drift reports	recommended_publish_command	Gives operators the exact dry-run publish command to review when local backup catalog metadata should replace published metadata
Doctor checks	published_backup_drift detail includes the repair hint	Keeps the combined health report actionable without requiring a second CLI lookup
Feature metadata	doctor-published-backup-repair-hint	Lets live docs and /v1/features advertise the operational repair-hint surface

Compatibility

This release is non-breaking. The new command hint is additive JSON/report metadata and does not execute writes. Operators still need to run the recommended publish command themselves and add --execute only after reviewing the dry-run report.

Operator Flow

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

When local and published backup catalog metadata differ, the report now includes a dry-run command shaped like:

contextdb snapshot lifecycle index publish \
  --in "$CONTEXTDB_BACKUP_DIR/contextdb-backups.index.json" \
  --report \
  --publish-url "$CONTEXTDB_LIFECYCLE_INDEX_PUBLISHED_URL"

Verification

Release gates:

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