jif 88ec932e96 Handle fractional rate limits in thread history projection (#36083) ...

## Why

Paginated thread history could reject valid rollout records when rate-limit
percentages were encoded as floating-point JSON values, preventing later final
answers from being projected.

## What changed

Deserialize each rollout line through `serde_json::Value` before converting it
to `RolloutLine`, preserving floating-point rate-limit values during history
materialization.

## Testing

Added coverage for projecting fractional, integral, very small, and large
floating-point rate-limit percentages across both catch-up materialization and
subsequent history appends.

GitOrigin-RevId: 68da907987ffe59f4a3033ef90f3b88c39734cb1

2026-07-30 04:55:09 +00:00

..

local

Handle fractional rate limits in thread history projection (#36083)

2026-07-30 04:55:09 +00:00

error.rs

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

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

in_memory.rs

Add persisted manual ordering for thread sections (#36007)

2026-07-29 18:37:22 +00:00

lib.rs

Add persisted manual ordering for thread sections (#36007)

2026-07-29 18:37:22 +00:00

live_thread.rs

Preserve paginated thread metadata across resumes (#35678)

2026-07-27 22:12:15 +00:00

store.rs

Add persisted manual ordering for thread sections (#36007)

2026-07-29 18:37:22 +00:00

thread_metadata_sync.rs

Preserve paginated thread metadata across resumes (#35678)

2026-07-27 22:12:15 +00:00

types.rs

Add persisted manual ordering for thread sections (#36007)

2026-07-29 18:37:22 +00:00