mirror of
https://github.com/openai/codex.git
synced 2026-11-06 20:20:34 +00:00
## Why Item reads with an update boundary previously rejected forked thread histories and only supported an exclusive lower bound on update ordinals. ## What changed - Add `before_updated_at_ordinal` as an exclusive upper bound, mutually exclusive with `after_updated_at_ordinal`. - Allow update-filtered and update-ordered item reads across parent and child segments, applying segment bounds and preserving cursor pagination in both directions. - Require an update boundary for update-order sorting and reject either boundary when using an item anchor or item-ID filtering. ## Testing Extend thread-store tests to cover upper-bound filtering, descending cursor pagination, forward and backward paging across forked lineages, mutually exclusive boundaries, and ordinals outside SQLite's integer range. GitOrigin-RevId: 63f7e18fb24a89a41ff8e570cf65963622519a25