Critical architectural fix for VFS tree corruption bug:
- GraphAdjacencyIndex singleton via storage.getGraphIndex()
- Auto-rebuild verbIdSet when LSM-trees have existing data
- Removed dual-ownership causing verbIdSet out of sync
- PathResolver cache invalidation on checkout/fork
🤖 Generated with Claude Code
Co-Authored-By: Claude <noreply@anthropic.com>
Bug fixes:
- Fix verbCountsByType optimization skipping Contains relationships
- Fix UnifiedCache not invalidated on path deletion
- Add fast path for sourceId + verbType queries (common VFS pattern)
- Save statistics on first entity of each type
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
Performance fix for GCS/S3/R2/Azure:
- Single add(): 7-11 seconds → 200-400ms
- Zero configuration - automatic for cloud storage
- flush() on close() ensures data durability
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
Fix add() → relate() race condition in cloud storage (GCS, S3, R2, Azure)
Problem:
- In high-volume mode, writes go to buffer instead of direct storage
- Cache was NOT populated when buffering
- add() returns but relate() fails with "Source entity not found"
Solution:
- Populate cache BEFORE adding to write buffer
- Ensures immediate read-after-write consistency
- Buffer still flushes asynchronously for performance
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
CRITICAL BUG FIX: v5.10.0 regressed the v5.7.2 blob integrity bug, causing
100% VFS file read failure. This fix restores functionality with production-grade
defense-in-depth architecture and comprehensive testing.
Problem:
- v5.10.0 reintroduced bug where BlobStorage.read() hashed wrapped data
- Symptom: "Blob integrity check failed" on every VFS file read
- Impact: 100% failure rate in Workshop application
- Root Cause: Missing defense-in-depth unwrap verification
The Fix:
1. Defense-in-Depth Unwrapping
- Added unwrap verification in BlobStorage.read() before hash check (line 342)
- Added unwrap for metadata parsing (line 314)
- Ensures data is always unwrapped regardless of adapter behavior
2. DRY Architecture
- Created binaryDataCodec.ts as single source of truth
- Refactored baseStorage to use shared utilities
- All 8 storage adapters now use same implementation
3. Comprehensive Testing
- Added TestWrappingAdapter that actually wraps like production
- 3 new regression tests validate the fix
- Tests exercise real wrapping scenario that caused the bug
Architecture Improvements:
- ✅ Defense-in-Depth: Unwrap at BOTH adapter and blob layers
- ✅ DRY Principle: Single source of truth in binaryDataCodec.ts
- ✅ Works Across ALL Storage Adapters (8 total)
- ✅ Prevents Future Regressions: Real wrapping tests
Files Changed:
- NEW: src/storage/cow/binaryDataCodec.ts (single source of truth)
- FIXED: src/storage/cow/BlobStorage.ts (defense-in-depth unwrap)
- REFACTORED: src/storage/baseStorage.ts (uses shared codec)
- NEW: tests/helpers/TestWrappingAdapter.ts (real wrapping adapter)
- ADDED: 3 regression tests in tests/unit/storage/cow/BlobStorage.test.ts
- UPDATED: CHANGELOG.md, package.json (v5.10.1)
Related Issues:
- v5.7.2: Original bug - hashed wrapper instead of content
- v5.7.5: First fix - added unwrap to adapter (necessary but insufficient)
- v5.10.0: Regression - missing defense-in-depth in BlobStorage
- v5.10.1: Complete fix - defense-in-depth + DRY + tests
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
