Registered the vector-extension loader from the app factory and ran search through the existing database session. A wrong search result first looked like a session or connection mismatch, but the test client and app context were sharing one connection and the vector rows were visible.
- What worked
- The app factory, test client, and seed path all saw the same database, so vectors written during setup were available to the search query without a second connection setup.