Bug: Smart Extraction path does not write to mdMirror (dual-write incomplete)

[arlen8411]

Bug Description

The Smart Extraction path (LLM-powered 6-category extraction) does not write to mdMirror, even though mdMirror is enabled. Only the Regex Fallback path writes to mdMirror.

Expected Behavior

According to the code comment "Markdown Mirror (dual-write)", all memory entries written to LanceDB should also be written to mdMirror as a backup. This includes memories created via Smart Extraction.

Evidence

From the logs, when Smart Extraction succeeds it directly returns without calling mdMirror:

```typescript
// index.ts around line 2248
const stats = await smartExtractor.extractAndPersist(...);
if (stats.created > 0 || stats.merged > 0) {
api.logger.info(`smart-extracted ${stats.created} created...`);
return; // ← exits here, no mdMirror call
}
```

The mdMirror write only exists in the Regex Fallback path (store.store() call followed by mdMirror() call).

Impact

• LanceDB: ✅ Memory entries created
• mdMirror: ❌ No .md file backup created
• This breaks the "dual-write" guarantee stated in the code comment

Question

Is this behavior intentional? If so, the documentation and code comment should be updated to clarify that Smart Extraction memories are NOT mirrored to .md files. If not, this is a bug that should be fixed.

Environment

• memory-lancedb-pro: 1.1.0-beta.9
• OpenClaw: 2026.4.2
• Configuration: smartExtraction: true, mdMirror: { enabled: true }