Owen Lin 19b2273d8a Keep paginated thread Git metadata in SQLite (#34382) ...

## Why

Paginated rollouts contain only the initial Git metadata tuple. Reusing that
tuple during later reads, reconciliation, or resume can overwrite newer SQLite
values and undo explicit field clears.

## What changed

- Treat SQLite as authoritative for Git metadata once a thread is paginated.
- Apply paginated Git metadata patches directly to SQLite without appending
  compatibility metadata to the rollout.
- Preserve explicit null values when reading by rollout path or reconciling the
  initial session metadata, and ignore the initial Git tuple during resume.

## Testing

Added coverage for updating and clearing paginated Git metadata, preserving the
result through reconciliation and rollout-path reads, and avoiding stale Git
metadata updates on resume.

GitOrigin-RevId: 4d3e68cb24965b93d337d923092a98bac9b352b5

2026-07-20 17:23:18 +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

Move memory state to a dedicated SQLite DB (#24591)

2026-05-26 20:07:25 +02:00

migrations

Persist names for paginated threads (#34229)

2026-07-19 21:13:13 +00:00

src

Keep paginated thread Git metadata in SQLite (#34382)

2026-07-20 17:23:18 +00:00

thread_history_migrations

Add occurrence search for paginated threads (#33907)

2026-07-17 21:24:26 +00:00

BUILD.bazel

Add dedicated storage for paginated thread history (#32234)

2026-07-10 18:27:19 +00:00

Cargo.toml

Centralize SQLite connection configuration (#33938)

2026-07-18 02:06:13 +00:00