You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
Cost TrackingArea: what it touches
Internal ChangesKind: in v2.1.251,
Internal ChangesSection of the release
What
Cost estimation now chooses a one-hour cache lifetime when a longer-TTL override is configured or the request comes from the interactive session's main thread, and five minutes otherwise, so estimates match the cache tier actually used.
Evidence
return nM("repl_main_thread") ? "1h" : "5m";
Strings lifted out of the shipped bundle, so the claim above can be checked against them.