- Wire PluginRegistry into Brainy init() with provider resolution for distance,
metadataIndex, graphIndex, embeddings, roaring, msgpack, and storage adapters
- Add setupStorage() factory that resolves storage:* providers from plugins before
falling back to built-in createStorage()
- Export internals API (setGlobalCache, UnifiedCache, EntityIdMapper, etc.) for
cortex plugin consumption
- Add plugin.test.ts verifying registration, activation, and provider resolution
- Deprecate browser support (OPFS, Web Workers, WASM embeddings) with warnings
in preparation for v8.0 server-only release
- FileSystemStorage: fix setupStorage resolution for mmap-filesystem provider
Fixed confusing messaging where comments mentioned Node 24 while actual requirement is Node 22:
- environment.ts: Fixed areWorkerThreadsAvailableSync() to check for >= 22 instead of >= 24
- workerUtils.ts: Updated comments to reference Node.js 22 LTS instead of 24
- embedding.ts: Updated ONNX threading comment to reference Node.js 22 LTS
Why Node 22 not Node 24:
- ONNX Runtime has stability issues in Node 24 (V8 HandleScope crashes)
- Node 22 LTS provides maximum stability with our embedding model
- These stale Node 24 references were causing user confusion
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>