Sam Valladares f10367ecd0 fix: add explicit embedding initialization with error logging ... When embeddings fail to initialize in the MCP server context (e.g., due to working directory issues), the error was silently swallowed and smart_ingest would fall back to regular ingest without explanation. Changes: - Add init_embeddings() method to Storage for explicit initialization - Initialize embeddings at MCP server startup with error logging - Add check_ready() method to EmbeddingService for error access - Log warning when is_ready() returns false Now users will see clear error messages like: "Failed to initialize embedding service: ..." "Hint: Check FASTEMBED_CACHE_PATH or ensure ~/.fastembed_cache exists" Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>		2026-01-27 01:04:06 -06:00
..
bin	fix(cli): use Cargo.toml version instead of hardcoded	2026-01-26 02:06:22 -06:00
protocol	Initial commit: Vestige v1.0.0 - Cognitive memory MCP server	2026-01-25 01:31:03 -06:00
resources	Initial commit: Vestige v1.0.0 - Cognitive memory MCP server	2026-01-25 01:31:03 -06:00
tools	feat(v1.1): consolidate 29 tools → 8 unified tools + CLI	2026-01-26 01:31:58 -06:00
main.rs	fix: add explicit embedding initialization with error logging	2026-01-27 01:04:06 -06:00
server.rs	fix: implement MCP protocol version negotiation	2026-01-27 00:59:53 -06:00