sqlite reader pool real dev verification, 2026-11-04 UTC
main: 9e85538535, separate /home/user/main worktree
pr: e667d990c0bf4177ea30ed18fc6bf8196fe01f09
linux; node v24.22.1; chrome via repository playwright
data created through web UI: real /home/user/t3code git project, threads, Codex gpt-6.1-sol turns via local proxy. no mocks or demo data.
fault: debugger retires a real reader; task userdata directory permissions temporarily 000, making replacement SQLite read-only open fail; permissions restored to 700. no source edits. Directory denial also temporarily blocked trace/provider-log writes; metrics were collected outside that directory.

$ rg -A1 "SQLite reader" /tmp/main-dev.log
[14:20:26.336] WARN (#6047) http.span=66664ms: SQLite reader worker unavailable; reads use the main connection
  { reason: 'unable to open database file' }
main directory access restored about 14:20:28; database file mode restored to 600 before final client turn.
$ node /tmp/trace-summary.mjs main-server.trace.ndjson 2026-11-04T14:20:29Z
{
  "from": "2026-11-04T14:20:29.000Z",
  "through": "2026-11-04T14:21:55.127Z",
  "counts": {
    "writer": 165,
    "undefined": 204
  }
}

undefined denotes nested spans without a connection annotation; excluded from routing comparison.
main client response: main fallback still works. Reload retained history. No reader recovery before shutdown.

PR fault applied 14:31:26.943; directory restored 14:31:31.038
$ rg -A1 "SQLite reader" /tmp/dev.log
[14:31:27.068] WARN (#5708): SQLite reader worker unavailable; reads use the main connection
  { reason: 'unable to open database file' }
[14:31:34.161] INFO (#5759): SQLite reader worker available again; reads use the reader workers
actual OTLP gauge transitions:
2026-11-04T14:31:26.821Z t3_sqlite_reader_pool_available=1
2026-11-04T14:31:27.837Z t3_sqlite_reader_pool_available=0
2026-11-04T14:31:34.874Z t3_sqlite_reader_pool_available=1

$ node /tmp/trace-summary.mjs PR-server.trace.ndjson 2026-11-04T14:31:35Z
{
  "from": "2026-11-04T14:31:35.000Z",
  "through": "2026-11-04T14:32:53.792Z",
  "counts": {
    "writer": 14,
    "reader": 155,
    "undefined": 310
  }
}

During fallback after permissions restored, successful SELECTs used writer at 14:31:33.393 and 14:31:33.394. Recovery logged at 14:31:34.161.
Client responses: sqlite baseline ok.; recovered writes ok.; new thread after recovery ok. Follow-up send, new thread, and history reload passed.

Remote Blacksmith checks: vp test run packages/shared/src/nodeSqliteClient.test.ts: 24/24 passed.
vp run check:changed 8b44f42b14c8e273156474a924ccf29680dd7857: format/lint/knip passed, 34 packages typechecked, 25/25 tests passed. Explicit base needed because remote snapshot initially lacked main history; fetched actual PR ancestry.

Not exercised in running app: 10s startup timeout, 60s retry cap, permanent non-WAL path, close during retry. Existing focused tests passed. Native mobile, Electron shell, Windows/macOS and relay/tunnel not exercised on this Linux VM.