## Why
Repeated tool output, such as the same image returned in several results,
can consume the trace bundle budget. When output bytes are unavailable,
the surrounding result can still carry terminal metadata and conversation
links.
## What changed
- Store JSON string values of at least 64 KiB, measured after encoding,
separately from their tool result or runtime event. Identical encoded
values share one record per bundle, while each occurrence retains its
position and complete captures reconstruct the original JSON bytes.
- Keep separate compression shards open for content and surrounding
records. Budget for the serialized event and fall back to a single
capped or omitted payload when the split layout or its references
exceed the applicable limit.
- Track missing values separately from literal `null` so reduction can
preserve surviving terminal metadata and keep tool output IDs attached
to their original items.
## Testing
Add regression tests for shared image and text payloads, byte-for-byte
reconstruction, recording completion under tight bundle limits, and
reduction with missing output.
GitOrigin-RevId: a003197ea998639b6c2ae27f408990c0186406bd