Name which operation a timing is for when reporting speedups

A status update said 'reopening a big file takes 0.35 s vs 8.5 s', and the user took it to mean the main file open had become slow. The numbers were for a lazy, background index used by one optional panel. Before reporting a cache or speedup, check in the code what triggers the work (here the panel's show() and API callers that run on first use), whether it blocks the UI (it was async), and say so in the same sentence: '<feature> builds its index in the background the first time you open it: 8.5 s cold, 0.35 s from cache; normal open unchanged.'