fix: resolve SDK spawn failures and sharp native binary crashes

- Strip CLAUDECODE env var from SDK subprocesses to prevent "cannot be
  launched inside another Claude Code session" error (Claude Code 2.1.42+)
- Lazy-load @chroma-core/default-embed to avoid eagerly pulling in
  sharp native binaries at bundle startup (fixes ERR_DLOPEN_FAILED)
- Add stderr capture to SDK spawn for diagnosing future process failures
- Exclude lockfiles from marketplace rsync and delete stale lockfiles
  before npm install to prevent native dep version mismatches

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

src/services/sync/ChromaSync.ts

@@ -13,7 +13,6 @@
  */
 
 import { ChromaClient, Collection } from 'chromadb';
-import { DefaultEmbeddingFunction } from '@chroma-core/default-embed';
 import { ParsedObservation, ParsedSummary } from '../../sdk/parser.js';
 import { SessionStore } from '../sqlite/SessionStore.js';
 import { logger } from '../../utils/logger.js';
@@ -191,7 +190,9 @@ export class ChromaSync {
 
     try {
       // getOrCreateCollection handles both cases
-      // Use DefaultEmbeddingFunction for local embeddings (all-MiniLM-L6-v2)
+      // Lazy-load DefaultEmbeddingFunction to avoid eagerly pulling in
+      // @huggingface/transformers → sharp native binaries at bundle startup
+      const { DefaultEmbeddingFunction } = await import('@chroma-core/default-embed');
       const embeddingFunction = new DefaultEmbeddingFunction();
       this.collection = await this.chromaClient.getOrCreateCollection({
         name: this.collectionName,