@wrongstack/vector-memory 1.0.2 → 1.0.4

package/dist/sage-sync.d.ts

@@ -1,3 +1,33 @@
+/**
+ * First-boot SAGE → vector-memory mirror.
+ *
+ * `VectorMemoryStore.syncFromSage()` has no production caller on its own;
+ * this module is that caller. On the first boot per project (no sync marker
+ * next to the vector db), the active SAGE corpus is mirrored into the vector
+ * store so semantic search starts with the project's existing knowledge
+ * instead of an empty index.
+ *
+ * Semantics:
+ *  - Fire-and-forget: the CLI never waits on the sync (first run pays the
+ *    ONNX model download; boot must not block on it).
+ *  - Marker-based: `sage-sync.complete.json` in `store.directory`. A
+ *    `complete` marker means "corpus fully mirrored — don't rescan". A
+ *    `running` marker owned by a LIVE pid means another CLI process owns the
+ *    sync; takeover happens when the marker is >10 minutes old AND the owning
+ *    pid is confirmed dead (`process.kill(pid, 0)`), or when the pid is our
+ *    own (second call in-process).
+ *  - The `complete` marker is only written when the sync had zero failures
+ *    and the embedding provider was available. Anything less leaves no
+ *    marker, so the next boot retries — content-hash dedup inside
+ *    `syncFromSage` makes that retry cheap (already-mirrored texts skip).
+ *  - Privacy: the adapter (createSageSurfaceSyncSource) deliberately omits
+ *    sessionId/includeAllSessions, keeping SAGE's under-report default for
+ *    session-scoped memories — another session's private records are never
+ *    mirrored into this shared project-scoped store.
+ *  - Teardown race: if the store is closed mid-sync, subsequent remember()
+ *    calls throw inside syncFromSage's per-entry guard, the report comes
+ *    back with failures, and no marker is written — next boot retries.
+ */
 import type { MemoryPort } from '@wrongstack/core/types';
 import type { VectorMemoryStore } from './store.js';
 /** Sync marker file written next to the vector db (`running` → `complete` phases). */

package/dist/transformers-provider.d.ts

@@ -3,8 +3,8 @@
  * feature-extraction pipeline as a sage `EmbeddingProvider`.
  *
  * The provider is lazy: nothing is imported until `embed()` is first called.
- * If `@huggingface/transformers` is not installed (it's listed as an
- * optionalDependency), `isAvailable()` returns false and `embed()` throws
+ * If the opt-in `@huggingface/transformers` package is not installed,
+ * `isAvailable()` returns false and `embed()` throws
  * a descriptive `VectorMemoryProviderUnavailableError` so callers can
  * fall back to `HashingEmbeddingProvider`.
  *

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wrongstack/vector-memory",
-  "version": "1.0.2",
+  "version": "1.0.4",
   "license": "MIT",
   "description": "WrongStack Vector Memory — an additional vector-search memory store powered by @huggingface/transformers (local ONNX embeddings), alongside the SAGE lexical memory system.",
   "repository": {
@@ -27,12 +27,9 @@
     "README.md"
   ],
   "dependencies": {
-    "@wrongstack/core": "1.0.2",
-    "@wrongstack/persistence": "1.0.2",
-    "@wrongstack/sage": "1.0.2"
-  },
-  "optionalDependencies": {
-    "@huggingface/transformers": "^4.2.0"
+    "@wrongstack/core": "1.0.4",
+    "@wrongstack/persistence": "1.0.4",
+    "@wrongstack/sage": "1.0.4"
   },
   "devDependencies": {
     "@types/node": "^26.2.0",
@@ -45,7 +42,7 @@
   },
   "scripts": {
     "build": "node ../../scripts/build-package.mjs",
-    "typecheck": "tsc --noEmit && tsc --noEmit -p tsconfig.test.json",
+    "typecheck": "tsc --noEmit",
     "test": "vitest run",
     "test:integration": "WRONGSTACK_VECTOR_INTEGRATION=1 vitest run tests/integration.test.ts",
     "clean": "node -e \"require('node:fs').rmSync('dist',{recursive:true,force:true})\""