Three applications, not three screenshots.
Each of these runs in this page, on the binding you pick, from the flow definition printed below it. They are the same applications the end-to-end suite drives, so nothing is shown here that the engine cannot do.
R-A
Change your answer. Keep the right data.
Onboarding with a conditional branch and backtracking. The payer type decides the route, the visitor walks back across the branch, and the flow says what is submitted and what is forgotten.
whenon.nextback() across branchesclearOnLeaveR-B
Reload halfway through. Continue safely.
A form that survives F5, checks a name against a service that takes its time, and is not corrupted by a reload in the middle of that check.
persistthe snapshot contractbusythe navigation epochR-C
Add passengers. Revisit any passenger.
One block of steps per passenger: add and remove them, then go back and edit the second after finishing the third.
GroupSteprepeatthe frame stackkeyBy