The chunk store reads whatever database is open at call time, so a query that
was awaiting the model returned an answer built from the previous account's
documents, and a large file being read was inserted into the new account's
knowledge base and synced there. Each operation now remembers the account
scope it started in and stops if it changed.
- Each document gets an indexing run number; a reindex, synced replacement or
delete makes the older run stop instead of embedding stale chunks, reporting
'indexed' early and leaving a progress bar for a deleted document
- Reindexing a file that is now empty throws like addDocument instead of
replacing the stored chunks with nothing