ruflo v3.38.18

v3.38.18

v3.38.18 — Windows CI, dead agentdb exports, memory driver doctor check, MCP HTTP transport

Added 1
  • Added a read-only doctor check (checkMemoryPersistenceDriver) that reports whether the active SQLite driver is native better-sqlite3 or the silently-lossy sql.js fallback
Changed 1
  • @claude-flow/memory bumped to 3.0.0-alpha.23 and republished to resolve via the npm registry
Fixed 4
  • Windows CI Build V3 job was broken due to windows-latest moving to VS2026; pinned the matrix to windows-2022 to restore native builds for hnswlib-node and better-sqlite3
  • @claude-flow/memory's controller registry attempted to import 8 agentdb exports that no installable agentdb range provides; removed the dead import attempts and promoted existing fallback implementations to first-class for hierarchicalMemory/memoryConsolidation
  • MCP HTTP transport spec violations (non-string protocolVersion, HTTP tools/list only exposing 4 system tools, IPv6-only bind) that were fixed in source are now shipped in a release
  • Fixed a stale @claude-flow/mcp dependency pin (3.0.0-alpha.10, never published) that broke npm install of the monorepo

From ruflo

⚠️ BROKEN — superseded by v3.38.19
This version (and 3.38.17) shipped with a corrupted dependency graph due to a publish race — see v3.38.19 for the postmortem. @claude-flow/cli, claude-flow, and ruflo are all deprecated on npm at this version. Install 3.38.19 or later instead.
Fixes
  • #2992 — Windows CI (Build V3 job) was fully broken: windows-latest moved to VS2026, which node-gyp's VS detector can't identify, breaking native builds for hnswlib-node and better-sqlite3. Pinned the matrix to windows-2022.
  • #2977 — @claude-flow/memory's controller registry attempted to import 8 agentdb exports that no installable agentdb range actually provides, silently degrading every fresh install. Removed the dead import attempts and promoted the existing, verified-working fallback implementations (tieredMemoryFallback, the consolidation stub) to first-class for hierarchicalMemory/memoryConsolidation; the 6 controllers with no fallback now return null directly. agentdb_consolidate's stub response now says explicitly that it's a no-op rather than reading as "nothing to consolidate."
  • #2968 — Added a read-only doctor check (checkMemoryPersistenceDriver) that reports whether the active SQLite driver is native better-sqlite3 (durable, WAL-capable) or the silently-lossy sql.js fallback, using the table-count signal from the issue (~47 native vs ~10 fallback tables). Warns, never fails; does not change install behavior.
  • #2990 — MCP HTTP transport spec violations (non-string protocolVersion, HTTP tools/list only exposing 4 system tools, IPv6-only bind) were already fixed in source but had never shipped in a release; this release ships them.
  • Fixed a stale @claude-flow/mcp dependency pin (3.0.0-alpha.10, never published) that broke a plain npm install of the monorepo; repinned to the real published range.
  • @claude-flow/memory bumped to 3.0.0-alpha.23 (carries the #2977 fix) and republished, since it's resolved via the npm registry rather than bundled with @claude-flow/cli.

Verified: @claude-flow/memory full test suite (459/459), @claude-flow/cli doctor/commands/mcp-tools suites (541/541), clean tsc --noEmit on both packages, clean production builds. #3002 (ruvocal hidden-tab stream freeze) was checked and found already fixed on main — no change needed.

View original

Upgraded? How did it go?

Discussion