Why

SQLite state was still being opened from consumer paths, including lazy OnceCell-backed thread-store call sites. That let one process construct multiple state DB connections for the same Codex home, which makes SQLite lock contention and database is locked failures much easier to hit.

State DB lifetime should be chosen by main-like entrypoints and tests, then passed through explicitly. Consumers should use the supplied Option<StateDbHandle> or StateDbHandle and keep their existing filesystem fallback or error behavior when no handle is available.

The startup path also needs to keep the rollout crate in charge of SQLite state initialization. Opening codex_state::StateRuntime directly bypasses rollout metadata backfill, so entrypoints should initialize through codex_rollout::state_db and receive a handle only after required rollout backfills have completed.

What Changed

• Initialize the state DB in main-like entrypoints for CLI, TUI, app-server, exec, MCP server, and the thread-manager sample.
• Pass Option<StateDbHandle> through ThreadManager, LocalThreadStore, app-server processors, TUI app wiring, rollout listing/recording, personality migration, shell snapshot cleanup, session-name lookup, and memory/device-key consumers.
• Remove the lazy local state DB wrapper from the thread store so non-test consumers use only the supplied handle or their existing fallback path.
• Make codex_rollout::state_db::init the local state startup path: it opens/migrates SQLite, runs rollout metadata backfill when needed, waits for concurrent backfill workers up to a bounded timeout, verifies completion, and then returns the initialized handle.
• Keep optional/non-owning SQLite helpers, such as remote TUI local reads, as open-only paths that do not run startup backfill.
• Switch app-server startup from direct codex_state::StateRuntime::init to the rollout state initializer so app-server cannot skip rollout backfill.
• Collapse split rollout lookup/list APIs so callers use the normal methods with an optional state handle instead of _with_state_db variants.
• Restore getConversationSummary(ThreadId) to delegate through ThreadStore::read_thread instead of a LocalThreadStore-specific rollout path special case.
• Keep DB-backed rollout path lookup keyed on the DB row and file existence, without imposing the filesystem filename convention on existing DB rows.
• Verify readable DB-backed rollout paths against session_meta.id before returning them, so a stale SQLite row that points at another thread's JSONL falls back to filesystem search and read-repairs the DB row.
• Keep debug prompt-input filesystem-only so a one-off debug command does not initialize or backfill SQLite state just to print prompt input.
• Keep goal-session test Codex homes alive only in the goal-specific helper, rather than leaking tempdirs from the shared session test helper.
• Update tests and call sites to pass explicit state handles where DB behavior is expected and explicit None where filesystem-only behavior is intended.

Validation

