SQLite reader recovery runtime transcript. Linux; real development server.
Only reader-pool status messages are included.

[00:04:52.291] WARN (#2336) http.span=6434ms: SQLite reader worker unavailable; reads use the writer
  { reason: 'unable to open database file' }
[00:07:40.675] WARN (#2335): SQLite reader worker unavailable; reads use the writer
  { reason: 'unable to open database file' }
[00:07:47.741] INFO (#4282): SQLite reader worker available again; reads use the reader workers
[00:10:27.300] WARN (#2335) http.span=6534ms: SQLite reader worker unavailable; reads use the writer
  { reason: 'unable to open database file' }
[00:11:51.303] WARN (#2333): SQLite reader worker unavailable; reads use the writer
  { reason: 'unable to open database file' }
[00:11:58.353] INFO (#5702): SQLite reader worker available again; reads use the reader workers

Completed final scenario: base failed only the reader-operation assertion; head passed.
Base after restore: readers=0, reader operations=0, writer operations=614, same process=true.
Head after restore: readers=2, reader operations=172, writer operations=412, same process=true.