Automation Replay Gate — Workflow Failure QA

Illustrative missing-evidence receipt; no workflow, service, or sandbox was run.

Workflow artifact/version: not supplied. Trigger, input schema, task-store effect, notification effect, idempotency key, retry policy, and recovery path need to be extracted from the actual artifact before assertions can be set. Proposed versioned fixtures are: one normal event; two deliveries with the same event ID; a timeout after a stubbed task-store commit but before acknowledgment; and a notification failure after the task effect. Each fixture must record initial state, ordered effect journal, retry count, final state, expected result, and actual result.

Isolation status: not proved, because there is no harness to inspect. The agent must confirm that every outbound path, including error and retry branches, is stubbed or redirected to disposable state. A control labeled “dry run” is insufficient by itself. All four fixtures are marked not run; no effect count is invented. Verdict: HOLD. Next proof: provide the workflow artifact, documented effect and retry contracts, synthetic input, and an isolated runner; then run the four cases and compare observed state with predeclared assertions. Even a later PASS would apply only to that isolated fixture set, not to live provider behavior or permission to activate the workflow.