How does the VS Code extension protect vector fields during key edits?

In both the Search Query Runner's results and the hash key editor, vector fields are rendered as read-only placeholders like ⟨N bytes · binary⟩ rather than as editable text or numbers.

That matters because a vector embedding round-tripped through a text editor – parsed, displayed, re-typed, and re-serialized – risks subtle corruption from formatting or precision loss.

By keeping the vector itself untouchable while still letting you edit other fields on the same hash, BetterDB guarantees the embedding bytes stay exactly as they were, which matters a lot when that embedding is what a vector index is searching against.

It's a small design choice with an outsized payoff: a tool built for general-purpose key editing could easily let someone innocently fix a typo in a neighboring text field and silently corrupt the vector alongside it, breaking KNN search results in a way that's hard to trace back to "someone edited this hash in an editor."