phernandez e846ae85d8 fix: semantic embeddings not generated on fresh DB or upgrade ...

The previous backfill trigger relied on Alembic revision tracking, but
alembic_version only stores the head revision — intermediate revisions
(like the backfill trigger) are invisible after a multi-step upgrade or
fresh DB creation.

Three changes fix this:

1. Replace Alembic revision check with a simple "entities exist but
   embeddings are empty" check that works regardless of migration path
2. Generate embeddings during sync — after FTS indexing, batch-embed all
   synced entities at the end of the sync operation
3. Add background backfill at MCP startup for the upgrade path (entities
   already exist, no embeddings) without blocking server readiness

Also adds clear startup logging for semantic embedding status so issues
are easy to spot in the logs.

📋 Covers: fresh DB, upgrade from pre-embedding version, db reset,
   interrupted backfill

Signed-off-by: Pedro Hernandez <pedro@basicmachines.co>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Signed-off-by: phernandez <paul@basicmachines.co>

2026-03-07 13:23:39 -06:00

..

__init__.py

refactor: composition roots, deps split, and typed API clients (#490 roadmap) (#502)

2026-01-04 11:05:58 -06:00

background_sync.py

chore: Cloud auth (#213)

2025-07-07 21:08:25 -05:00

coordinator.py

feat: add basic-memory watch CLI command (#559)

2026-02-12 20:10:09 -06:00

sync_service.py

fix: semantic embeddings not generated on fresh DB or upgrade

2026-03-07 13:23:39 -06:00

watch_service.py

fix: unify project path so path is always the local filesystem path

2026-02-24 15:08:09 -06:00