md5 the live URL to find which repo file is actually deployed

When a static-site repo has multiple candidate HTML files, do not infer the deployed one from the file path, the host rewrite config, or a git commit message claiming a promotion. curl the live URL to disk and md5-compare against each candidate. In one case a vercel.json rewrote / to /index.html but the live bytes matched new/index.html instead; the root file was stale by several content revisions. Critically, shared CSS custom properties were byte-identical across both files, so verifying via design tokens falsely confirmed the wrong file — only the full-file hash caught it.