brainy/tests/integration/find-where-zero.test.ts

220 lines
9.1 KiB
TypeScript
Raw Permalink Normal View History

fix: find()/stats() correctness + Cortex compat (BR-FIND-WHERE-ZERO, BR-DEFENSIVE-INTERFACE) Two production correctness defects fixed together so consumers can land one upgrade. BR-FIND-WHERE-ZERO — find() returned [] and stats() reported 0 entities for any workspace whose data was written after the 7.20.0 column-store refactor. Root cause: getStats() and the getIds() fallback still read from the deleted sparse-index path. Separately, BaseStorage.getNounType() was hardcoded to return 'thing', poisoning type-statistics.json with every noun attributed to that bucket. - MetadataIndex.getStats() reads from ColumnStore + idMapper. - MetadataIndex.getIdsFromChunks() throws BrainyError(FIELD_NOT_INDEXED) when neither store has the field. getIdsForFilter() catches per clause, logs once, returns []. - BaseStorage.nounTypeByIdCache populated in saveNounMetadata_internal and consumed in saveNoun_internal. flushCounts() now persists the Uint32Array counters too, so readers see fresh per-type counts. - Self-heal at init: loadTypeStatistics() auto-rebuilds when the poisoned signature is detected. rebuildTypeCounts() is now public for use from `brainy inspect repair`. - Dead state removed: dirtyChunks, dirtySparseIndices, flushDirtyMetadata(). BR-DEFENSIVE-INTERFACE — 7.21.0 called supportsMultiProcessLocking() unconditionally, crashing on older Cortex storage adapters that predate the method. New hasStorageMethod(name) helper gates every new-method call site. Older adapter triggers a one-line warning at init pointing at the recommended plugin version. Tests: - new tests/integration/find-where-zero.test.ts (7 cases) - new tests/integration/cortex-compat.test.ts (5 cases) - multi-process-safety.test.ts updated to enforce correct counts - 1329/1329 unit + 24/24 new integration tests passing
2026-05-15 12:31:28 -07:00
/**
* BR-FIND-WHERE-ZERO regression test.
*
* Pre-7.22.0, the following failed silently:
* - Writer adds N entities of various types and flushes.
* - A fresh reader opens the same directory.
* - reader.find({ where: { ... } }) returned [].
* - reader.stats().entityCount returned 0.
* - reader.stats().entitiesByType reported all entities as 'thing'.
*
* Root cause was twofold:
* 1. The 7.20.0 column-store refactor deleted the sparse-index write path
* but left getStats() and the getIds()-fallback reading from sparse
* indices. New workspaces have no sparse-index files, so both surfaces
* returned 0 / [].
* 2. BaseStorage.getNounType() was hardcoded to return 'thing' after a
* type-cache removal, poisoning _system/type-statistics.json.
*
* 7.22.0 fix: getStats() reads from ColumnStore + idMapper, getIds() throws
* FIELD_NOT_INDEXED instead of silently returning [], and getNounType() reads
* from a write-time nounTypeByIdCache populated in saveNounMetadata_internal.
*/
import { describe, it, expect, beforeEach, afterEach } from 'vitest'
import { mkdtempSync, rmSync } from 'node:fs'
import { tmpdir } from 'node:os'
import { join } from 'node:path'
import { Brainy } from '../../src/brainy.js'
import { NounType } from '../../src/types/graphTypes.js'
import { BrainyError } from '../../src/errors/brainyError.js'
function makeTempDir(): string {
return mkdtempSync(join(tmpdir(), 'brainy-fwz-'))
}
describe('BR-FIND-WHERE-ZERO regression', () => {
let dir: string
let writer: Brainy | null = null
let reader: Brainy | null = null
beforeEach(() => {
dir = makeTempDir()
})
afterEach(async () => {
if (writer) {
try { await writer.close() } catch { /* may already be closed */ }
writer = null
}
if (reader) {
try { await reader.close() } catch { /* may already be closed */ }
reader = null
}
try { rmSync(dir, { recursive: true, force: true }) } catch { /* ignore */ }
})
describe('Reader sees correct entity counts after writer cold-start', () => {
it('preserves entity count across writer→close→reader-open', async () => {
feat(8.0): API simplification — remove neural()/Db.search, one storage `path` key, integration→0 8.0 RC cleanup toward "one place per thing, zero-config, no deprecation": - Remove the `brain.neural()` clustering namespace (ImprovedNeuralAPI + the dead legacy NeuralAPI + the neural CLI + neural-only types). Similarity is `find({vector})` / `similar({to})`; attribute grouping is the aggregation `GROUP BY` engine. The separate entity-extraction / smart-import feature (NeuralImport, NeuralEntityExtractor, SmartExtractor, NaturalLanguageProcessor, `brain.extract()`/`brain.nlp()`) is kept. - Remove `Db.search()`; `find()` is the one query verb (accepts a bare string or FindParams). Fix the bundled MCP client, which called a non-existent `brain.search(query, limit)` → now `find({ query, limit })`. - Storage config: collapse to one canonical top-level `path` key. The pre-8.0 aliases (`rootDirectory`, `options.*`, `fileSystemStorage.*`) are removed and now THROW with the exact rename instead of silently defaulting to `./brainy-data` on upgrade. A single resolver feeds createStorage, the 7.x→8.0 migration probe, and the plugin-factory handoff, so a native storage provider resolves the identical root (no split-brain). - Fix `similar({ threshold })`: the min-similarity filter was silently dropped; it is now applied as a post-filter on `result.score` (the documented way to bound semantic results). - Fix `vfs.rename()` on a directory: child path updates spread the entity vector into `update()` and failed dimension validation; they are metadata-only updates now. - Fix `vfs.move()`: copy+delete orphaned the content-addressed content blob (the destination shared the source hash, then unlink removed it). `move()` now delegates to `rename()` — an in-place path change that preserves the blob and the entity id, for files and directories. - Fix streaming import: the bulk fast path never flushed mid-import nor signalled queryability. Entity writes are now chunked by a progressive flush interval (100 → 1000 → 5000); each chunk flushes and emits `progress.queryable`, so imported data is queryable during the import. - Sweep all docs, comments, and JSDoc for the removed/changed APIs. Integration suite: 49 files / 588 passed / 0 failed. Unit: 80 files / 1456 passed, no type errors.
2026-06-20 13:31:11 -07:00
writer = new Brainy({ requireSubtype: false, storage: { type: 'filesystem', path: dir }, silent: true })
fix: find()/stats() correctness + Cortex compat (BR-FIND-WHERE-ZERO, BR-DEFENSIVE-INTERFACE) Two production correctness defects fixed together so consumers can land one upgrade. BR-FIND-WHERE-ZERO — find() returned [] and stats() reported 0 entities for any workspace whose data was written after the 7.20.0 column-store refactor. Root cause: getStats() and the getIds() fallback still read from the deleted sparse-index path. Separately, BaseStorage.getNounType() was hardcoded to return 'thing', poisoning type-statistics.json with every noun attributed to that bucket. - MetadataIndex.getStats() reads from ColumnStore + idMapper. - MetadataIndex.getIdsFromChunks() throws BrainyError(FIELD_NOT_INDEXED) when neither store has the field. getIdsForFilter() catches per clause, logs once, returns []. - BaseStorage.nounTypeByIdCache populated in saveNounMetadata_internal and consumed in saveNoun_internal. flushCounts() now persists the Uint32Array counters too, so readers see fresh per-type counts. - Self-heal at init: loadTypeStatistics() auto-rebuilds when the poisoned signature is detected. rebuildTypeCounts() is now public for use from `brainy inspect repair`. - Dead state removed: dirtyChunks, dirtySparseIndices, flushDirtyMetadata(). BR-DEFENSIVE-INTERFACE — 7.21.0 called supportsMultiProcessLocking() unconditionally, crashing on older Cortex storage adapters that predate the method. New hasStorageMethod(name) helper gates every new-method call site. Older adapter triggers a one-line warning at init pointing at the recommended plugin version. Tests: - new tests/integration/find-where-zero.test.ts (7 cases) - new tests/integration/cortex-compat.test.ts (5 cases) - multi-process-safety.test.ts updated to enforce correct counts - 1329/1329 unit + 24/24 new integration tests passing
2026-05-15 12:31:28 -07:00
await writer.init()
const writerIds = new Set<string>()
for (let i = 0; i < 10; i++) {
const id = await writer.add({ data: `alpha-${i}-payload`, type: NounType.Concept })
writerIds.add(id)
}
await writer.flush()
await writer.close()
writer = null
reader = await Brainy.openReadOnly({
feat(8.0): API simplification — remove neural()/Db.search, one storage `path` key, integration→0 8.0 RC cleanup toward "one place per thing, zero-config, no deprecation": - Remove the `brain.neural()` clustering namespace (ImprovedNeuralAPI + the dead legacy NeuralAPI + the neural CLI + neural-only types). Similarity is `find({vector})` / `similar({to})`; attribute grouping is the aggregation `GROUP BY` engine. The separate entity-extraction / smart-import feature (NeuralImport, NeuralEntityExtractor, SmartExtractor, NaturalLanguageProcessor, `brain.extract()`/`brain.nlp()`) is kept. - Remove `Db.search()`; `find()` is the one query verb (accepts a bare string or FindParams). Fix the bundled MCP client, which called a non-existent `brain.search(query, limit)` → now `find({ query, limit })`. - Storage config: collapse to one canonical top-level `path` key. The pre-8.0 aliases (`rootDirectory`, `options.*`, `fileSystemStorage.*`) are removed and now THROW with the exact rename instead of silently defaulting to `./brainy-data` on upgrade. A single resolver feeds createStorage, the 7.x→8.0 migration probe, and the plugin-factory handoff, so a native storage provider resolves the identical root (no split-brain). - Fix `similar({ threshold })`: the min-similarity filter was silently dropped; it is now applied as a post-filter on `result.score` (the documented way to bound semantic results). - Fix `vfs.rename()` on a directory: child path updates spread the entity vector into `update()` and failed dimension validation; they are metadata-only updates now. - Fix `vfs.move()`: copy+delete orphaned the content-addressed content blob (the destination shared the source hash, then unlink removed it). `move()` now delegates to `rename()` — an in-place path change that preserves the blob and the entity id, for files and directories. - Fix streaming import: the bulk fast path never flushed mid-import nor signalled queryability. Entity writes are now chunked by a progressive flush interval (100 → 1000 → 5000); each chunk flushes and emits `progress.queryable`, so imported data is queryable during the import. - Sweep all docs, comments, and JSDoc for the removed/changed APIs. Integration suite: 49 files / 588 passed / 0 failed. Unit: 80 files / 1456 passed, no type errors.
2026-06-20 13:31:11 -07:00
storage: { type: 'filesystem', path: dir }
fix: find()/stats() correctness + Cortex compat (BR-FIND-WHERE-ZERO, BR-DEFENSIVE-INTERFACE) Two production correctness defects fixed together so consumers can land one upgrade. BR-FIND-WHERE-ZERO — find() returned [] and stats() reported 0 entities for any workspace whose data was written after the 7.20.0 column-store refactor. Root cause: getStats() and the getIds() fallback still read from the deleted sparse-index path. Separately, BaseStorage.getNounType() was hardcoded to return 'thing', poisoning type-statistics.json with every noun attributed to that bucket. - MetadataIndex.getStats() reads from ColumnStore + idMapper. - MetadataIndex.getIdsFromChunks() throws BrainyError(FIELD_NOT_INDEXED) when neither store has the field. getIdsForFilter() catches per clause, logs once, returns []. - BaseStorage.nounTypeByIdCache populated in saveNounMetadata_internal and consumed in saveNoun_internal. flushCounts() now persists the Uint32Array counters too, so readers see fresh per-type counts. - Self-heal at init: loadTypeStatistics() auto-rebuilds when the poisoned signature is detected. rebuildTypeCounts() is now public for use from `brainy inspect repair`. - Dead state removed: dirtyChunks, dirtySparseIndices, flushDirtyMetadata(). BR-DEFENSIVE-INTERFACE — 7.21.0 called supportsMultiProcessLocking() unconditionally, crashing on older Cortex storage adapters that predate the method. New hasStorageMethod(name) helper gates every new-method call site. Older adapter triggers a one-line warning at init pointing at the recommended plugin version. Tests: - new tests/integration/find-where-zero.test.ts (7 cases) - new tests/integration/cortex-compat.test.ts (5 cases) - multi-process-safety.test.ts updated to enforce correct counts - 1329/1329 unit + 24/24 new integration tests passing
2026-05-15 12:31:28 -07:00
})
// find() must return every entity we explicitly added — the historical
// bug was 0 results despite N being on disk. Anything beyond N from
// auto-extraction or VFS init is acceptable; the minimum guarantee is
// that no user-added entity is silently dropped.
const all = await reader.find({ type: NounType.Concept, limit: 1000 })
const recovered = all.filter(e => writerIds.has(e.id)).map(e => e.id)
expect(recovered.length).toBe(10)
})
it('preserves type classification (no "all entities are thing" poisoning)', async () => {
feat(8.0): API simplification — remove neural()/Db.search, one storage `path` key, integration→0 8.0 RC cleanup toward "one place per thing, zero-config, no deprecation": - Remove the `brain.neural()` clustering namespace (ImprovedNeuralAPI + the dead legacy NeuralAPI + the neural CLI + neural-only types). Similarity is `find({vector})` / `similar({to})`; attribute grouping is the aggregation `GROUP BY` engine. The separate entity-extraction / smart-import feature (NeuralImport, NeuralEntityExtractor, SmartExtractor, NaturalLanguageProcessor, `brain.extract()`/`brain.nlp()`) is kept. - Remove `Db.search()`; `find()` is the one query verb (accepts a bare string or FindParams). Fix the bundled MCP client, which called a non-existent `brain.search(query, limit)` → now `find({ query, limit })`. - Storage config: collapse to one canonical top-level `path` key. The pre-8.0 aliases (`rootDirectory`, `options.*`, `fileSystemStorage.*`) are removed and now THROW with the exact rename instead of silently defaulting to `./brainy-data` on upgrade. A single resolver feeds createStorage, the 7.x→8.0 migration probe, and the plugin-factory handoff, so a native storage provider resolves the identical root (no split-brain). - Fix `similar({ threshold })`: the min-similarity filter was silently dropped; it is now applied as a post-filter on `result.score` (the documented way to bound semantic results). - Fix `vfs.rename()` on a directory: child path updates spread the entity vector into `update()` and failed dimension validation; they are metadata-only updates now. - Fix `vfs.move()`: copy+delete orphaned the content-addressed content blob (the destination shared the source hash, then unlink removed it). `move()` now delegates to `rename()` — an in-place path change that preserves the blob and the entity id, for files and directories. - Fix streaming import: the bulk fast path never flushed mid-import nor signalled queryability. Entity writes are now chunked by a progressive flush interval (100 → 1000 → 5000); each chunk flushes and emits `progress.queryable`, so imported data is queryable during the import. - Sweep all docs, comments, and JSDoc for the removed/changed APIs. Integration suite: 49 files / 588 passed / 0 failed. Unit: 80 files / 1456 passed, no type errors.
2026-06-20 13:31:11 -07:00
writer = new Brainy({ requireSubtype: false, storage: { type: 'filesystem', path: dir }, silent: true })
fix: find()/stats() correctness + Cortex compat (BR-FIND-WHERE-ZERO, BR-DEFENSIVE-INTERFACE) Two production correctness defects fixed together so consumers can land one upgrade. BR-FIND-WHERE-ZERO — find() returned [] and stats() reported 0 entities for any workspace whose data was written after the 7.20.0 column-store refactor. Root cause: getStats() and the getIds() fallback still read from the deleted sparse-index path. Separately, BaseStorage.getNounType() was hardcoded to return 'thing', poisoning type-statistics.json with every noun attributed to that bucket. - MetadataIndex.getStats() reads from ColumnStore + idMapper. - MetadataIndex.getIdsFromChunks() throws BrainyError(FIELD_NOT_INDEXED) when neither store has the field. getIdsForFilter() catches per clause, logs once, returns []. - BaseStorage.nounTypeByIdCache populated in saveNounMetadata_internal and consumed in saveNoun_internal. flushCounts() now persists the Uint32Array counters too, so readers see fresh per-type counts. - Self-heal at init: loadTypeStatistics() auto-rebuilds when the poisoned signature is detected. rebuildTypeCounts() is now public for use from `brainy inspect repair`. - Dead state removed: dirtyChunks, dirtySparseIndices, flushDirtyMetadata(). BR-DEFENSIVE-INTERFACE — 7.21.0 called supportsMultiProcessLocking() unconditionally, crashing on older Cortex storage adapters that predate the method. New hasStorageMethod(name) helper gates every new-method call site. Older adapter triggers a one-line warning at init pointing at the recommended plugin version. Tests: - new tests/integration/find-where-zero.test.ts (7 cases) - new tests/integration/cortex-compat.test.ts (5 cases) - multi-process-safety.test.ts updated to enforce correct counts - 1329/1329 unit + 24/24 new integration tests passing
2026-05-15 12:31:28 -07:00
await writer.init()
// Three types. Each id is tracked individually so we don't conflate
// user-added entities with whatever VFS / auto-extraction inserts.
const conceptIds = new Set<string>()
const eventIds = new Set<string>()
const docIds = new Set<string>()
for (let i = 0; i < 3; i++) conceptIds.add(await writer.add({ data: `alpha-${i}`, type: NounType.Concept }))
for (let i = 0; i < 5; i++) eventIds.add(await writer.add({ data: `beta-${i}`, type: NounType.Event }))
for (let i = 0; i < 2; i++) docIds.add(await writer.add({ data: `gamma-${i}`, type: NounType.Document }))
await writer.flush()
await writer.close()
writer = null
reader = await Brainy.openReadOnly({
feat(8.0): API simplification — remove neural()/Db.search, one storage `path` key, integration→0 8.0 RC cleanup toward "one place per thing, zero-config, no deprecation": - Remove the `brain.neural()` clustering namespace (ImprovedNeuralAPI + the dead legacy NeuralAPI + the neural CLI + neural-only types). Similarity is `find({vector})` / `similar({to})`; attribute grouping is the aggregation `GROUP BY` engine. The separate entity-extraction / smart-import feature (NeuralImport, NeuralEntityExtractor, SmartExtractor, NaturalLanguageProcessor, `brain.extract()`/`brain.nlp()`) is kept. - Remove `Db.search()`; `find()` is the one query verb (accepts a bare string or FindParams). Fix the bundled MCP client, which called a non-existent `brain.search(query, limit)` → now `find({ query, limit })`. - Storage config: collapse to one canonical top-level `path` key. The pre-8.0 aliases (`rootDirectory`, `options.*`, `fileSystemStorage.*`) are removed and now THROW with the exact rename instead of silently defaulting to `./brainy-data` on upgrade. A single resolver feeds createStorage, the 7.x→8.0 migration probe, and the plugin-factory handoff, so a native storage provider resolves the identical root (no split-brain). - Fix `similar({ threshold })`: the min-similarity filter was silently dropped; it is now applied as a post-filter on `result.score` (the documented way to bound semantic results). - Fix `vfs.rename()` on a directory: child path updates spread the entity vector into `update()` and failed dimension validation; they are metadata-only updates now. - Fix `vfs.move()`: copy+delete orphaned the content-addressed content blob (the destination shared the source hash, then unlink removed it). `move()` now delegates to `rename()` — an in-place path change that preserves the blob and the entity id, for files and directories. - Fix streaming import: the bulk fast path never flushed mid-import nor signalled queryability. Entity writes are now chunked by a progressive flush interval (100 → 1000 → 5000); each chunk flushes and emits `progress.queryable`, so imported data is queryable during the import. - Sweep all docs, comments, and JSDoc for the removed/changed APIs. Integration suite: 49 files / 588 passed / 0 failed. Unit: 80 files / 1456 passed, no type errors.
2026-06-20 13:31:11 -07:00
storage: { type: 'filesystem', path: dir }
fix: find()/stats() correctness + Cortex compat (BR-FIND-WHERE-ZERO, BR-DEFENSIVE-INTERFACE) Two production correctness defects fixed together so consumers can land one upgrade. BR-FIND-WHERE-ZERO — find() returned [] and stats() reported 0 entities for any workspace whose data was written after the 7.20.0 column-store refactor. Root cause: getStats() and the getIds() fallback still read from the deleted sparse-index path. Separately, BaseStorage.getNounType() was hardcoded to return 'thing', poisoning type-statistics.json with every noun attributed to that bucket. - MetadataIndex.getStats() reads from ColumnStore + idMapper. - MetadataIndex.getIdsFromChunks() throws BrainyError(FIELD_NOT_INDEXED) when neither store has the field. getIdsForFilter() catches per clause, logs once, returns []. - BaseStorage.nounTypeByIdCache populated in saveNounMetadata_internal and consumed in saveNoun_internal. flushCounts() now persists the Uint32Array counters too, so readers see fresh per-type counts. - Self-heal at init: loadTypeStatistics() auto-rebuilds when the poisoned signature is detected. rebuildTypeCounts() is now public for use from `brainy inspect repair`. - Dead state removed: dirtyChunks, dirtySparseIndices, flushDirtyMetadata(). BR-DEFENSIVE-INTERFACE — 7.21.0 called supportsMultiProcessLocking() unconditionally, crashing on older Cortex storage adapters that predate the method. New hasStorageMethod(name) helper gates every new-method call site. Older adapter triggers a one-line warning at init pointing at the recommended plugin version. Tests: - new tests/integration/find-where-zero.test.ts (7 cases) - new tests/integration/cortex-compat.test.ts (5 cases) - multi-process-safety.test.ts updated to enforce correct counts - 1329/1329 unit + 24/24 new integration tests passing
2026-05-15 12:31:28 -07:00
})
// Every user-added id is recoverable when querying by its declared
// type. Pre-7.22 this failed because counts said 0 entries (which the
// rebuild trigger acted on) or all entities were attributed to 'thing'.
const concepts = await reader.find({ type: NounType.Concept, limit: 1000 })
const events = await reader.find({ type: NounType.Event, limit: 1000 })
const docs = await reader.find({ type: NounType.Document, limit: 1000 })
expect(concepts.filter(e => conceptIds.has(e.id)).length).toBe(3)
expect(events.filter(e => eventIds.has(e.id)).length).toBe(5)
expect(docs.filter(e => docIds.has(e.id)).length).toBe(2)
// None of the user-added entities should leak into the 'thing' bucket.
const things = await reader.find({ type: NounType.Thing, limit: 1000 })
const userInThings = things.filter(
e => conceptIds.has(e.id) || eventIds.has(e.id) || docIds.has(e.id)
)
expect(userInThings.length).toBe(0)
})
})
describe('find() consistency', () => {
it('returns entities that exist on disk (not silent empty)', async () => {
feat(8.0): API simplification — remove neural()/Db.search, one storage `path` key, integration→0 8.0 RC cleanup toward "one place per thing, zero-config, no deprecation": - Remove the `brain.neural()` clustering namespace (ImprovedNeuralAPI + the dead legacy NeuralAPI + the neural CLI + neural-only types). Similarity is `find({vector})` / `similar({to})`; attribute grouping is the aggregation `GROUP BY` engine. The separate entity-extraction / smart-import feature (NeuralImport, NeuralEntityExtractor, SmartExtractor, NaturalLanguageProcessor, `brain.extract()`/`brain.nlp()`) is kept. - Remove `Db.search()`; `find()` is the one query verb (accepts a bare string or FindParams). Fix the bundled MCP client, which called a non-existent `brain.search(query, limit)` → now `find({ query, limit })`. - Storage config: collapse to one canonical top-level `path` key. The pre-8.0 aliases (`rootDirectory`, `options.*`, `fileSystemStorage.*`) are removed and now THROW with the exact rename instead of silently defaulting to `./brainy-data` on upgrade. A single resolver feeds createStorage, the 7.x→8.0 migration probe, and the plugin-factory handoff, so a native storage provider resolves the identical root (no split-brain). - Fix `similar({ threshold })`: the min-similarity filter was silently dropped; it is now applied as a post-filter on `result.score` (the documented way to bound semantic results). - Fix `vfs.rename()` on a directory: child path updates spread the entity vector into `update()` and failed dimension validation; they are metadata-only updates now. - Fix `vfs.move()`: copy+delete orphaned the content-addressed content blob (the destination shared the source hash, then unlink removed it). `move()` now delegates to `rename()` — an in-place path change that preserves the blob and the entity id, for files and directories. - Fix streaming import: the bulk fast path never flushed mid-import nor signalled queryability. Entity writes are now chunked by a progressive flush interval (100 → 1000 → 5000); each chunk flushes and emits `progress.queryable`, so imported data is queryable during the import. - Sweep all docs, comments, and JSDoc for the removed/changed APIs. Integration suite: 49 files / 588 passed / 0 failed. Unit: 80 files / 1456 passed, no type errors.
2026-06-20 13:31:11 -07:00
writer = new Brainy({ requireSubtype: false, storage: { type: 'filesystem', path: dir }, silent: true })
fix: find()/stats() correctness + Cortex compat (BR-FIND-WHERE-ZERO, BR-DEFENSIVE-INTERFACE) Two production correctness defects fixed together so consumers can land one upgrade. BR-FIND-WHERE-ZERO — find() returned [] and stats() reported 0 entities for any workspace whose data was written after the 7.20.0 column-store refactor. Root cause: getStats() and the getIds() fallback still read from the deleted sparse-index path. Separately, BaseStorage.getNounType() was hardcoded to return 'thing', poisoning type-statistics.json with every noun attributed to that bucket. - MetadataIndex.getStats() reads from ColumnStore + idMapper. - MetadataIndex.getIdsFromChunks() throws BrainyError(FIELD_NOT_INDEXED) when neither store has the field. getIdsForFilter() catches per clause, logs once, returns []. - BaseStorage.nounTypeByIdCache populated in saveNounMetadata_internal and consumed in saveNoun_internal. flushCounts() now persists the Uint32Array counters too, so readers see fresh per-type counts. - Self-heal at init: loadTypeStatistics() auto-rebuilds when the poisoned signature is detected. rebuildTypeCounts() is now public for use from `brainy inspect repair`. - Dead state removed: dirtyChunks, dirtySparseIndices, flushDirtyMetadata(). BR-DEFENSIVE-INTERFACE — 7.21.0 called supportsMultiProcessLocking() unconditionally, crashing on older Cortex storage adapters that predate the method. New hasStorageMethod(name) helper gates every new-method call site. Older adapter triggers a one-line warning at init pointing at the recommended plugin version. Tests: - new tests/integration/find-where-zero.test.ts (7 cases) - new tests/integration/cortex-compat.test.ts (5 cases) - multi-process-safety.test.ts updated to enforce correct counts - 1329/1329 unit + 24/24 new integration tests passing
2026-05-15 12:31:28 -07:00
await writer.init()
const conceptIds: string[] = []
for (let i = 0; i < 4; i++) {
const id = await writer.add({
data: `entity ${i}`,
type: NounType.Concept,
metadata: { entityType: 'booking', status: i % 2 === 0 ? 'paid' : 'pending' }
})
conceptIds.push(id)
}
await writer.flush()
await writer.close()
writer = null
reader = await Brainy.openReadOnly({
feat(8.0): API simplification — remove neural()/Db.search, one storage `path` key, integration→0 8.0 RC cleanup toward "one place per thing, zero-config, no deprecation": - Remove the `brain.neural()` clustering namespace (ImprovedNeuralAPI + the dead legacy NeuralAPI + the neural CLI + neural-only types). Similarity is `find({vector})` / `similar({to})`; attribute grouping is the aggregation `GROUP BY` engine. The separate entity-extraction / smart-import feature (NeuralImport, NeuralEntityExtractor, SmartExtractor, NaturalLanguageProcessor, `brain.extract()`/`brain.nlp()`) is kept. - Remove `Db.search()`; `find()` is the one query verb (accepts a bare string or FindParams). Fix the bundled MCP client, which called a non-existent `brain.search(query, limit)` → now `find({ query, limit })`. - Storage config: collapse to one canonical top-level `path` key. The pre-8.0 aliases (`rootDirectory`, `options.*`, `fileSystemStorage.*`) are removed and now THROW with the exact rename instead of silently defaulting to `./brainy-data` on upgrade. A single resolver feeds createStorage, the 7.x→8.0 migration probe, and the plugin-factory handoff, so a native storage provider resolves the identical root (no split-brain). - Fix `similar({ threshold })`: the min-similarity filter was silently dropped; it is now applied as a post-filter on `result.score` (the documented way to bound semantic results). - Fix `vfs.rename()` on a directory: child path updates spread the entity vector into `update()` and failed dimension validation; they are metadata-only updates now. - Fix `vfs.move()`: copy+delete orphaned the content-addressed content blob (the destination shared the source hash, then unlink removed it). `move()` now delegates to `rename()` — an in-place path change that preserves the blob and the entity id, for files and directories. - Fix streaming import: the bulk fast path never flushed mid-import nor signalled queryability. Entity writes are now chunked by a progressive flush interval (100 → 1000 → 5000); each chunk flushes and emits `progress.queryable`, so imported data is queryable during the import. - Sweep all docs, comments, and JSDoc for the removed/changed APIs. Integration suite: 49 files / 588 passed / 0 failed. Unit: 80 files / 1456 passed, no type errors.
2026-06-20 13:31:11 -07:00
storage: { type: 'filesystem', path: dir }
fix: find()/stats() correctness + Cortex compat (BR-FIND-WHERE-ZERO, BR-DEFENSIVE-INTERFACE) Two production correctness defects fixed together so consumers can land one upgrade. BR-FIND-WHERE-ZERO — find() returned [] and stats() reported 0 entities for any workspace whose data was written after the 7.20.0 column-store refactor. Root cause: getStats() and the getIds() fallback still read from the deleted sparse-index path. Separately, BaseStorage.getNounType() was hardcoded to return 'thing', poisoning type-statistics.json with every noun attributed to that bucket. - MetadataIndex.getStats() reads from ColumnStore + idMapper. - MetadataIndex.getIdsFromChunks() throws BrainyError(FIELD_NOT_INDEXED) when neither store has the field. getIdsForFilter() catches per clause, logs once, returns []. - BaseStorage.nounTypeByIdCache populated in saveNounMetadata_internal and consumed in saveNoun_internal. flushCounts() now persists the Uint32Array counters too, so readers see fresh per-type counts. - Self-heal at init: loadTypeStatistics() auto-rebuilds when the poisoned signature is detected. rebuildTypeCounts() is now public for use from `brainy inspect repair`. - Dead state removed: dirtyChunks, dirtySparseIndices, flushDirtyMetadata(). BR-DEFENSIVE-INTERFACE — 7.21.0 called supportsMultiProcessLocking() unconditionally, crashing on older Cortex storage adapters that predate the method. New hasStorageMethod(name) helper gates every new-method call site. Older adapter triggers a one-line warning at init pointing at the recommended plugin version. Tests: - new tests/integration/find-where-zero.test.ts (7 cases) - new tests/integration/cortex-compat.test.ts (5 cases) - multi-process-safety.test.ts updated to enforce correct counts - 1329/1329 unit + 24/24 new integration tests passing
2026-05-15 12:31:28 -07:00
})
const all = await reader.find({ where: { entityType: 'booking' } })
expect(all.length).toBe(4)
const paid = await reader.find({ where: { entityType: 'booking', status: 'paid' } })
expect(paid.length).toBe(2)
})
it('returns [] with a logged warning for unindexed field', async () => {
feat(8.0): API simplification — remove neural()/Db.search, one storage `path` key, integration→0 8.0 RC cleanup toward "one place per thing, zero-config, no deprecation": - Remove the `brain.neural()` clustering namespace (ImprovedNeuralAPI + the dead legacy NeuralAPI + the neural CLI + neural-only types). Similarity is `find({vector})` / `similar({to})`; attribute grouping is the aggregation `GROUP BY` engine. The separate entity-extraction / smart-import feature (NeuralImport, NeuralEntityExtractor, SmartExtractor, NaturalLanguageProcessor, `brain.extract()`/`brain.nlp()`) is kept. - Remove `Db.search()`; `find()` is the one query verb (accepts a bare string or FindParams). Fix the bundled MCP client, which called a non-existent `brain.search(query, limit)` → now `find({ query, limit })`. - Storage config: collapse to one canonical top-level `path` key. The pre-8.0 aliases (`rootDirectory`, `options.*`, `fileSystemStorage.*`) are removed and now THROW with the exact rename instead of silently defaulting to `./brainy-data` on upgrade. A single resolver feeds createStorage, the 7.x→8.0 migration probe, and the plugin-factory handoff, so a native storage provider resolves the identical root (no split-brain). - Fix `similar({ threshold })`: the min-similarity filter was silently dropped; it is now applied as a post-filter on `result.score` (the documented way to bound semantic results). - Fix `vfs.rename()` on a directory: child path updates spread the entity vector into `update()` and failed dimension validation; they are metadata-only updates now. - Fix `vfs.move()`: copy+delete orphaned the content-addressed content blob (the destination shared the source hash, then unlink removed it). `move()` now delegates to `rename()` — an in-place path change that preserves the blob and the entity id, for files and directories. - Fix streaming import: the bulk fast path never flushed mid-import nor signalled queryability. Entity writes are now chunked by a progressive flush interval (100 → 1000 → 5000); each chunk flushes and emits `progress.queryable`, so imported data is queryable during the import. - Sweep all docs, comments, and JSDoc for the removed/changed APIs. Integration suite: 49 files / 588 passed / 0 failed. Unit: 80 files / 1456 passed, no type errors.
2026-06-20 13:31:11 -07:00
writer = new Brainy({ requireSubtype: false, storage: { type: 'filesystem', path: dir }, silent: true })
fix: find()/stats() correctness + Cortex compat (BR-FIND-WHERE-ZERO, BR-DEFENSIVE-INTERFACE) Two production correctness defects fixed together so consumers can land one upgrade. BR-FIND-WHERE-ZERO — find() returned [] and stats() reported 0 entities for any workspace whose data was written after the 7.20.0 column-store refactor. Root cause: getStats() and the getIds() fallback still read from the deleted sparse-index path. Separately, BaseStorage.getNounType() was hardcoded to return 'thing', poisoning type-statistics.json with every noun attributed to that bucket. - MetadataIndex.getStats() reads from ColumnStore + idMapper. - MetadataIndex.getIdsFromChunks() throws BrainyError(FIELD_NOT_INDEXED) when neither store has the field. getIdsForFilter() catches per clause, logs once, returns []. - BaseStorage.nounTypeByIdCache populated in saveNounMetadata_internal and consumed in saveNoun_internal. flushCounts() now persists the Uint32Array counters too, so readers see fresh per-type counts. - Self-heal at init: loadTypeStatistics() auto-rebuilds when the poisoned signature is detected. rebuildTypeCounts() is now public for use from `brainy inspect repair`. - Dead state removed: dirtyChunks, dirtySparseIndices, flushDirtyMetadata(). BR-DEFENSIVE-INTERFACE — 7.21.0 called supportsMultiProcessLocking() unconditionally, crashing on older Cortex storage adapters that predate the method. New hasStorageMethod(name) helper gates every new-method call site. Older adapter triggers a one-line warning at init pointing at the recommended plugin version. Tests: - new tests/integration/find-where-zero.test.ts (7 cases) - new tests/integration/cortex-compat.test.ts (5 cases) - multi-process-safety.test.ts updated to enforce correct counts - 1329/1329 unit + 24/24 new integration tests passing
2026-05-15 12:31:28 -07:00
await writer.init()
await writer.add({ data: 'test', type: NounType.Concept })
await writer.flush()
await writer.close()
writer = null
reader = await Brainy.openReadOnly({
feat(8.0): API simplification — remove neural()/Db.search, one storage `path` key, integration→0 8.0 RC cleanup toward "one place per thing, zero-config, no deprecation": - Remove the `brain.neural()` clustering namespace (ImprovedNeuralAPI + the dead legacy NeuralAPI + the neural CLI + neural-only types). Similarity is `find({vector})` / `similar({to})`; attribute grouping is the aggregation `GROUP BY` engine. The separate entity-extraction / smart-import feature (NeuralImport, NeuralEntityExtractor, SmartExtractor, NaturalLanguageProcessor, `brain.extract()`/`brain.nlp()`) is kept. - Remove `Db.search()`; `find()` is the one query verb (accepts a bare string or FindParams). Fix the bundled MCP client, which called a non-existent `brain.search(query, limit)` → now `find({ query, limit })`. - Storage config: collapse to one canonical top-level `path` key. The pre-8.0 aliases (`rootDirectory`, `options.*`, `fileSystemStorage.*`) are removed and now THROW with the exact rename instead of silently defaulting to `./brainy-data` on upgrade. A single resolver feeds createStorage, the 7.x→8.0 migration probe, and the plugin-factory handoff, so a native storage provider resolves the identical root (no split-brain). - Fix `similar({ threshold })`: the min-similarity filter was silently dropped; it is now applied as a post-filter on `result.score` (the documented way to bound semantic results). - Fix `vfs.rename()` on a directory: child path updates spread the entity vector into `update()` and failed dimension validation; they are metadata-only updates now. - Fix `vfs.move()`: copy+delete orphaned the content-addressed content blob (the destination shared the source hash, then unlink removed it). `move()` now delegates to `rename()` — an in-place path change that preserves the blob and the entity id, for files and directories. - Fix streaming import: the bulk fast path never flushed mid-import nor signalled queryability. Entity writes are now chunked by a progressive flush interval (100 → 1000 → 5000); each chunk flushes and emits `progress.queryable`, so imported data is queryable during the import. - Sweep all docs, comments, and JSDoc for the removed/changed APIs. Integration suite: 49 files / 588 passed / 0 failed. Unit: 80 files / 1456 passed, no type errors.
2026-06-20 13:31:11 -07:00
storage: { type: 'filesystem', path: dir }
fix: find()/stats() correctness + Cortex compat (BR-FIND-WHERE-ZERO, BR-DEFENSIVE-INTERFACE) Two production correctness defects fixed together so consumers can land one upgrade. BR-FIND-WHERE-ZERO — find() returned [] and stats() reported 0 entities for any workspace whose data was written after the 7.20.0 column-store refactor. Root cause: getStats() and the getIds() fallback still read from the deleted sparse-index path. Separately, BaseStorage.getNounType() was hardcoded to return 'thing', poisoning type-statistics.json with every noun attributed to that bucket. - MetadataIndex.getStats() reads from ColumnStore + idMapper. - MetadataIndex.getIdsFromChunks() throws BrainyError(FIELD_NOT_INDEXED) when neither store has the field. getIdsForFilter() catches per clause, logs once, returns []. - BaseStorage.nounTypeByIdCache populated in saveNounMetadata_internal and consumed in saveNoun_internal. flushCounts() now persists the Uint32Array counters too, so readers see fresh per-type counts. - Self-heal at init: loadTypeStatistics() auto-rebuilds when the poisoned signature is detected. rebuildTypeCounts() is now public for use from `brainy inspect repair`. - Dead state removed: dirtyChunks, dirtySparseIndices, flushDirtyMetadata(). BR-DEFENSIVE-INTERFACE — 7.21.0 called supportsMultiProcessLocking() unconditionally, crashing on older Cortex storage adapters that predate the method. New hasStorageMethod(name) helper gates every new-method call site. Older adapter triggers a one-line warning at init pointing at the recommended plugin version. Tests: - new tests/integration/find-where-zero.test.ts (7 cases) - new tests/integration/cortex-compat.test.ts (5 cases) - multi-process-safety.test.ts updated to enforce correct counts - 1329/1329 unit + 24/24 new integration tests passing
2026-05-15 12:31:28 -07:00
})
// Field that has never been written — production find() should degrade
// to [] (caught by getIdsForFilter), not throw upward.
const empty = await reader.find({ where: { nonExistentField: 'value' } })
expect(empty).toEqual([])
})
it('raw getIds() throws BrainyError(FIELD_NOT_INDEXED) for unindexed field', async () => {
feat(8.0): API simplification — remove neural()/Db.search, one storage `path` key, integration→0 8.0 RC cleanup toward "one place per thing, zero-config, no deprecation": - Remove the `brain.neural()` clustering namespace (ImprovedNeuralAPI + the dead legacy NeuralAPI + the neural CLI + neural-only types). Similarity is `find({vector})` / `similar({to})`; attribute grouping is the aggregation `GROUP BY` engine. The separate entity-extraction / smart-import feature (NeuralImport, NeuralEntityExtractor, SmartExtractor, NaturalLanguageProcessor, `brain.extract()`/`brain.nlp()`) is kept. - Remove `Db.search()`; `find()` is the one query verb (accepts a bare string or FindParams). Fix the bundled MCP client, which called a non-existent `brain.search(query, limit)` → now `find({ query, limit })`. - Storage config: collapse to one canonical top-level `path` key. The pre-8.0 aliases (`rootDirectory`, `options.*`, `fileSystemStorage.*`) are removed and now THROW with the exact rename instead of silently defaulting to `./brainy-data` on upgrade. A single resolver feeds createStorage, the 7.x→8.0 migration probe, and the plugin-factory handoff, so a native storage provider resolves the identical root (no split-brain). - Fix `similar({ threshold })`: the min-similarity filter was silently dropped; it is now applied as a post-filter on `result.score` (the documented way to bound semantic results). - Fix `vfs.rename()` on a directory: child path updates spread the entity vector into `update()` and failed dimension validation; they are metadata-only updates now. - Fix `vfs.move()`: copy+delete orphaned the content-addressed content blob (the destination shared the source hash, then unlink removed it). `move()` now delegates to `rename()` — an in-place path change that preserves the blob and the entity id, for files and directories. - Fix streaming import: the bulk fast path never flushed mid-import nor signalled queryability. Entity writes are now chunked by a progressive flush interval (100 → 1000 → 5000); each chunk flushes and emits `progress.queryable`, so imported data is queryable during the import. - Sweep all docs, comments, and JSDoc for the removed/changed APIs. Integration suite: 49 files / 588 passed / 0 failed. Unit: 80 files / 1456 passed, no type errors.
2026-06-20 13:31:11 -07:00
writer = new Brainy({ requireSubtype: false, storage: { type: 'filesystem', path: dir }, silent: true })
fix: find()/stats() correctness + Cortex compat (BR-FIND-WHERE-ZERO, BR-DEFENSIVE-INTERFACE) Two production correctness defects fixed together so consumers can land one upgrade. BR-FIND-WHERE-ZERO — find() returned [] and stats() reported 0 entities for any workspace whose data was written after the 7.20.0 column-store refactor. Root cause: getStats() and the getIds() fallback still read from the deleted sparse-index path. Separately, BaseStorage.getNounType() was hardcoded to return 'thing', poisoning type-statistics.json with every noun attributed to that bucket. - MetadataIndex.getStats() reads from ColumnStore + idMapper. - MetadataIndex.getIdsFromChunks() throws BrainyError(FIELD_NOT_INDEXED) when neither store has the field. getIdsForFilter() catches per clause, logs once, returns []. - BaseStorage.nounTypeByIdCache populated in saveNounMetadata_internal and consumed in saveNoun_internal. flushCounts() now persists the Uint32Array counters too, so readers see fresh per-type counts. - Self-heal at init: loadTypeStatistics() auto-rebuilds when the poisoned signature is detected. rebuildTypeCounts() is now public for use from `brainy inspect repair`. - Dead state removed: dirtyChunks, dirtySparseIndices, flushDirtyMetadata(). BR-DEFENSIVE-INTERFACE — 7.21.0 called supportsMultiProcessLocking() unconditionally, crashing on older Cortex storage adapters that predate the method. New hasStorageMethod(name) helper gates every new-method call site. Older adapter triggers a one-line warning at init pointing at the recommended plugin version. Tests: - new tests/integration/find-where-zero.test.ts (7 cases) - new tests/integration/cortex-compat.test.ts (5 cases) - multi-process-safety.test.ts updated to enforce correct counts - 1329/1329 unit + 24/24 new integration tests passing
2026-05-15 12:31:28 -07:00
await writer.init()
await writer.add({ data: 'test', type: NounType.Concept })
await writer.flush()
// Direct getIds() on the metadata index throws — that's what
// getIdsForFilter() catches. Tests guarantee the contract holds.
const metadataIndex = (writer as any).metadataIndex
await expect(
metadataIndex.getIds('nonExistentField', 'anything')
).rejects.toThrow(BrainyError)
await expect(
metadataIndex.getIds('nonExistentField', 'anything')
).rejects.toMatchObject({ type: 'FIELD_NOT_INDEXED' })
})
})
describe('explain() and health() match the new contract', () => {
it('explain() returns column-store path for indexed fields', async () => {
feat(8.0): API simplification — remove neural()/Db.search, one storage `path` key, integration→0 8.0 RC cleanup toward "one place per thing, zero-config, no deprecation": - Remove the `brain.neural()` clustering namespace (ImprovedNeuralAPI + the dead legacy NeuralAPI + the neural CLI + neural-only types). Similarity is `find({vector})` / `similar({to})`; attribute grouping is the aggregation `GROUP BY` engine. The separate entity-extraction / smart-import feature (NeuralImport, NeuralEntityExtractor, SmartExtractor, NaturalLanguageProcessor, `brain.extract()`/`brain.nlp()`) is kept. - Remove `Db.search()`; `find()` is the one query verb (accepts a bare string or FindParams). Fix the bundled MCP client, which called a non-existent `brain.search(query, limit)` → now `find({ query, limit })`. - Storage config: collapse to one canonical top-level `path` key. The pre-8.0 aliases (`rootDirectory`, `options.*`, `fileSystemStorage.*`) are removed and now THROW with the exact rename instead of silently defaulting to `./brainy-data` on upgrade. A single resolver feeds createStorage, the 7.x→8.0 migration probe, and the plugin-factory handoff, so a native storage provider resolves the identical root (no split-brain). - Fix `similar({ threshold })`: the min-similarity filter was silently dropped; it is now applied as a post-filter on `result.score` (the documented way to bound semantic results). - Fix `vfs.rename()` on a directory: child path updates spread the entity vector into `update()` and failed dimension validation; they are metadata-only updates now. - Fix `vfs.move()`: copy+delete orphaned the content-addressed content blob (the destination shared the source hash, then unlink removed it). `move()` now delegates to `rename()` — an in-place path change that preserves the blob and the entity id, for files and directories. - Fix streaming import: the bulk fast path never flushed mid-import nor signalled queryability. Entity writes are now chunked by a progressive flush interval (100 → 1000 → 5000); each chunk flushes and emits `progress.queryable`, so imported data is queryable during the import. - Sweep all docs, comments, and JSDoc for the removed/changed APIs. Integration suite: 49 files / 588 passed / 0 failed. Unit: 80 files / 1456 passed, no type errors.
2026-06-20 13:31:11 -07:00
writer = new Brainy({ requireSubtype: false, storage: { type: 'filesystem', path: dir }, silent: true })
fix: find()/stats() correctness + Cortex compat (BR-FIND-WHERE-ZERO, BR-DEFENSIVE-INTERFACE) Two production correctness defects fixed together so consumers can land one upgrade. BR-FIND-WHERE-ZERO — find() returned [] and stats() reported 0 entities for any workspace whose data was written after the 7.20.0 column-store refactor. Root cause: getStats() and the getIds() fallback still read from the deleted sparse-index path. Separately, BaseStorage.getNounType() was hardcoded to return 'thing', poisoning type-statistics.json with every noun attributed to that bucket. - MetadataIndex.getStats() reads from ColumnStore + idMapper. - MetadataIndex.getIdsFromChunks() throws BrainyError(FIELD_NOT_INDEXED) when neither store has the field. getIdsForFilter() catches per clause, logs once, returns []. - BaseStorage.nounTypeByIdCache populated in saveNounMetadata_internal and consumed in saveNoun_internal. flushCounts() now persists the Uint32Array counters too, so readers see fresh per-type counts. - Self-heal at init: loadTypeStatistics() auto-rebuilds when the poisoned signature is detected. rebuildTypeCounts() is now public for use from `brainy inspect repair`. - Dead state removed: dirtyChunks, dirtySparseIndices, flushDirtyMetadata(). BR-DEFENSIVE-INTERFACE — 7.21.0 called supportsMultiProcessLocking() unconditionally, crashing on older Cortex storage adapters that predate the method. New hasStorageMethod(name) helper gates every new-method call site. Older adapter triggers a one-line warning at init pointing at the recommended plugin version. Tests: - new tests/integration/find-where-zero.test.ts (7 cases) - new tests/integration/cortex-compat.test.ts (5 cases) - multi-process-safety.test.ts updated to enforce correct counts - 1329/1329 unit + 24/24 new integration tests passing
2026-05-15 12:31:28 -07:00
await writer.init()
await writer.add({
data: 'test',
type: NounType.Concept,
metadata: { entityType: 'booking', priority: 1 }
})
await writer.flush()
const plan = await writer.explain({ where: { entityType: 'booking' } })
expect(plan.fieldPlan).toHaveLength(1)
expect(plan.fieldPlan[0].path).toBe('column-store')
expect(plan.warnings).toEqual([])
})
it('health() reports pass for a clean writer + reader handoff', async () => {
feat(8.0): API simplification — remove neural()/Db.search, one storage `path` key, integration→0 8.0 RC cleanup toward "one place per thing, zero-config, no deprecation": - Remove the `brain.neural()` clustering namespace (ImprovedNeuralAPI + the dead legacy NeuralAPI + the neural CLI + neural-only types). Similarity is `find({vector})` / `similar({to})`; attribute grouping is the aggregation `GROUP BY` engine. The separate entity-extraction / smart-import feature (NeuralImport, NeuralEntityExtractor, SmartExtractor, NaturalLanguageProcessor, `brain.extract()`/`brain.nlp()`) is kept. - Remove `Db.search()`; `find()` is the one query verb (accepts a bare string or FindParams). Fix the bundled MCP client, which called a non-existent `brain.search(query, limit)` → now `find({ query, limit })`. - Storage config: collapse to one canonical top-level `path` key. The pre-8.0 aliases (`rootDirectory`, `options.*`, `fileSystemStorage.*`) are removed and now THROW with the exact rename instead of silently defaulting to `./brainy-data` on upgrade. A single resolver feeds createStorage, the 7.x→8.0 migration probe, and the plugin-factory handoff, so a native storage provider resolves the identical root (no split-brain). - Fix `similar({ threshold })`: the min-similarity filter was silently dropped; it is now applied as a post-filter on `result.score` (the documented way to bound semantic results). - Fix `vfs.rename()` on a directory: child path updates spread the entity vector into `update()` and failed dimension validation; they are metadata-only updates now. - Fix `vfs.move()`: copy+delete orphaned the content-addressed content blob (the destination shared the source hash, then unlink removed it). `move()` now delegates to `rename()` — an in-place path change that preserves the blob and the entity id, for files and directories. - Fix streaming import: the bulk fast path never flushed mid-import nor signalled queryability. Entity writes are now chunked by a progressive flush interval (100 → 1000 → 5000); each chunk flushes and emits `progress.queryable`, so imported data is queryable during the import. - Sweep all docs, comments, and JSDoc for the removed/changed APIs. Integration suite: 49 files / 588 passed / 0 failed. Unit: 80 files / 1456 passed, no type errors.
2026-06-20 13:31:11 -07:00
writer = new Brainy({ requireSubtype: false, storage: { type: 'filesystem', path: dir }, silent: true })
fix: find()/stats() correctness + Cortex compat (BR-FIND-WHERE-ZERO, BR-DEFENSIVE-INTERFACE) Two production correctness defects fixed together so consumers can land one upgrade. BR-FIND-WHERE-ZERO — find() returned [] and stats() reported 0 entities for any workspace whose data was written after the 7.20.0 column-store refactor. Root cause: getStats() and the getIds() fallback still read from the deleted sparse-index path. Separately, BaseStorage.getNounType() was hardcoded to return 'thing', poisoning type-statistics.json with every noun attributed to that bucket. - MetadataIndex.getStats() reads from ColumnStore + idMapper. - MetadataIndex.getIdsFromChunks() throws BrainyError(FIELD_NOT_INDEXED) when neither store has the field. getIdsForFilter() catches per clause, logs once, returns []. - BaseStorage.nounTypeByIdCache populated in saveNounMetadata_internal and consumed in saveNoun_internal. flushCounts() now persists the Uint32Array counters too, so readers see fresh per-type counts. - Self-heal at init: loadTypeStatistics() auto-rebuilds when the poisoned signature is detected. rebuildTypeCounts() is now public for use from `brainy inspect repair`. - Dead state removed: dirtyChunks, dirtySparseIndices, flushDirtyMetadata(). BR-DEFENSIVE-INTERFACE — 7.21.0 called supportsMultiProcessLocking() unconditionally, crashing on older Cortex storage adapters that predate the method. New hasStorageMethod(name) helper gates every new-method call site. Older adapter triggers a one-line warning at init pointing at the recommended plugin version. Tests: - new tests/integration/find-where-zero.test.ts (7 cases) - new tests/integration/cortex-compat.test.ts (5 cases) - multi-process-safety.test.ts updated to enforce correct counts - 1329/1329 unit + 24/24 new integration tests passing
2026-05-15 12:31:28 -07:00
await writer.init()
for (let i = 0; i < 5; i++) {
await writer.add({ data: `entry ${i}`, type: NounType.Concept })
}
await writer.flush()
await writer.close()
writer = null
reader = await Brainy.openReadOnly({
feat(8.0): API simplification — remove neural()/Db.search, one storage `path` key, integration→0 8.0 RC cleanup toward "one place per thing, zero-config, no deprecation": - Remove the `brain.neural()` clustering namespace (ImprovedNeuralAPI + the dead legacy NeuralAPI + the neural CLI + neural-only types). Similarity is `find({vector})` / `similar({to})`; attribute grouping is the aggregation `GROUP BY` engine. The separate entity-extraction / smart-import feature (NeuralImport, NeuralEntityExtractor, SmartExtractor, NaturalLanguageProcessor, `brain.extract()`/`brain.nlp()`) is kept. - Remove `Db.search()`; `find()` is the one query verb (accepts a bare string or FindParams). Fix the bundled MCP client, which called a non-existent `brain.search(query, limit)` → now `find({ query, limit })`. - Storage config: collapse to one canonical top-level `path` key. The pre-8.0 aliases (`rootDirectory`, `options.*`, `fileSystemStorage.*`) are removed and now THROW with the exact rename instead of silently defaulting to `./brainy-data` on upgrade. A single resolver feeds createStorage, the 7.x→8.0 migration probe, and the plugin-factory handoff, so a native storage provider resolves the identical root (no split-brain). - Fix `similar({ threshold })`: the min-similarity filter was silently dropped; it is now applied as a post-filter on `result.score` (the documented way to bound semantic results). - Fix `vfs.rename()` on a directory: child path updates spread the entity vector into `update()` and failed dimension validation; they are metadata-only updates now. - Fix `vfs.move()`: copy+delete orphaned the content-addressed content blob (the destination shared the source hash, then unlink removed it). `move()` now delegates to `rename()` — an in-place path change that preserves the blob and the entity id, for files and directories. - Fix streaming import: the bulk fast path never flushed mid-import nor signalled queryability. Entity writes are now chunked by a progressive flush interval (100 → 1000 → 5000); each chunk flushes and emits `progress.queryable`, so imported data is queryable during the import. - Sweep all docs, comments, and JSDoc for the removed/changed APIs. Integration suite: 49 files / 588 passed / 0 failed. Unit: 80 files / 1456 passed, no type errors.
2026-06-20 13:31:11 -07:00
storage: { type: 'filesystem', path: dir }
fix: find()/stats() correctness + Cortex compat (BR-FIND-WHERE-ZERO, BR-DEFENSIVE-INTERFACE) Two production correctness defects fixed together so consumers can land one upgrade. BR-FIND-WHERE-ZERO — find() returned [] and stats() reported 0 entities for any workspace whose data was written after the 7.20.0 column-store refactor. Root cause: getStats() and the getIds() fallback still read from the deleted sparse-index path. Separately, BaseStorage.getNounType() was hardcoded to return 'thing', poisoning type-statistics.json with every noun attributed to that bucket. - MetadataIndex.getStats() reads from ColumnStore + idMapper. - MetadataIndex.getIdsFromChunks() throws BrainyError(FIELD_NOT_INDEXED) when neither store has the field. getIdsForFilter() catches per clause, logs once, returns []. - BaseStorage.nounTypeByIdCache populated in saveNounMetadata_internal and consumed in saveNoun_internal. flushCounts() now persists the Uint32Array counters too, so readers see fresh per-type counts. - Self-heal at init: loadTypeStatistics() auto-rebuilds when the poisoned signature is detected. rebuildTypeCounts() is now public for use from `brainy inspect repair`. - Dead state removed: dirtyChunks, dirtySparseIndices, flushDirtyMetadata(). BR-DEFENSIVE-INTERFACE — 7.21.0 called supportsMultiProcessLocking() unconditionally, crashing on older Cortex storage adapters that predate the method. New hasStorageMethod(name) helper gates every new-method call site. Older adapter triggers a one-line warning at init pointing at the recommended plugin version. Tests: - new tests/integration/find-where-zero.test.ts (7 cases) - new tests/integration/cortex-compat.test.ts (5 cases) - multi-process-safety.test.ts updated to enforce correct counts - 1329/1329 unit + 24/24 new integration tests passing
2026-05-15 12:31:28 -07:00
})
const report = await reader.health()
// index-parity must pass (HNSW count matches metadata count) and
// field-registry must pass (every persisted field discoverable).
// No more 'index-parity warn: differ by N' regressions.
const indexParity = report.checks.find(c => c.name === 'index-parity')
expect(indexParity?.status).toBe('pass')
})
})
})