fix(ci): deploy Pages once per release instead of twice

[TMHSDigital]

Summary

Closes #215. Every release-worthy push to main started two Pages deploys: one from the push, then one from release.yml's dispatch after the version bump. The dispatch cancelled the first. 8 of the last 9 push-triggered runs were cancelled.

Type

• feat
• fix — CI waste; a single deploy per release
• docs / chore / ci / refactor

Changes

• New gate job in pages.yml. On a push, it takes the first line of each pushed commit (github.event.commits) and applies the same subject test release.yml uses (^(feat|feature|fix)(\(.+\))?!?:|BREAKING[ -]CHANGE). A match means a release will dispatch Pages, so the push deploy is skipped. workflow_dispatch always deploys, and so do non-release pushes (docs:, chore:, …).
• .github/workflows/pages.yml added to its own paths:, so editing the deploy workflow deploys.

Trade-off: if the release job fails after a fix:/feat: push, nothing deploys that push; before, the cancelled-by-dispatch run would have finished. The workflow comment names the recovery: Actions → Deploy GitHub Pages → Run workflow.

Evidence

• live-run-proven (local):

  • pages.yml parses as YAML.

  • The gate's matching was exercised with a Python equivalent of the jq extraction, since jq isn't installed locally:

    Input	Result
    fix(site): x (#209) + body	skip
    feat!: big	skip
    chore(scripts): …	deploy
    docs: fix typo in fix: text	deploy (anchored match)
    docs + fix mixed push	skip
    empty (dispatch)	deploy

• To verify post-merge: this PR is a fix: that touches pages.yml. The merge push should show gate → deploy=false with build-and-deploy skipped, then exactly one successful deploy from the release dispatch.

Checklist

• Explicit paths only.
• Counts and manifest unchanged.
• DCO Signed-off-by: present.
• No credentials, emails, or local paths.

🤖 Generated with Claude Code