Owen Lin 69cebb5d15 Route rollout reads through the canonical JSON decoder (#42378) ...

## Why

Directly deserializing the flattened `RolloutLine` envelope can reject nested
decimal values, preventing affected paginated sessions from resuming.

## What changed

- Add canonical string, byte, and reverse-scanner helpers that decode rollout
  records through `serde_json::Value` before decoding the flattened item.
- Route rollout readers across session discovery, history, migration, search,
  thread storage, and transcript previews through those helpers.
- Remove `Deserialize` from `RolloutLine` so new readers cannot bypass the
  canonical persistence decoder.

## Testing

Add coverage that resumes a paginated rollout after a token-count record with
a decimal rate-limit value and verifies that ordinal sequencing continues.

GitOrigin-RevId: 49abac1e0751c073daa5a93a840d8a483fd2d013

2026-09-02 22:45:19 +00:00

..

src

Route rollout reads through the canonical JSON decoder (#42378)

2026-09-02 22:45:19 +00:00

tests

Add structured asynchronous user input requests (#42178)

2026-09-02 02:09:35 +00:00

BUILD.bazel

[codex] Shard exec Bazel integration test (#19862)

2026-04-27 21:22:53 +00:00

Cargo.toml

Include shared histories in rollout compression (#42039)

2026-09-01 12:23:20 +00:00