Dmitriy Kovalenko 1ef30bcbe7 Preserve existing SQLite journal modes on startup (#54389) ...

## Why

Opening an initialized database in `DELETE` journal mode previously attempted to convert it to `WAL`, which could fail while another connection held a write lock.

## What changed

- Initialize `WAL` and incremental auto-vacuum only for databases without a schema, including files left by interrupted initialization.
- Preserve journal and vacuum modes for initialized databases, use `synchronous = EXTRA` for `DELETE` connections, and retain `NORMAL` for `WAL`.
- Close failed initialization pools before retrying and restrict background page reclamation to `WAL` databases.

## Testing

Extend SQLite tests to cover interrupted initialization, opening `DELETE` databases under a write lock across all pool connections, persistence after reopening, and lock release after failed initialization.

GitOrigin-RevId: 23acecfe472618dde8545815e9a1058a51591235

2026-10-15 19:15:04 +00:00

..

goals_migrations

Preserve thread context when retrying or editing turns (#33211)

2026-07-15 02:35:49 +00:00

logs_migrations

Align SQLite feedback logs with feedback formatter (#13494)

2026-03-18 22:44:31 +00:00

memory_migrations

Add memory dual writing and v2 readiness reporting (#43827)

2026-09-08 14:23:23 +00:00

migrations

Expose experimental durable thread read state in the app server (#52350)

2026-10-09 01:22:30 +00:00

queue_migrations

Dispatch queued messages written by other processes (#39034)

2026-08-17 17:19:46 +00:00

src

Preserve existing SQLite journal modes on startup (#54389)

2026-10-15 19:15:04 +00:00

thread_history_migrations

Expose and persist turn lineage across the app server (#51415)

2026-10-06 16:56:39 +00:00

BUILD.bazel

Shard state unit tests under Bazel (#37478)

2026-08-07 17:49:48 +00:00

Cargo.toml

Detect SQLite corruption during startup and preserve recovery backups (#49701)

2026-09-30 18:29:46 +00:00