v0.98.0 Release Recap

v0.98.0 is a non-breaking operations docs release that turns the published backup repair closure lane into a stable artifact bundle shape.

What's New

Area	New in v0.98.0	Why it matters
Closure artifact bundle	docs/deployment/published-backup-repair-guard.md	Gives incident handoffs fixed filenames for every repair evidence step
Stable evidence names	01-doctor-freshness-before.json through 07-doctor-final.json	Makes it obvious which reports happened before, during, and after the repair
Docs regression test	TestPublishedBackupRepairGuardDocumentsDoctorReceiptClosureLane	Keeps the closure lane and bundle artifact names present in the runbook
Feature metadata	doctor-backup-receipt-closure-artifact-bundle	Lets live deployments advertise the closure bundle recipe

Operator Flow

Create one bundle directory per published backup catalog repair:

export CONTEXTDB_REPAIR_BUNDLE="$CONTEXTDB_BACKUP_DIR/published-backup-repair-$(date -u +%Y%m%dT%H%M%SZ)"
mkdir -p "$CONTEXTDB_REPAIR_BUNDLE"

Then save the before-doctor reports, dry-run publish report, execute report, receipt, receipt verification report, doctor receipt report, and final doctor report using the stable filenames in the repair guard.

Compatibility

This release is intentionally non-breaking. Runtime behavior is unchanged; the release documents a stable incident artifact shape around existing doctor, publish, receipt, and verification commands.

Verification

Release verification included:

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

The next reliability slice should focus on a doctor lane for KV receipt verification or a schema catalog for published docs schemas.