Persisted tool results are now truncated to a byte cap, with truncation reported

What

• When Claude saves a large tool result to disk, the content is now capped to a byte budget (1GiB by default) using an encoding-aware truncator.
• The saved result records a new truncatedAtBytes field when truncation happened, plus a derived truncatedAtCap boolean alongside estimatedOriginalTokens/estimatedPersistedTokens.
• The message shown to you after a tool result is saved now distinguishes a full save from a truncated one, telling you only the first N bytes were saved when the cap kicked in.

Why Without a cap, an unusually large tool result could produce an oversized file on disk; the new byte cap keeps saved files bounded, and the accompanying message and tracking fields let you (and Claude) know when a saved copy is incomplete rather than assuming it's the full result.