A source-code change can make a release feel finished, but several deployment and cache layers may still sit between the repository and a user's browser. A new file, a newly published artifact, and a newly observed response are three different pieces of evidence.
Not every metric needs to be collected at the same cadence; expensive inventory can be cached without weakening real-time health signals.
Docker storage size is useful, but asking the daemon for deep filesystem inventory on every fast scrape consumed too much monitoring overhead.
One attraction of static publishing is that the authoring server may not need to stay online for readers to receive already-published files. But the boundary of that independence needs to be clear.