This is a comment left during a code review.
Path: src/plugins/loader.ts
Line: 1522-1546

Comment:
**`memorySlotMatched` not set when dreaming engine IS the configured slot**

When `memorySlot === dreamingEngineId` (e.g., user has explicitly set `plugins.slots.memory = "memory-core"` and also enabled dreaming), the `pluginId !== dreamingEngineId` guard skips the entire path-2 block. In the `!shouldLoadModules` code path (used by tooling that calls `loadOpenClawPlugins` with `loadModules: false`), execution then hits the `continue` at line 1563–1566 before the module-loading path (line 1668) can update `memorySlotMatched`. This leaves `memorySlotMatched = false`, triggering the false-positive diagnostic at line 1790: `"memory slot plugin not found or not marked as memory: memory-core"`.

The issue doesn't affect the primary fix target (`memorySlot = "memory-lancedb"`, dreaming enabled), but it is a regression for the edge case where `memory-core` is the explicit slot. A simple guard would resolve it:

```
if (!shouldLoadModules && registrationMode === "full") {
  if (pluginId === dreamingEngineId && hasKind(record.kind, "memory") && memorySlot === pluginId) {
    selectedMemoryPluginId = record.id;
    memorySlotMatched = true;
    record.memorySlotSelected = true;
  } else if (pluginId !== dreamingEngineId) {
    // ... existing logic unchanged
  }
}
```

The same pattern applies to path 3 (around line 1672) if both paths can be reached with `memorySlot === dreamingEngineId`.

How can I resolve this? If you propose a fix, please make it concise.

---

This is a comment left during a code review.
Path: src/plugins/loader.ts
Line: 1293-1299

Comment:
**No tests cover the new dreaming-engine exemption behavior**

The three-path exemption logic (plus the CLI-registry path) is non-trivial, yet no new test cases were added to `loader.test.ts`. The test plan verifies existing tests still pass but doesn't add coverage for the targeted scenario or for the regression guard. Consider adding tests for at least these two cases:

- `memory-lancedb` as slot + dreaming enabled at `memory-lancedb`'s config → both `memory-core` and `memory-lancedb` appear in the loaded registry, `memory-lancedb` has `memorySlotSelected: true`, `memory-core` does not.
- Same config with dreaming disabled → `memory-core` is absent (slot-policy exclusion still applies).

How can I resolve this? If you propose a fix, please make it concise.