export_web: SurrealDB served ran at a sync per commit in both durability classes; withhold its October write cells (BUGS F165) #80

SurrealDB 3.2.4 served takes its sync mode as a parameter on the storage path (rocksdb:/path?sync=never|every|<interval>) and logs it at INFO when it starts. Its default is Sync mode: every transaction commit. Every SurrealDB served serverlog of the October campaign on mini (107 of 107) carries that line, in both durability classes, while the rows said the behaviour at commit was "not verified" (the September search covered only its SURREAL_* variable names).

Laptop strace on the pinned image (surrealdb/surrealdb@sha256:6a500236…, v3.2.4): one fdatasync per commit at the default, 5.3 ms each wall clock; none at sync=never, where single-record writes fall from about 7.5 ms to under 1.2 ms. A read-only BEGIN/COMMIT also syncs. Reported by a co-author reading the page: SurrealDB served new-order p50 9.87 ms against 0.16 ms embedded.

October page: withhold SurrealDB served write cells on Document OLTP, Graph OLTP, and the cross-model transaction (marked re-run, keyed on rows without surreal_sync_mode), and replace the "could not be established" durability sentences with what it ran. Reads, analytics, and ingest stay. The re-pin (local repin-prep) runs it at sync=never and sync=every with the mode read back from the startup log.