fix: exclude __words__ keyword index from corruption detection and getStats()

The __words__ keyword index stores 50-5000 entries per entity (one per
word), which inflated avg entries/entity well above the corruption
threshold of 100. This caused:

1. validateConsistency() to falsely detect corruption on every startup,
   triggering unnecessary clearAllIndexData() + rebuild() cycles
2. getStats() to log false "Metadata index may be corrupted" warnings
   and report inflated totalEntries/totalIds stats

Both methods now skip __words__ when counting, so stats and health
checks reflect metadata fields only (noun, type, createdAt, etc.).
Keyword search is unaffected since the __words__ field index itself
is not modified.
This commit is contained in:
David Snelling 2026-01-27 15:38:21 -08:00
parent 32dbdcec61
commit 364360d447
128 changed files with 5637 additions and 5682 deletions

View file

@ -33,8 +33,8 @@ export interface VFSMetadata {
name: string // Filename or directory name
parent?: string // Parent directory entity ID
vfsType: 'file' | 'directory' | 'symlink'
isVFS?: boolean // v4.3.3: Mark as VFS entity (internal, separates from knowledge graph)
isVFSEntity?: boolean // v5.3.0: Explicit developer-facing flag for filtering VFS entities
isVFS?: boolean // Mark as VFS entity (internal, separates from knowledge graph)
isVFSEntity?: boolean // Explicit developer-facing flag for filtering VFS entities
// File attributes
size: number // Size in bytes (0 for directories)
@ -50,7 +50,7 @@ export interface VFSMetadata {
accessed: number // Last access timestamp (ms)
modified: number // Last modification timestamp (ms)
// Content storage strategy (v5.2.0: unified blob storage)
// Content storage strategy (unified blob storage)
storage?: {
type: 'blob' // All files now use BlobStorage (was 'inline'|'reference'|'chunked')
hash: string // SHA-256 content hash from BlobStorage