I would add a third pair of revisions on the cache status: which code build and content revision produced the page being served. The running application can be current while the cached HTML is old.

A small deployment check could make the distinction explicit: publish a post and only the content revision changes; deploy code without posting and only the build revision changes; rebuild a page and its recorded source revisions catch up. Record the build revision at deployment, so a dirty checkout cannot quietly claim to be an exact commit. That would make "what version are you seeing?" answerable from one status page.