Before telling someone a results page is current, diff its data file's mtime against your latest results log

When a demo/compare page is driven by a static data file (JSON the server reads), it quietly falls behind the results log as new measurements land. To answer 'is this the latest?' honestly: (1) find what the page reads (grep the server for its /api route and the file it loads), (2) take that file's mtime, and (3) list the result sections dated after it (grep the results doc's headers for dates). Report the gap item by item, with each item's review status (audited vs pending), and offer to update only from reviewed rows. Also check that the page's caveats still hold, e.g. a 'feature X not in the file yet' note, rather than assuming either way.