v3.38.21

DavidHDev/react-bitsv3.38.21Sep 2, 2026by ruvnet

AI Summary

Fixes a memory-persistence issue in the MCP HTTP bridge where entries became unreadable after a restart due to a database path mismatch in the initialization logic. Also relaxes a CI test assertion to handle coarse clock resolution.

Key Highlights

Fixed MCP bridge entries unreadable after restart (issue #3155)
Root cause identified in `initializeMemoryDatabase()` seeding logic
Relaxed CI test assertion for `result.duration` from `> 0` to `>= 0`

Full Release Notes

## Fixed

- **#3155** — `ruflo mcp start -t http`: entries stored via the bridge were unreadable after a bridge restart (`found:false`, `memory_list` empty), even though `.swarm/memory.db` held them and the CLI read them fine. Root cause: `initializeMemoryDatabase()` seeded the process-wide `ControllerRegistry` singleton with the sql.js-facing `memory.db` path instead of the dedicated `agentdb-memory.db` path. Fixed in #3156.
- **#3059** (CI) — `agentic-flow-agent.test.ts` asserted `result.duration` strictly `> 0`; under coarse CI clock resolution a ~1ms task's duration could legitimately read `0`, flaking the test-ratchet gate on `main`. Relaxed to `>= 0`.

## Known, separately-tracked gap (not in this release)

`@claude-flow/mcp` is pinned to `3.0.0-alpha.10` in root/CLI `package.json` (bumped in the 3.38.20 release commit) but that exact version was never published standalone to npm — only `alpha.9` exists on the registry. This breaks a fresh `npm ci` inside the `ruvnet/ruflo` monorepo itself (confirmed failing on CI). It does **not** affect end users installing `ruflo`/`@claude-flow/cli` from npm, since `@claude-flow/mcp` ships bundled inside those tarballs. Filed for follow-up.