2025-09-26 14:27:46 -07:00
|
|
|
/**
|
|
|
|
|
* VFS Initialization Tests
|
|
|
|
|
*
|
2025-11-02 11:38:12 -08:00
|
|
|
* Tests v5.1.0+ auto-initialization behavior
|
2025-09-26 14:27:46 -07:00
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
import { describe, it, expect } from 'vitest'
|
refactor(8.0): remove dead, unreachable, and unwired modules
Pre-GA dead-code sweep. A deterministic import-reachability walk from the
package's real entry points (the exports map, the CLI bin, the conversation
surface) found 34 source modules that nothing reachable imports — they
compile and ship as dist output that no consumer or internal path can ever
reach. All were superseded duplicates, abandoned parallel implementations,
or built-but-never-wired features:
- superseded duplicates of live modules: an older "unified" entry, a
standalone neural-import variant, a static NLP processor + its matcher,
a parallel API-types module, a duplicate progress-types module
- an abandoned import path (orchestrator + entity deduplicator + barrels)
left behind when ingestion moved to the coordinator
- unwired feature modules (instance pool, import presets, cached
embeddings, relationship-confidence scorer) reachable only from tests
- dead leaf utilities (write buffer, deleted-items index, bounded
registry, two crypto shims, a cache manager, a structured logger, a
stale v5 type-migration helper, a browser-only FS type shim) and
several dead re-export barrels
- a CLI catalog command wired into no command
Also removed two tests that only exercised deleted modules, repointed two
VFS tests off a deleted barrel onto the implementation module, and deleted
one example that demoed removed features.
Verified: clean build (both tsc passes), unit 1505 + integration 607 green,
and a re-run of the reachability walk reports zero remaining orphans.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-24 15:18:40 -07:00
|
|
|
import { VirtualFileSystem } from '../../src/vfs/VirtualFileSystem.js'
|
2025-09-26 14:27:46 -07:00
|
|
|
import { Brainy } from '../../src/brainy.js'
|
|
|
|
|
|
|
|
|
|
describe('VFS Initialization', () => {
|
|
|
|
|
|
2025-11-02 11:38:12 -08:00
|
|
|
describe('Auto-Initialization (v5.1.0+)', () => {
|
|
|
|
|
it('should auto-initialize VFS during brain.init()', async () => {
|
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
|
|
|
const brain = new Brainy({ requireSubtype: false,
|
2025-09-26 14:27:46 -07:00
|
|
|
storage: { type: 'memory' },
|
|
|
|
|
silent: true
|
|
|
|
|
})
|
|
|
|
|
await brain.init()
|
|
|
|
|
|
2025-11-02 11:38:12 -08:00
|
|
|
const vfs = brain.vfs
|
2025-09-26 14:27:46 -07:00
|
|
|
|
2025-11-02 11:38:12 -08:00
|
|
|
// VFS is ready to use immediately after brain.init()
|
2025-09-26 14:27:46 -07:00
|
|
|
await vfs.writeFile('/test.txt', 'Hello World')
|
2025-11-02 11:38:12 -08:00
|
|
|
const content = await vfs.readFile('/test.txt')
|
|
|
|
|
expect(content.toString()).toBe('Hello World')
|
2025-09-26 14:27:46 -07:00
|
|
|
|
|
|
|
|
await brain.close()
|
|
|
|
|
})
|
|
|
|
|
|
2025-11-02 11:38:12 -08:00
|
|
|
it('should automatically create root directory on brain.init()', async () => {
|
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
|
|
|
const brain = new Brainy({ requireSubtype: false,
|
2025-09-26 14:27:46 -07:00
|
|
|
storage: { type: 'memory' },
|
|
|
|
|
silent: true
|
|
|
|
|
})
|
|
|
|
|
await brain.init()
|
|
|
|
|
|
2025-11-02 11:38:12 -08:00
|
|
|
const vfs = brain.vfs
|
2025-09-26 14:27:46 -07:00
|
|
|
|
2025-11-02 11:38:12 -08:00
|
|
|
// Root directory exists after brain.init()
|
2025-09-26 14:27:46 -07:00
|
|
|
expect(await vfs.exists('/')).toBe(true)
|
|
|
|
|
|
|
|
|
|
// Root is a directory
|
|
|
|
|
const stats = await vfs.stat('/')
|
|
|
|
|
expect(stats.isDirectory()).toBe(true)
|
|
|
|
|
|
2025-11-02 11:38:12 -08:00
|
|
|
// Can list root directory
|
2025-09-26 14:27:46 -07:00
|
|
|
const entries = await vfs.readdir('/')
|
|
|
|
|
expect(Array.isArray(entries)).toBe(true)
|
|
|
|
|
|
|
|
|
|
await brain.close()
|
|
|
|
|
})
|
|
|
|
|
|
2025-11-02 11:38:12 -08:00
|
|
|
it('should handle nested directories after brain.init()', async () => {
|
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
|
|
|
const brain = new Brainy({ requireSubtype: false,
|
2025-09-26 14:27:46 -07:00
|
|
|
storage: { type: 'memory' },
|
|
|
|
|
silent: true
|
|
|
|
|
})
|
|
|
|
|
await brain.init()
|
|
|
|
|
|
2025-11-02 11:38:12 -08:00
|
|
|
const vfs = brain.vfs
|
2025-09-26 14:27:46 -07:00
|
|
|
|
|
|
|
|
// Create nested structure
|
|
|
|
|
await vfs.mkdir('/documents')
|
|
|
|
|
await vfs.writeFile('/documents/readme.txt', 'Important info')
|
|
|
|
|
await vfs.mkdir('/documents/reports')
|
|
|
|
|
await vfs.writeFile('/documents/reports/q1.txt', 'Q1 Report')
|
|
|
|
|
|
|
|
|
|
// Verify structure
|
|
|
|
|
const rootEntries = await vfs.readdir('/')
|
|
|
|
|
expect(rootEntries).toContain('documents')
|
|
|
|
|
|
|
|
|
|
const docEntries = await vfs.readdir('/documents')
|
|
|
|
|
expect(docEntries).toContain('readme.txt')
|
|
|
|
|
expect(docEntries).toContain('reports')
|
|
|
|
|
|
|
|
|
|
const reportEntries = await vfs.readdir('/documents/reports')
|
|
|
|
|
expect(reportEntries).toContain('q1.txt')
|
|
|
|
|
|
2025-11-02 11:38:12 -08:00
|
|
|
await brain.close()
|
|
|
|
|
})
|
|
|
|
|
|
2025-09-26 14:27:46 -07:00
|
|
|
})
|
2025-11-02 11:38:12 -08:00
|
|
|
})
|