Files
codex/codex-rs/thread-store/src
Charlie Marsh bc4a2544b8 Resolve fork ancestry lazily for descending history pages (#61840)
## Why

Reading the newest turns or items in a fork previously resolved the entire rollout lineage, even when the page only needed recent segments. This caused unnecessary ancestor reads and could fail when an unused ancestor was missing.

## What changed

Introduce an incremental `LineageWalk` and use it to resolve descending history pages only as far as needed for the cursor, requested rows, and next-page lookahead. Defer sibling rollout discovery until a parent is needed, while preserving newer turns' overrides when resuming in an ancestor.

Keep full lineage resolution for ascending reads, update replay, item anchors, and inherited summary lookup.

## Testing

Add regression coverage for pages with missing unused ancestors, continuation within a parent, turn overrides, inherited summaries, and exact page-boundary lookahead. Extend coverage for descending item pages using the selected rollout.

GitOrigin-RevId: dad941f4f3c54a46121d4fa22b69e13f1830a385
2026-11-16 16:37:03 +00:00
..