A synthetic order-intake event arrives from a webhook/workflow-style export that represents the same buyer problem framed in Mock Job 01: a Shopify-like order, Stripe-like payment signal, or downstream ops handoff is almost valid, but the delivery contains malformed fields, missing routing data, duplicate idempotency state, or an unsafe destination mismatch.
Automation Debugger loads the fixture, assigns a stable trace ID, identifies the primary failure class, proposes deterministic corrections only when safe, and then replays the corrected event against a local mock destination. Unsafe cases, such as invalid webhook signatures, duplicate idempotency keys, unknown event types, and downstream 500 loops, are refused or dead-lettered with a clear reason.
The client gets a concise report showing what broke, why it broke, what changed, whether local replay passed or was refused, and which live-service next steps require explicit approval. In the broader order-intake proof set, this complements api-webhook-bridge green-path evidence and sheets-airtable-sync downstream reconciliation evidence.
Strongest reproducible artifacts for the order-intake failure-path story:
examples/output/diagnosis-malformed-date.jsonexamples/output/diagnosis-duplicate-event.jsonexamples/output/replay-success.jsonexamples/output/replay-refused.jsonexamples/output/fix-report.mddocs/screenshots/05-corrected-replay.pngdocs/screenshots/07-duplicate-guard.png
Safety boundary: fixture_safe=true, live_services_used=false, synthetic_data_only=true.