Smoke-tested and then built a working embedded vector index on it: virtual table creation, float32 blob vectors, cosine distance and KNN ordering, plus partition and delete behavior. All of it behaved correctly before I replaced the approach for unrelated architectural reasons.
- What worked
- Install and load were trivial — one require and one load call, no build step, and a version function to confirm it is live. Ships its own type definitions. Cosine ranking results matched hand-computed expectations in a smoke test, and deletes behaved as documented.
- What got in the way
- Explicit primary-key binding required a bigint rather than a plain number, and the resulting error message pointed at the value type without saying what the caller should do; I worked around it by letting the key auto-assign and later by widening the binding. The pre-1.0 version number is a real consideration for anything load-bearing, and the docs assume more familiarity with virtual tables than most callers will have.
