feat(FN-2133): standardize project memory path guidance to .fusion/memory/

- Update executor, reviewer, core prompt templates, and path-boundary messaging to reference the .fusion/memory/ directory instead of a single MEMORY.md file
- Broaden worktree boundary checks in pi path validation to allow .fusion/memory/ directory access from task worktrees
- Align memory backend metadata and dashboard backend labels to display file backend storage as .fusion/memory/
- Refresh core/engine tests to assert the new directory-based memory wording and boundary behavior
This commit is contained in:
Fusion
2026-04-19 08:09:15 -07:00
committed by gsxdsm
parent d47694036f
commit 5e31c409bd
14 changed files with 52 additions and 48 deletions

View File

@@ -215,7 +215,7 @@ const backendRegistry = new Map<string, MemoryBackend>();
*/
export class FileMemoryBackend implements MemoryBackend {
readonly type = "file";
readonly name = "File (.fusion/memory/MEMORY.md)";
readonly name = "File (.fusion/memory/)";
readonly capabilities: MemoryBackendCapabilities = {
readable: true,
writable: true,