feat: startup-selected plugin memory orchestration #99
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/replaceable-memory-orchestration"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Startup-selected memory orchestration
Add trusted PluginAPI.registerMemoryOrchestrator recall/capture implementation separate from durable MemoryProvider. CLI selects default/none/custom after plugin activation before Harness start. Existing MemoryService remains default; disabled memory selects none. Explicit memory tools/storage unchanged. Persistent memory.orchestration overlay accepted; restart required, no runtime hot reload claim.
Validation
3 focused registry/actual Harness/plugin/settings-reopen tests and full557/557tests/typecheck/build/diffcheck PASS. Class receiver binding, unknown selection, malformed config, none, activation cleanup, custom recall/capture and persisted disabled/custom selection covered. Not a full real deployment restart/provider test. Original drafts untouched. Existing recall errors propagate, capture remains best effort; documented. Core default engine not yet extracted. Author checked, no extra independent round/reset. Standing operator delivery mandate; merge not deployment.