fix(ingest): embed project-scoped writes (#216)

[RockinPaul]

📋 Description

Fixes #216. applyImportPlan ingests inside a synchronous import_transaction().run(...) and never called the embedder, so every node it created was stored with vectors.semantic: null. Project ingest (longmemory_ingest with project_id), every longmemory_remember_decision, and connector imports go through it, so those memories never received a vector score in recall and could only match lexically.

This embeds each planned node before entering the transaction, the same way ingest() does (embed(cfg.embedding_provider, multilingual_embeddings, embedding_cache, text, language, 'document')), and passes it to engine.ingest as vector. Nodes are embedded sequentially, as ingest() does, so a large connector import doesn't fan out into concurrent provider requests.

🔄 Type of Change

• 🐛 Bug fix (non-breaking change which fixes an issue)

Verification

• New check in benchmarks/src/check.ts: a project-scoped ingestProjectEvent with a configured embedding provider must store a semantic vector. It failed on main (undefined !== 4) and passes with the fix.

• pnpm typecheck, pnpm bench:check, pnpm bench:ci and pnpm build pass.

• pnpm branding:check and pnpm integration:check fail identically on unmodified main: tools/ is not in the repository (Cannot find module tools/branding.mjs), and the n8n lint step reports Command "eslint" not found. No files were added, so the header requirement is unaffected.

• pnpm release:check passes locally (blocked by the missing tools/ directory above)

• New files pass pnpm branding:check (no new files)

• User-visible behavior has been exercised manually when applicable (the reproduction in [BUG] Project-scoped writes (ingest with project_id, remember_decision) are stored without embeddings #216 was run against a deployed server)

🔍 Code Review Checklist

• Code follows the project's coding standards
• Self-review of the code has been performed

📚 Related Issues

• Fixes [BUG] Project-scoped writes (ingest with project_id, remember_decision) are stored without embeddings #216
• Same pattern as fix: expose legacy migration with configured embeddings #214 (a write path that bypassed the configured embedder, there in legacy migration)

🚀 Deployment Notes

Memories already written through this path keep their null vectors; there is no re-embed step, so they stay lexical-only until re-ingested.

🤖 Generated with Claude Code