fix: recognize dynamic site deployment runs

[lyc-aon]

Problem

The maintainer matched the site workflow by both its stable path and the literal name Deploy project site. The workflow now defines a dynamic run-name, so a successful exact-commit v0.1.23 site deployment was misclassified as terminal/stale. That sent the compatibility flow back to Sol instead of adopting the public release.

Fix

• identify site deployment runs by stable workflow path, exact commit, and workflow_dispatch event
• retain status/conclusion checks and exact CI/release workflow checks
• make maintainer fixtures use the real dynamic site run-name
• assert the contract never relies on the dynamic site name

Verification

• bash -n ops/t4-maintainer/run.sh
• git diff --check
• node --test scripts/t4-maintainer-contract.test.mjs scripts/t4-maintainer-integration.test.mjs (195/195)

This is a production blocker for adopting and deterministically deploying the already-published immutable T4 Code v0.1.23 release.