brainy/tests/unit/utils/entity-id-mapper-stability.test.ts
David Snelling 780fb6444b feat(8.0)!: flip requireSubtype default to true (BRAINY-8.0-SUBTYPE-CONTRACT § C-1)
Brainy 8.0 makes subtype required by default on every public write path
(`add`, `addMany`, `update`, `relate`, `relateMany`, `updateRelation`,
import). Per the locked C-1 contract, every entity and relation gets a
non-empty subtype string by the time the storage layer sees it.

OPT-OUT REMAINS FULLY SUPPORTED

The runtime flag is still consumer-controlled. Three opt-out paths
cover migration / legacy fixtures / typed escape:

- `new Brainy({ requireSubtype: false })` — last-resort: turn off the
  contract entirely. Recommended only for migration windows or test
  fixtures that legitimately can't supply a subtype.
- `new Brainy({ requireSubtype: { except: [NounType.Thing, ...] } })` —
  per-type allowlist: strict everywhere except the listed types.
- `brain.requireSubtype(type, options)` — per-type registration with
  optional vocabulary. Composes with the brain-wide flag.

Default is now `true`. Opt-out is explicit and documented; nothing
silently degrades.

TEST SWEEP

Bulk-applied `requireSubtype: false` to every `new Brainy({...})` call
site across 120 test files. Three sed patterns covered the shapes:
  - `new Brainy({` → `new Brainy({ requireSubtype: false,`
  - `new Brainy<T>({` → `new Brainy<T>({ requireSubtype: false,`
  - `new Brainy()` → `new Brainy({ requireSubtype: false })`

tests/helpers/test-factory.ts → createTestConfig() defaults
`requireSubtype: false` so test files using the helper inherit the
opt-out without per-site edits.

The test sites that DO exercise subtype semantics (the
subtype-and-facets suite, the strict-mode-self-test suite, the verb-
subtype-and-enforcement suite, etc.) already pass real subtypes — they
were the 7.30.x acceptance tests for this contract. Those tests
continue to pass unchanged.

CHANGES

src/brainy.ts
- normalizeConfig() — `requireSubtype` default `false` → `true`.
  Comment refreshed to document the three opt-out paths.

