# ruflo v3.38.1 — v3.38.1 — memory search truncation + persistence honesty fixes

- Product: ruflo (https://whatsnew.fyi/product/ruflo)
- Vendor: ruflo
- Date: 2026-08-12
- Version: v3.38.1
- Original notes: https://github.com/ruvnet/ruflo/releases/tag/v3.38.1
- Permalink: https://whatsnew.fyi/product/ruflo/releases/v3.38.1

What's New is an index, not a publisher: every entry below links to the vendor's own release notes, which are the authoritative source. Entries are labelled where they are hand-curated sample data, pre-releases, or drawn from a secondary source such as a developer blog.

Reuse: the summaries, labels and curation here are © What's New. Quote freely with attribution and a link back; wholesale republication of the corpus is not permitted — terms: https://whatsnew.fyi/terms. The vendors' own release notes remain their publishers'.

---

- **fixed** — Memory search silently dropped entries on large corpora due to unordered LIMIT being applied before BM25/embedding scoring; now orders by updated_at DESC before truncating in bridgeSearchEntries() and bridgeSearchHNSW()
- **fixed** — memory store command claimed success even when the write might not persist on sql.js fallback driver; now distinguishes wal_checkpoint(PASSIVE) failures and surfaces them as persistWarning instead of unconditional success message

##### Fixes

**#2982 / #2976 — memory search silently dropped entries on large corpora.** `bridgeSearchEntries()` and `bridgeSearchHNSW()` pre-ranked the memory corpus with an unordered `LIMIT 1000` / `LIMIT 10000` before BM25/embedding scoring ever ran. Without an `ORDER BY`, SQLite returns rows in arbitrary storage order (insertion order on a fresh table) — so on any corpus over the limit, the newest entries never reached scoring at all, regardless of how well they matched the query. Both paths now order by `updated_at DESC` before truncating, matching the pattern `bridgeListEntries()` already used.

Verified with a stash-based A/B on a 1005-row fixture: the exact same search returns zero results without the fix, recalls correctly with it.

**#2968 — `memory store` claimed success even when the write might not persist.** On the sql.js fallback driver (engaged when better-sqlite3's native binding never got built — e.g. a skipped `optionalDependency` postinstall), the post-write `wal_checkpoint(PASSIVE)` checkpoint throws `Invalid PRAGMA command` every time and was silently swallowed as "non-fatal." `bridgeStoreEntry()` now distinguishes that specific failure signature from an ordinary busy/non-WAL pragma failure and surfaces it as `persistWarning`, which `memory store` prints instead of an unconditional green "Data stored successfully."

Both fixes are scoped to ruflo's own CLI bridge layer — no changes to the external `agentdb`/`better-sqlite3` packages.

##### Also investigated, not changed

From the same triage pass: #2969 (`--version` hang), #2970 (witness verify soft-pass), and #2967 bug 1 (uptime unit mismatch) were all checked with a direct repro against current `main` and none reproduced — `--version` exits cleanly and fast, `verify.mjs` already exits 2 on a forced source-only checkout, and the uptime math is already correct post-#2235(B). No speculative fixes shipped for those.

##### Links

- PR: [#2983](https://github.com/ruvnet/ruflo/pull/2983)
- Issues closed: #2982, #2976; part of #2968