Caprock Files

Added

• The cache hit rate now says what it means. It was a bare percentage, amber below 90% and identical above — so 99% and 91% read the same and neither said anything, on a figure that runs from 6% to 99.6% across real sessions. One word sits beside it: outstanding at 99%+, good from 95, ok from 85, low below. The bands are set against the observed spread rather than picked for roundness, so outstanding lands on about one session in nine and is worth reading.

It describes a state, not a performance — the cache is Claude Code's doing and Caprock only reads it — and low is a fact rather than a verdict: a short session has little to reuse. Nothing animates; this dashboard sits open all day, and motion here means live data and nothing else.

Added

• The share card asks the reader what theirs is. It carried a figure and a domain and stopped there — someone seeing another person's total had no reason to think it was a thing they could do too. A question, not an install line: a command on a picture is an advertisement and reads as one, and the domain in the heading is where a person who wonders goes to find out.

Fixed

• Dismissing a banner recorded the wrong time. The premium banner, the premium hint and the share nudge all stamped the dismissal with a fresh Date.now() while every other decision in them used the clock they were handed. The two disagreed by however long the render had been on screen — invisible in production, but it meant the test suite passed for a year and then began failing on the day the fixed test clock and the wall clock crossed, with nobody having touched the files. All three use the clock they are given, and the boundary is now tested to the millisecond.