tests/* (120 files)
- Bulk-edited brain construction sites. No functional test changes; the
  opt-out preserves the test author's original intent.

tests/helpers/test-factory.ts
- createTestConfig() base config gains `requireSubtype: false`.

NO-OP for consumers who were already passing subtype on every write.

For consumers who weren't, the upgrade path is one of the three opt-out
forms above. Migration recipe documented in 8.0 release notes (next
commit).

VERIFICATION

- npx tsc --noEmit: clean
- npm test: 1408 / 1409 (same pre-existing race-condition outstanding;
  no other regressions from the flip)
2026-06-09 14:58:25 -07:00

161 lines
5.5 KiB
TypeScript

/**
* Regression test: EntityIdMapper stability across rebuild.
*
* The foundation 2.4.0 (vector mmap store, graph link compression, column-store
* JS↔native interchange) all key off UUID→int mappings that **must not change**
* across a metadata-index rebuild. Previously `metadataIndex.rebuild()` called
* `idMapper.clear()` which reset `nextId` to 1 and renumbered every UUID by
* re-insertion order, silently invalidating any consumer that had persisted
* int-keyed data against the old map.
*
* This test pins down the stability contract:
*
* 1. UUID→int mappings persist across a single rebuild.
* 2. Mappings persist across many consecutive rebuilds.
* 3. New entities added after rebuild get fresh ints greater than any prior
* assignment — no collisions with existing UUIDs' ints.
* 4. Removed entities leave a permanent hole — new entities don't recycle the
* gap, even across a rebuild.
* 5. `clearAllIndexData()` is the explicit, intentional nuclear path — it DOES
* renumber. This is the only documented way to invalidate the int space, and
* a warning is logged so consumers know persisted int-keyed data is now stale.
*/
import { describe, it, expect, beforeEach, afterEach } from 'vitest'
import { Brainy } from '../../../src/brainy.js'
const DIM = 384
const makeVec = (seed = 1) =>
new Float32Array(DIM).map((_, i) => ((i + seed) % DIM) / DIM)
describe('EntityIdMapper stability (foundation for 2.4.0)', () => {
let brain: Brainy
beforeEach(async () => {
brain = new Brainy({ requireSubtype: false, storage: { type: 'memory' }, silent: true })
await brain.init()
})
afterEach(async () => {
await brain.close()
})
async function addEntity(name: string, seed: number): Promise<string> {
return brain.add({
data: name,
vector: makeVec(seed),
type: 'thing' as any,
metadata: { name }
})
}
function getInt(uuid: string): number | undefined {
return (brain as any).metadataIndex.idMapper.getInt(uuid)
}
async function rebuild(): Promise<void> {
await (brain as any).metadataIndex.rebuild()
}
it('UUID→int mappings persist across a single metadata-index rebuild', async () => {
const ids = [
await addEntity('a', 1),
await addEntity('b', 2),
await addEntity('c', 3),
await addEntity('d', 4),
await addEntity('e', 5)
]
const before = ids.map(id => getInt(id))
expect(before.every(i => typeof i === 'number' && (i as number) > 0)).toBe(true)
await rebuild()
const after = ids.map(id => getInt(id))
expect(after).toEqual(before)
})
it('mappings stay byte-for-byte stable across many consecutive rebuilds', async () => {
const ids = [
await addEntity('a', 1),
await addEntity('b', 2),
await addEntity('c', 3)
]
const before = ids.map(id => getInt(id))
for (let i = 0; i < 5; i++) {
await rebuild()
const after = ids.map(id => getInt(id))
expect(after).toEqual(before)
}
})
it('entities added after rebuild get fresh monotonic ints (no collision with existing)', async () => {
const priorIds = [
await addEntity('a', 1),
await addEntity('b', 2),
await addEntity('c', 3)
]
const priorInts = priorIds.map(id => getInt(id) as number)
const maxPrior = Math.max(...priorInts)
await rebuild()
const newId = await addEntity('d', 4)
const newInt = getInt(newId) as number
expect(newInt).toBeGreaterThan(maxPrior)
// Prior entities' ints didn't drift.
expect(priorIds.map(id => getInt(id))).toEqual(priorInts)
})
it('removed entities leave a permanent hole — new entities never recycle the gap', async () => {
const ids = [
await addEntity('a', 1),
await addEntity('b', 2),
await addEntity('c', 3),
await addEntity('d', 4),
await addEntity('e', 5)
]
const beforeInts = ids.map(id => getInt(id) as number)
const deletedId = ids[2]
const deletedInt = beforeInts[2]
const maxBefore = Math.max(...beforeInts)
await brain.delete(deletedId)
expect(getInt(deletedId)).toBeUndefined()
const newId = await addEntity('f', 6)
const newInt = getInt(newId) as number
expect(newInt).not.toBe(deletedInt)
expect(newInt).toBeGreaterThan(maxBefore)
// Surviving ids keep their ints across the deletion + the add.
const survivors = ids.filter((_, i) => i !== 2)
const survivorIntsBefore = beforeInts.filter((_, i) => i !== 2)
expect(survivors.map(id => getInt(id))).toEqual(survivorIntsBefore)
// Survivors' ints also survive a rebuild after the delete.
await rebuild()
expect(survivors.map(id => getInt(id))).toEqual(survivorIntsBefore)
// The deleted id is still gone after rebuild (no resurrection).
expect(getInt(deletedId)).toBeUndefined()
})
it('clearAllIndexData() is the explicit nuclear path that DOES renumber', async () => {
const id1 = await addEntity('a', 1)
const id2 = await addEntity('b', 2)
const priorInts = [getInt(id1) as number, getInt(id2) as number]
expect(priorInts.every(i => i >= 1)).toBe(true)
// Nuclear recovery: explicit destructive op. The warning logged here is
// the only documented way to invalidate the canonical int space.
await (brain as any).metadataIndex.clearAllIndexData()
// Both UUIDs are gone from the mapper.
expect(getInt(id1)).toBeUndefined()
expect(getInt(id2)).toBeUndefined()
// The int counter restarted from 1: the next add() gets int 1.
const idAfter = await addEntity('c', 3)
expect(getInt(idAfter)).toBe(1)
})
})