Tool result / binary content / hook output persistence now falls back to an in-transcript truncation preview when disk save is unavailable

Large tool results, hook outputs (output from custom scripts that run at certain points), and binary content are normally saved to disk when they're too big to keep in the conversation directly. When disk storage isn't available to save them, Claude Code now builds a truncated preview shown inline in the conversation, marked with an explicit <truncated-output> label and a message explaining that the output was too large, couldn't be saved, and only the first part is shown.