Rhythm staff work across customers' stuck payments, and each customer sees the staff action in its own trail

Verification Boundary

This API journey suite exercises the acceptance journey for rhythm staff work across customers' stuck payments, and each customer sees the staff action in its own trail. Its registration records the executable definition; no run result is asserted.

What This Suite Proves

The suite contains executable checks, but no detailed scenario binding is verified in this pass.

What It Does Not Prove

Some steps report missing harness support. Those steps do not supply executable product proof. A mock run does not establish deployed persistence, provider effects or service authorization. The suite does not establish a complete feature sequence merely because it visits several screens.

Real Dependencies and Test Doubles

The deployed mode uses the acceptance service clients and reads resulting records. The mock mode substitutes service responses through the harness; neither mode requires a browser interaction in this file.

Must Not Be Doubled

The service operations and resulting-record assertions for a claimed API outcome must execute. A deployed claim requires the actual persistence effects checked by that step.