“Every one of the 50 writes returned success: true, and the DB stays integrity_check: ok. One process's entire batch was obliterated.”

— sparkling, on GitHub · Comment on issue #2621, The write drop is reproducible in ~30 lines

Quote · github.com

From “3.25.6 field report: daemon ↔ MCP last-writer-wins still drops MCP-session writes”, found 2026-10-14.

Take

Two processes wrote 25 rows each; all 50 writes were acknowledged and 25 rows remained. The test forced the sql.js fallback path, so it doesn't apply to every backend. The remaining race moved to #2878, closed in August 2026.

Tools it’s about