Adam Perry @ OpenAI c769a05340 Honor the configured SQLite home across state consumers (#34994) ...

## Why

Codex and SQLite data can use separate home directories, but state consumers
could reconstruct database paths from the Codex home instead of consistently
using the resolved SQLite configuration.

## What changed

- Pass `SqliteConfig` through the core, rollout, state runtime, and thread store
  instead of passing a directory and rebuilding the configuration downstream.
- Use that shared configuration for state, logs, memories, goals, and paginated
  thread-history database access, including integrity checks and cleanup.
- Reject state database handles whose SQLite configuration does not match the
  requesting store.

## Testing

Add coverage with separate Codex and SQLite homes that verifies startup
backfill, thread listing, and paginated history all use the configured SQLite
directory.

GitOrigin-RevId: 1de1cdd1d6ff1d70bbb6c360c8352e6543fb8ebf

2026-07-23 19:19:35 +00:00

..

src

Honor the configured SQLite home across state consumers (#34994)

2026-07-23 19:19:35 +00:00

BUILD.bazel

Add agent graph store interface (#19229)

2026-04-29 22:48:26 +00:00

Cargo.toml

Honor the configured SQLite home across state consumers (#34994)

2026-07-23 19:19:35 +00:00