The optional native graph-acceleration provider exposes `isInitialized`, which is false during its cold-start / rebuild window (engine + cursor not yet loaded). The accessor cached the resolved provider INSTANCE but never re-checked readiness, so `brain.graph.*` could dispatch to a not-ready provider and throw instead of answering. Resolve and cache the instance once, but check `isInitialized` LIVE on every call: route to the pure-TS analytics path while the provider is not ready, and re-engage the native path automatically the moment it flips true. This gates every native route at once — subgraph, export, rank, communities, path, and the query→expand fusion. Adds a test asserting the provider is never called (and the TS fallback returns real answers) while not ready. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| api | ||
| benchmarks | ||
| comprehensive | ||
| configs | ||
| fixtures/import | ||
| helpers | ||
| integration | ||
| integrations | ||
| performance | ||
| regression | ||
| scripts | ||
| transaction | ||
| unit | ||
| vfs | ||
| brainy-3.test.ts | ||
| critical-error-handling.test.ts | ||
| critical-neural-validation.test.ts | ||
| critical-performance-benchmark.test.ts | ||
| model-loading.test.ts | ||
| package-size-breakdown.test.ts | ||
| package-size-limit.test.ts | ||
| setup-integration.ts | ||
| setup-semantic.ts | ||
| setup-unit.ts | ||
| setup.ts | ||
| streaming-pipeline.test.ts | ||
| type-utils.test.ts | ||