Decode cache_creation_input_tokens from the result event and surface it alongside cache_read in the spike console and the app transcript row, so a session's prompt-cache write/read split is visible. Cache writes (billed at a premium) were previously invisible, making cache-thrash impossible to diagnose from the UI. Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>