root/fusion
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat(FN-1772): add backend-aware memory instruction context API

Browse Source 
- Add MemoryBackendContext interface for backend-aware memory integration
- Implement getMemoryInstructions() method with backend-specific logic in project-memory.ts
- Add QMD memory backend type detection and instruction context for QMD-backed projects
- Update memory-plugin-contract.md with backend-variant instruction requirements (section 3.8.7)
- Update settings reference for memoryBackendType with custom backend support
- Add comprehensive regression tests for backend-variant memory instruction behavior
- Add changeset for @gsxdsm/fusion package
This commit is contained in:
gsxdsm
2026-04-13 22:03:42 -07:00
parent ce518f3b61
commit f6ae0e2e82
9 changed files with 502 additions and 18 deletions
Download Patch File Download Diff File Expand all files Collapse all files

27
docs/memory-plugin-contract.md
View File

@@ -810,13 +810,30 @@ The `.fusion/memory-insights.md` file has different semantics:
#### 3.8.7 Prompt Instruction Compatibility
Prompt instructions always reference `.fusion/memory.md` (project-root path). This is preserved regardless of backend:
Prompt instructions branch based on the configured memory backend type via `resolveMemoryInstructionContext()`:
- **Triage prompts**: `buildTriageMemoryInstructions()` still returns the same instruction text
- **Executor prompts**: `buildExecutionMemoryInstructions()` still returns the same instruction text
- **Path reference**: Instructions always show `.fusion/memory.md`, not backend-specific paths
**Backend-specific behavior:**
The backend abstraction does **not** change what instructions agents receive — it only changes where that content is stored.
| Backend Type | Path Hint | Behavior |
|-------------|-----------|-----------|
| `file` | `.fusion/memory.md` | Full read/write instructions with explicit file path |
| `readonly` | `null` | Read-only instructions, no write/update directives |
| `qmd` / non-file | `null` | Generic instructions without unconditional `.fusion/memory.md` reference |
**API functions:**
- `buildTriageMemoryInstructions(rootDir, settings?)` — Returns backend-appropriate instructions for the specification agent
- `buildExecutionMemoryInstructions(rootDir, settings?)` — Returns backend-appropriate instructions for the executor agent
- `resolveMemoryInstructionContext(settings?)` — Returns `MemoryInstructionContext` with backend metadata and capabilities
**Behavior details:**
- **File backend**: Instructions include `.fusion/memory.md` guidance and read/write directives
- **Readonly backend**: Instructions include read-only wording but no write/update directives
- **QMD/non-file backends**: Instructions are generic without assuming a file path; agents consult the project memory through backend-specific mechanisms
- **Backward compatibility**: When `memoryBackendType` is omitted or unknown, defaults to file behavior
**Invariant:** `memoryEnabled: false` always removes memory instructions regardless of backend type.
---