Commit graph

2 commits

Author SHA1 Message Date
364360d447 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.
2026-01-27 15:38:21 -08:00
00aae8023c chore(release): 4.0.0
Major release: Enterprise-scale cost optimization and performance features

Features:
- Cloud storage lifecycle management (GCS Autoclass, AWS Intelligent-Tiering, Azure)
- Batch operations (1000x faster deletions: 533 entities/sec vs 0.5/sec)
- FileSystem compression (60-80% space savings with gzip)
- OPFS quota monitoring for browser storage
- Enhanced CLI system (47 commands, 9 storage management commands)

Cost Impact:
- Up to 96% storage cost savings
- $138,000/year → $5,940/year @ 500TB scale

Breaking Changes: NONE
- 100% backward compatible
- All new features are opt-in
- No migration required
2025-10-17 14:48:34 -07:00