lint-staleness

To identify staleness in lint scan results, evaluate provenance.last_compiled timestamps across flagged entities to classify whether URLs, pricing, or contacts require re-verification versus static but aged information.

Stale lint flags require re-verification of dynamic data like URLs and pricing, while aged-but-stable flags indicate factual information that has aged but remains valid based on provenance data.

Generate a staleness report from lint_scan.json by processing each flagged entity to evaluate provenance timestamps, producing a concise markdown report highlighting items to re-verify and items to leave alone without modifying source data.

The staleness checker does not modify wiki content during lint verification; it enforces a read-only approach that assesses flags and produces a single staleness report while preserving the original source data.

You need to re-verify URLs and pricing in lint scans when provenance.last_compiled timestamps indicate the data is stale, meaning the dynamic information has likely changed and requires active refresh.

You can integrate staleness classification into an existing lint cycle to aid teams in refreshing critical information, using the generated report to prioritize which flagged entities need re-verification without overwriting static knowledge.