• CARGO_TARGET_DIR=/tmp/codex-target-state-db cargo check -p codex-rollout -p codex-thread-store -p codex-app-server -p codex-core -p codex-tui -p codex-exec -p codex-cli --tests
• CARGO_TARGET_DIR=/tmp/codex-target-state-db cargo test -p codex-rollout state_db_
• CARGO_TARGET_DIR=/tmp/codex-target-state-db cargo test -p codex-rollout find_thread_path
• CARGO_TARGET_DIR=/tmp/codex-target-state-db cargo test -p codex-rollout find_thread_path -- --nocapture
• CARGO_TARGET_DIR=/tmp/codex-target-state-db cargo test -p codex-rollout try_init_ -- --nocapture
• CARGO_TARGET_DIR=/tmp/codex-target-state-db cargo test -p codex-rollout
• CARGO_TARGET_DIR=/tmp/codex-target-state-db cargo clippy -p codex-rollout --lib -- -D warnings
• CARGO_TARGET_DIR=/tmp/codex-target-state-db cargo test -p codex-thread-store read_thread_falls_back_when_sqlite_path_points_to_another_thread -- --nocapture
• CARGO_TARGET_DIR=/tmp/codex-target-state-db cargo test -p codex-thread-store
• CARGO_TARGET_DIR=/tmp/codex-target-state-db cargo test -p codex-core shell_snapshot
• CARGO_TARGET_DIR=/tmp/codex-target-state-db cargo test -p codex-core --test all personality_migration
• CARGO_TARGET_DIR=/tmp/codex-target-state-db cargo test -p codex-core --test all rollout_list_find
• RUST_MIN_STACK=8388608 CODEX_SKIP_VENDORED_BWRAP=1 CARGO_TARGET_DIR=/tmp/codex-target-state-db cargo test -p codex-core --test all rollout_list_find::find_prefers_sqlite_path_by_id -- --nocapture
• RUST_MIN_STACK=8388608 CODEX_SKIP_VENDORED_BWRAP=1 CARGO_TARGET_DIR=/tmp/codex-target-state-db cargo test -p codex-core --test all rollout_list_find -- --nocapture
• CARGO_TARGET_DIR=/tmp/codex-target-state-db cargo test -p codex-core interrupt_accounts_active_goal_before_pausing
• CARGO_TARGET_DIR=/tmp/codex-target-state-db cargo test -p codex-app-server get_auth_status -- --test-threads=1
• CODEX_SKIP_VENDORED_BWRAP=1 CARGO_TARGET_DIR=/tmp/codex-target-state-db cargo test -p codex-app-server --lib
• CODEX_SKIP_VENDORED_BWRAP=1 CARGO_TARGET_DIR=/tmp/codex-target-state-db cargo check -p codex-rollout -p codex-app-server --tests
• CARGO_TARGET_DIR=/tmp/codex-target-state-db just fix -p codex-rollout -p codex-thread-store -p codex-core -p codex-app-server -p codex-tui -p codex-exec -p codex-cli
• CODEX_SKIP_VENDORED_BWRAP=1 CARGO_TARGET_DIR=/tmp/codex-target-state-db just fix -p codex-rollout -p codex-app-server
• CARGO_TARGET_DIR=/tmp/codex-target-state-db just fix -p codex-rollout
• CODEX_SKIP_VENDORED_BWRAP=1 CARGO_TARGET_DIR=/tmp/codex-target-state-db just fix -p codex-core
• just argument-comment-lint -p codex-core
• just argument-comment-lint -p codex-rollout

Focused coverage added in codex-rollout:

• recorder::tests::state_db_init_backfills_before_returning verifies the rollout metadata row exists before startup init returns.
• state_db::tests::try_init_waits_for_concurrent_startup_backfill verifies startup waits for another worker to finish backfill instead of disabling the handle for the process.
• state_db::tests::try_init_times_out_waiting_for_stuck_startup_backfill verifies startup does not hang indefinitely on a stuck backfill lease.
• tests::find_thread_path_accepts_existing_state_db_path_without_canonical_filename verifies DB-backed lookup accepts valid existing rollout paths even when the filename does not include the thread UUID.
• tests::find_thread_path_falls_back_when_db_path_points_to_another_thread verifies DB-backed lookup ignores a stale row whose existing path belongs to another thread and read-repairs the row after filesystem fallback.

Focused coverage updated in codex-core:

• rollout_list_find::find_prefers_sqlite_path_by_id now uses a DB-preferred rollout file with matching session_meta.id, so it still verifies that valid SQLite paths win without depending on stale/empty rollout contents.

cargo test -p codex-app-server thread_list_respects_search_term_filter -- --test-threads=1 --nocapture was attempted locally but timed out waiting for the app-server test harness initialize response before reaching the changed thread-list code path.

bazel test //codex-rs/thread-store:thread-store-unit-tests --test_output=errors was attempted locally after the thread-store fix, but this container failed before target analysis while fetching v8+ through BuildBuddy/direct GitHub. The equivalent local crate coverage, including cargo test -p codex-thread-store, passes.

A plain local cargo check -p codex-rollout -p codex-app-server --tests also requires system libcap.pc for codex-linux-sandbox; the follow-up app-server check above used CODEX_SKIP_VENDORED_BWRAP=1 in this container.