Repository navigation
v3.66.1 — federation trust thresholds enforced; locked memory stores say so
Patch release: @claude-flow/cli, claude-flow, ruflo 3.66.1, plus standalone @claude-flow/memory 3.2.0 and @claude-flow/plugin-agent-federation 1.0.4.
Security
- Federation trust thresholds are now enforced (#4618, #4619).
SecurityPolicy.minTrustLevelForWrite,minTrustLevelForMemoryandminTrustLevelForSpawnwere declared and accepted as overrides but never checked.- Before:
memory-queryandmemory-responsepassed atATTESTED, below the default policy's ownTRUSTEDminimum. - Now:
PolicyEngine.evaluateMessage()checks the configured minimum for write, memory and spawn messages. The check adds to the built-in capability gates; a looser policy cannot bypass them.
- Before:
Fixed
- A memory store locked by another process now says so (#4622). Separate stdio MCP servers opening one store contend for its native vector store.
- Before: AgentDB fell back to a backend that rejected the locked file as the wrong format, and only that error was reported. The registry was still treated as available, and memory operations then failed with an unrelated sql.js WAL refusal.
- Now:
ControllerRegistry.getAgentDBInitError()(@claude-flow/memory3.2.0) keeps the first backend's failure, such asDatabase already open. Cannot acquire lock. It names the fix: run one owner withruflo mcp start --transport httpand point every client at it. The CLI bridge records that reason and adds it to the fallback's refusal.isBridgeAvailable()returns false when AgentDB did not open. memory_listreports a failed query assuccess: falsewith its error, not as an empty inventory.