refactor(FN-2126): align memory handling with canonical .fusion/memory paths
- Update memory docs and contracts to reference canonical .fusion/memory files while treating the legacy top-level memory file as compatibility-only - Tighten memory backend path normalization messaging and map stale qmd legacy top-level memory results back to .fusion/memory/MEMORY.md - Remove legacy memory read/write fallback branches from backend initialization paths and rely on ensureOpenClawMemoryFiles() migration behavior - Preserve migration-seeded legacy content during ensureMemoryFile() bootstrap and add regression coverage for seeded long-term memory creation
This commit is contained in:
@@ -412,7 +412,7 @@ Fusion can automatically extract insights from project memory and prune transien
|
||||
| File | Description |
|
||||
|------|-------------|
|
||||
| `.fusion/memory/MEMORY.md` | Long-term memory (updated when pruning is applied and validated) |
|
||||
| `.fusion/memory.md` | Deprecated legacy fallback (migration compatibility only; not canonical storage) |
|
||||
| Legacy top-level memory file | Deprecated migration fallback (compatibility only; not canonical storage) |
|
||||
| `.fusion/memory-insights.md` | Long-term insights distilled from working memory |
|
||||
| `.fusion/memory-audit.md` | Human-readable audit report after each extraction |
|
||||
|
||||
|
||||
Reference in New Issue
Block a user