A contract fixture that a consumer stopped publishing

Four consumer-authored fixtures fetched nightly, and one that stopped updating in November.

the fetch job pulls each consumer's published fixture
and runs it against a live instance.

integrator-C's fixture last changed 2025-11-04.

which could mean:
  their integration has not changed  — plausible
  they stopped publishing            — also plausible
  their repository moved             — it had

and the check that distinguishes them: the fetch
returning 404 rather than an unchanged file. it had
been returning a cached copy from our own storage.

A fetch that falls back to a cached copy on failure is being helpful and is hiding the only signal available. Failing the job when the source is unreachable, rather than using the last known fixture, is the correct behaviour and makes a consumer’s repository move visible within a day.