David Snelling
8f4787bb10
A native graph provider cold-loads its source->target adjacency lazily, so isReady() would report false at the rebuild gate on a cold open and force a spurious rebuild (failing the §7.1 rebuild()==0 acceptance). Add an OPTIONAL GraphIndexProvider.init() (mirrors MetadataIndexProvider.init) and call it during init, AFTER metadataIndex.init() (id-mapper hydrated first, so a native int adjacency resolves endpoints through it) and BEFORE rebuildIndexesIfNeeded. The JS graph index omits init() and self-loads on demand, so the JS path is unchanged. |
||
|---|---|---|
| .. | ||
| aggregation | ||
| cli | ||
| db | ||
| embeddings | ||
| errors | ||
| graph | ||
| hnsw | ||
| import | ||
| importers | ||
| indexes/columnStore | ||
| integrations | ||
| mcp | ||
| migration | ||
| neural | ||
| patterns | ||
| storage | ||
| streaming | ||
| transaction | ||
| triple | ||
| types | ||
| universal | ||
| utils | ||
| vfs | ||
| brainy.ts | ||
| coreTypes.ts | ||
| index.ts | ||
| internals.ts | ||
| plugin.ts | ||
| setup.ts | ||