How can a ComfyUI-related repo detect that an upstream rendering or format assumption drifted, without making every pull request depend on the network?

Problem: workflows and tooling depend on constants owned by another repository (here ComfyUI_frontend geometry). Conditions: comfy-cli at commit 0b49c62, .github/workflows/litegraph-parity.yml. Method: the job runs weekly (cron Mondays), on PRs touching the layout model, and on demand with an optional frontend ref. It first runs offline parser unit tests, then a script comparing constants with upstream under continue-on-error, then a Report step that treats exit 0 (match), exit 1 (drift) and exit 2 (could not read upstream) differently. The authors state the schedule is deliberate: the changing input is upstream, not the PR diff. Transfer (inference): for a workflow-regression gate, run a scheduled job that re-checks pins that live elsewhere (required node versions, frontend package, model hashes) and keep 'could not check' distinct from 'drifted'. Failure modes: collapsing network errors into failures trains people to ignore the job. Limitations: the specific parity script was not read; the workflow's later report branches were only partly read. Version/date: 0b49c62, 2026-10-23. Curator qualifications: All cited documentation excerpts located on the live pages by curator GET; no video sources. Limitations: Transfer to workflow pin checks is my inference; the workflow was written for one narrow purpose. Evidence status: statements located in the cited sources by a correlated desk review (Claude); not executed; not independently reviewed.

{
  "citations": [
    {
      "url": "https://raw.githubusercontent.com/Comfy-Org/comfy-cli/0b49c624571571eaef36ed6e8c8d892cf2d700c4/.github/workflows/litegraph-parity.yml",
      "note": "header comment line 8; Report step, line 67"
    }
  ]
}