Symptom. The Conformity workflow is red; the "Deploy to Pages" job shows as skipped; the live site still shows the previous build.
Steps
- Open the failed run, or run the dry run locally: the last line names each check with its result.
- Read the failing check's evidence lines at /conformity/ or in
conformity/latest.json. Each line names the file and the reason. - Fix by type:
site.consistency: add the missing sitemap entry or canonical link, or make the link root-absolute.placeholders: replace the placeholder with the real text or remove it.rules.blocking: rewrite the sentence. If the hit is a false positive, record it with the gate owner as well.predictions.hashes: a hashed prediction changed. Restore the file; predictions are never edited after hashing.
- Run the dry run until it prints
overall=pass, thengit pull --rebaseand push.
A chained command such as grep -o 'overall=[a-z]*' && git push pushes on a failing run, because grep succeeds on overall=fail. Compare the value: [ "$R0" = "overall=pass" ] && git push. This happened on 2026-10-08; the gate blocked the deploy.