v3.32.34
ruvnet/ruflov3.32.34Jul 29, 2026by ruvnet
AI Summary
Repairs migration gap for existing installations to ensure reliable memory writes via the native AgentDB bridge.
Key Highlights
- Adds `provenance_type` column to existing `memory_entries` tables for pre-ADR-323 databases.
- Fails closed if the database is read-only, locked, or damaged.
- Recoverable bridge failure latch for diagnostics.
New Features
- Automatic migration of legacy databases.
- Preservation of actual native bridge errors for diagnostics.
- Idempotent migration logic.
Full Release Notes
# Ruflo v3.32.34: Reliable Memory Writes on Existing Installations v3.32.34 repairs a migration gap that could prevent `memory store` and MCP `memory_store` writes on databases created before ADR-323. The native AgentDB bridge now adds the required `provenance_type` column to existing `memory_entries` tables before writing. If that migration cannot run because the database is read-only, locked, or damaged, Ruflo fails closed and reports the native bridge error instead of presenting an unrelated WAL fallback message. The bridge failure latch is also recoverable: shutdown resets it, successful native writes clear stale diagnostics, and degradation notices remain visible. ## Install or upgrade ```bash npm install --global ruflo@3.32.34 ruflo doctor ``` Existing databases are migrated automatically on the first native bridge access. No manual SQL is required. ## Verify memory round-trip ```bash ruflo memory store \ --key release-3.32.34-check \ --value "memory bridge migration works" \ --namespace verification ruflo memory retrieve \ --key release-3.32.34-check \ --namespace verification ``` For MCP clients, the equivalent `memory_store` and `memory_retrieve` tools use the same repaired path. ## What changed - Migrates `provenance_type` on pre-ADR-323 AgentDB files. - Retries schema setup when the database was not writable. - Preserves the actual native bridge error for diagnostics. - Clears obsolete bridge errors after a successful native write. - Resets a failed initialization latch during bridge shutdown. - Keeps native-driver fallback notices visible. - Adds regression coverage for legacy databases, idempotent migration, fail-closed migration, and failure-latch recovery. ## Compatibility The migration is additive and idempotent. New databases already contain the column; existing databases receive it once; installations without the optional native bridge continue to use the existing sql.js path. This release resolves [#2843](https://github.com/ruvnet/ruflo/issues/2843) via [#2844](https://github.com/ruvnet/ruflo/pull/2844).