15 Automated Checks All Passed — Yet the Live Demo Was Running the Wrong Version

A developer's release script cleared all 15 automated checks for version 1.8.0, yet the publicly visible demo was still displaying the previous version, 1.7.0. The checks covered version consistency, changelog updates, site availability, and image loading, but none monitored what the demo app itself was actually running. The root cause was that the deploy script published the marketing site wholesale, while the demo was a separately compiled build that nothing had rebuilt or verified. A fix was added to query Flutter's auto-generated version.json file directly from the live URL and compare it against the expected release version. However, a subtler follow-up bug revealed that manually updating the demo's destination folder was undone by the next deploy, which faithfully re-synced the stale source — illustrating that verifying an action was taken is not the same as verifying the deployed artifact.