fix(db): error on embedding dimension mismatch #20
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When the embedding model changes after indexing, stored chunk embeddings can have a different dimensionality than the query embedding. Previously this was silently treated as 0.0 similarity, producing confusing 0% scores.
This change detects dimension mismatches (and corrupt embedding blobs) during search and returns a clear error suggesting reindexing via: vgrep index --force.
A unit test covers the mismatch case.
Validation: