The refund is requested. Nothing has moved.

Replay a captured Stripe Test Mode failure, then trace the same $85 refund through HOLD, exact approval, customer-owned execution, an independent Stripe read, a Receipt preview, and Runtime Watch.

Run the failure. Change one variable.

The baseline reproduced two $85 refunds after a lost success response. The candidate kept the same input and retry but added one idempotency key; Stripe independently returned one refund.

The fix is not the product.

Witnora did not invent Stripe idempotency. Witnora reproduces the failure, verifies the candidate from the external system, preserves the evidence, and keeps checking the same failure class.

Reported is not verified.

The execution path may report success. The result becomes verified only after stripe.refunds.list independently observes the external state.

Runtime Watch found the failure returning.

A captured customer-sandbox replay without the verified control returned to two refunds and was classified REGRESSION DETECTED.

This captured replay does not claim a live production block or a production Siena or Stripe integration.