v0.101.0 Release Recap

v0.101.0 is a non-breaking operations release that turns published backup repair closure bundles into hashed manifest artifacts.

What's New

Area	New in v0.101.0	Why it matters
Closure bundle CLI	contextdb snapshot lifecycle index publish closure-bundle	Gives incident handoffs one command that checks the expected repair evidence files
Manifest artifact	closure-manifest.json	Records expected artifact paths, byte counts, and SHA-256 hashes for later audit
Missing-artifact checks	Non-zero exit on missing evidence	Prevents an incomplete repair bundle from looking closed
Feature metadata	published-backup-closure-bundle-manifest	Lets live deployments advertise hashed closure bundle support
Test coverage	Complete and missing bundle tests	Guards the expected eight-artifact shape and error behavior

Operator Flow

After collecting the seven doctor, publish, and receipt reports in the repair bundle, write the manifest:

contextdb snapshot lifecycle index publish closure-bundle \
  --dir "$CONTEXTDB_REPAIR_BUNDLE" \
  --out "$CONTEXTDB_REPAIR_BUNDLE/closure-manifest.json" \
  --report

The command checks the stable filenames from the published backup repair guard, hashes present files, and reports missing artifacts before the incident is closed.

Compatibility

This release is intentionally non-breaking. The new command is opt-in and only reads the bundle directory plus the manifest path it writes.

Verification

Release verification included:

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

The next reliability slices should focus on KV receipt verification fixtures, schema catalog drift annotations, or manifest re-verification for saved closure bundles.