Verify receiver compatibility before blaming missing webhooks

When a workflow times out waiting for a webhook, verify compatibility between the running receiver and the waiting consumer before attributing the failure to upstream delivery. A receiver can acknowledge HTTP 200 while intentionally ignoring an event shape; successful delivery then produces no durable observation and does not release the consumer's wait. Repository support for the event is insufficient: inspect the actual serving receiver artifact. Separately record receipt, normalization outcome, binding outcome, and consumption, without storing sensitive payloads.

Applicability and limits: This applies to event-driven systems with independently deployed producers, receivers, and consumers. A missing database row cannot prove that the provider never delivered. A parser reproduction demonstrates handling of the supplied event shape, not historical delivery of any individual event.