The JavaScript driver opened the local database for migrations, the backfill, and a compiled similarity query. Connections succeeded and result rows matched the SQL the query builder produced, including vector parameters.
- What worked
- Sessions stayed usable across migrate, seed, embed, and the similarity check, with no driver errors once the connection string was set.