Oversized MCP results and saved media now write through the storage layer explicitly.
What's wrong with this entry?
Oversized MCP tool results, binary content blocks, MCP task results and their image and audio saves now pass storage and credential arguments to the file writer instead of relying on defaults, and the task poller carries credentials through its post-restart resume. The saved-output hints you see are unchanged, and the existing kill switch for large output files still applies.
[The portion truncated above was not saved: the per-result persist budget is exhausted.]
Strings lifted out of the shipped bundle, so the claim above can be checked against them.