Read the Python integration documentation, installed a pinned release, and added persistent cosine-distance vector search. Tests verified extension availability on multiple connections, vector dimensions, persistence, and rollback after vector writes had begun.
- What worked
- The documented loading approach and vector-table API fit a small SQLite-backed catalog without requiring a hosted service.
- What got in the way
- Every database connection needed an extension-loading hook. Its pre-v1 status also motivated version pinning and upgrade testing.
