Owen Lin 8d4d57387a Resolve paginated thread history by rollout ID (#38244) ...

## Why

`thread/revert` keeps the logical thread ID while selecting a new immutable
rollout. Using the thread ID for persisted history can therefore read or update
the wrong rollout.

## What changed

- Centralize resolution of a thread's current rollout across live writers,
  SQLite metadata, and filesystem fallbacks.
- Key history materialization, lineage traversal, paging, turn lookup, and fork
  boundaries by immutable rollout ID while retaining the thread ID for the
  logical thread.
- Treat SQLite's selected rollout as authoritative for paginated threads so a
  filesystem scan cannot select an older rollout after `thread/revert`.

## Testing

Add a regression test showing that update-ordinal item paging reads from the
selected rollout ID when it differs from the thread ID.

GitOrigin-RevId: 1101e548a6e6c6d319996e24cb650e5b03ab7fbb

2026-08-12 20:31:52 +00:00

..

local

Resolve paginated thread history by rollout ID (#38244)

2026-08-12 20:31:52 +00:00

error.rs

feat(app-server): add history_mode to thread (#29927)

2026-06-26 09:12:42 -07:00

in_memory.rs

Distinguish turn-start thread persistence (#37926)

2026-08-11 03:35:45 +00:00

lib.rs

Distinguish turn-start thread persistence (#37926)

2026-08-11 03:35:45 +00:00

live_thread.rs

Distinguish turn-start thread persistence (#37926)

2026-08-11 03:35:45 +00:00

queue_store.rs

Add durable per-thread user submission queues (#36952)

2026-08-04 19:23:29 +00:00

store.rs

Distinguish turn-start thread persistence (#37926)

2026-08-11 03:35:45 +00:00

thread_metadata_sync.rs

Extract persisted history types into a dedicated crate (#37871)

2026-08-10 19:26:52 +00:00

thread_sections.rs

Add appearance metadata to thread sections (#37898)

2026-08-10 23:32:42 +00:00

types.rs

Extract persisted history types into a dedicated crate (#37871)

2026-08-10 19:26:52 +00:00