It only catches it if you re-load the DB into sqlite after every write by turso. At which point you'd flag pretty quickly that it was the next write after 1 GB that messed things up

Yeah. Is their developer super human because he...reads the source code?? This should be obvious.

Now I would be genuinely worried about what other issues are lurking in their rewrite.

The worst thing is, it's also documented in the SQLite's documentation. The file format is documented, and it describes the existence of this lock-page located at 1 GiB mark. How they've managed to implement support for SQLite DB file format without reading the file format description is, frankly, beyond me.

I think it's a valid question, but it's better to assume they had their reasons and try to understand why before drawing conclusions.

We live in a SOCIETY!!!