Owen Lin b24aa20107 Resume thread history projection from its SQLite checkpoint (#32928) ...

## Why

Thread history JSONL is the durable source of truth, while SQLite is a rebuildable view. If a SQLite projection fails after a durable append, the next write must catch up the unprojected suffix instead of skipping it.

## What changed

- Start materialization at the byte offset stored in `thread_history_projection_state`.
- Project only complete newline-terminated rollout records, leaving a trailing partial record for a later pass.
- Preserve validation for missing files, invalid offsets, and missing or out-of-order ordinals without advancing projection state.

## Testing

Add coverage for catching up after projection failure, avoiding replay when already synchronized, retaining partial lines, and rejecting invalid suffixes without changing SQLite state.

GitOrigin-RevId: 8a7200a77edd5411ddf5fe31ab6af5ee287ed7d7

2026-07-14 02:22:57 +00:00

..

local

Resume thread history projection from its SQLite checkpoint (#32928)

2026-07-14 02:22:57 +00:00

error.rs

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

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

in_memory.rs

Load model context from a bounded rollout suffix (#32896)

2026-07-13 23:29:59 +00:00

lib.rs

Load model context from a bounded rollout suffix (#32896)

2026-07-13 23:29:59 +00:00

live_thread.rs

feat(rollout): persist TurnItems for paginated thread rollouts (#30188)

2026-07-08 19:55:03 -07:00

store.rs

Load model context from a bounded rollout suffix (#32896)

2026-07-13 23:29:59 +00:00

thread_metadata_sync.rs

Make advanced reasoning selection explicit in the TUI (#32746)

2026-07-13 09:40:51 +00:00

types.rs

Materialize paginated thread history in SQLite (#32923)

2026-07-14 02:00:39 +00:00