Bug: 'memory store' reports success but does not create .swarm/memory.db file

### Description

The persistent memory feature appears to be broken in the latest alpha version (`2.0.0-alpha.90`).

The `npx claude-flow@alpha memory store` command incorrectly reports a successful write (`✅ Stored successfully`), but it does not actually create the `.swarm/` directory or the `memory.db` file on the filesystem. This results in total memory loss between commands and makes the persistent memory feature unusable.

### Steps to Reproduce

This bug can be reliably reproduced with the following steps in a clean directory:

1. **Create a clean test environment:**
```bash
mkdir claude-flow-bug-report
cd claude-flow-bug-report
```

2. **Run the `memory store` command.** According to the documentation, this should create the database if it doesn't exist.
```bash
npx claude-flow@alpha memory store "test_key" "This is a test."
```

3. **Observe the output.** The command reports a successful save:
```
✅ Stored successfully
📝 Key: test_key
📦 Namespace: default
💾 Size: 15 bytes
```

4. **Immediately check if the file was actually created.**
```bash
ls -l .swarm/memory.db
```

### Expected Behavior

After step 2, I expect the `.swarm/` directory and the `.swarm/memory.db` SQLite file to be created on the disk. The data "This is a test." should be written to a table inside the database.

### Actual Behavior

After step 2 reports success, the command in step 4 immediately fails with the following error, proving that the file was never created:

Start by running the documented `npx claude-flow@alpha memory store "test_key" "This is a test."` command in a clean directory, then inspect the `.swarm/memory.db` path and the memory-store entry point. Trace why the command reports success without creating the SQLite file; done means the directory and database are created and the stored value persists between commands.

Written by the indexing model from the issue text.