v0.10.0 Release Recap
v0.10.0 is a non-breaking operational release that adds an opt-in backup readiness check to contextdb doctor. Operators can point doctor at a local backup marker file and fail the report when that marker is missing or stale.
What Changed
| Area | New in v0.10.0 | Why it matters |
|---|---|---|
| Doctor backup marker | contextdb doctor --backup-marker PATH | Lets deployments prove that backup automation recently ran |
| Backup age threshold | --max-backup-age 24h | Lets operators tune how fresh backup evidence must be |
| JSON report | backup_readiness check result | Makes backup freshness visible to scripts and deployment monitors |
| Feature metadata | doctor-backup-readiness feature tag | Lets live deployments advertise the doctor capability through introspection |
Non-Breaking Behavior
The backup check is opt-in. Existing doctor checks and sample write behavior are unchanged unless --backup-marker is provided.