v0.50.0 Release Recap

v0.50.0 is a non-breaking operations release that adds dry-run-first vector index repair for reviewed rebuild candidates.

What Changed

Area	New in v0.50.0	Why it matters
Repair command	contextdb repair vector-index	Turns doctor rebuild candidates into an operator-controlled repair flow
Dry-run report	--report without --execute	Shows sampled vector nodes and candidate IDs before any mutation
Explicit execution	--execute --report	Reindexes reviewed graph-node vectors into the local vector index
Feature metadata	vector-index-repair	Lets live deployments advertise the repair surface

Compatibility

This release adds a new CLI command. Existing write paths, retrieval APIs, doctor checks, backup flows, SDKs, REST, GraphQL, and gRPC behavior are unchanged.

Operator Flow

CONTEXTDB_DATA_DIR=/var/lib/contextdb \
  contextdb doctor --store-consistency --store-namespace my-app --store-sample 100

CONTEXTDB_DATA_DIR=/var/lib/contextdb \
  contextdb repair vector-index --namespace my-app --sample 100 --report

CONTEXTDB_DATA_DIR=/var/lib/contextdb \
  contextdb repair vector-index --namespace my-app --sample 100 --execute --report

The repair command scans valid graph nodes with vectors, confirms whether each node appears through vector search, and rebuilds missing vector entries only when --execute is present.

Verification

Release gates for this slice:

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