Shares the browser state this flow produces with the rest of a cloud plan run.
Tests that reach the flow before any state has been stored each run it and store
their own result. The tests in a plan stage start together, so that is the common
case; a test that starts once state already exists for the same application and
credentials begins from that stored state instead.
To sign in once per plan run, put a test that runs this flow in an earlier plan
stage, against the same application URL and with the same credentials. Stages run
in order, so the tests of later stages all start from the state that test stored.
A marked flow still runs every time. It is not skipped, so it must decide for
itself whether there is anything left to do — a login flow, for example, should
wrap its sign-in steps in a condition that only holds when the login page is
actually showing. A marked flow that unconditionally repeats its work will do so
on a browser that already carries the session.
The stored state lasts only for the plan run. Has no effect on local CLI runs.
