Feature summary (what you would like to be able to do and where):
Following T428992: Remove the override cookie there is no way to test in production experiments that span multiple pages (I was aware of the downsides but that function was very very useful).
My use case for the removed feature was testing a login/sign up workflow in production. The login workflow can be tested locally (thanks to header-based override in local dev) but in production works very differently so it would be risky to launch an experiment without careful end to end testing.
Note: We had some issues in the last experiment we ran (T424561#12009944) where we didn't successfully log accounts created due to auth.wikimedia.org dropping important query string parameters that were vital for the instrumentation so I'm keen to test this in a production environment. CentralAuthPostLoginRedirect is not super reliable right now because of an infrastructure issue T425262: Use a more reliable storage mechanism for SUL3 state during login.
Use case(s) (list the steps that you performed to discover that problem, and describe the actual underlying problem which you want to solve. Do not describe only a solution):
Benefits (why should this be implemented?):