Apply to host an event

Steps

1. 1 Guest A first-time host starts an application 0:11 ▣

   No account, no prior application. This is the only host the account gate exists for, and the only one prefill cannot help.

2. 2 Guest They fill in the night they have in mind 0:14 ▣

   Event name, date, headcount, bar minimum and a description — ten minutes of typing, and four different kinds of input.

3. 3 Guest They notice 'Log in to pre-fill' and go to sign in 0:16 ▣

   A FULL PAGE NAVIGATION — `/login?next=/host/apply`. This is the moment the owner's note describes, and the moment the form used to be lost.

4. 4 Guest They sign in 0:17 ▣

   Standing in for the Google hop: the property under test is that the TAB survived a navigation off-site and back, which is the same for any identity provider.

5. 5 Guest Back on the application 0:26 ▣
6. 6 Guest When does the night end? 0:28

   The one anchor. Everything after it is a duration, walked backwards from here.

7. 7 Guest …Midnight 0:29
8. 8 Guest How long does the headliner play? 0:30
9. 9 Guest …2 hours 0:31
10. 10 Guest How long is clean-up? 0:33
11. 11 Guest …1 hour 0:34
12. 12 Guest How long do the openers play? 0:35
13. 13 Guest …1 hour 0:36
14. 14 Guest How long is setup? 0:38
15. 15 Guest …1 hour 0:39
16. 16 Guest How long before the first act do doors open? 0:40
17. 17 Guest …30 min 0:41
18. 18 Guest They still have to type their own name, email and phone 0:43 ▣

    They signed in two beats ago. The server knows the email — it just authenticated it — and the form asks anyway.

19. 19 Guest They press submit 0:44 ▣

    Complete this time. A stale CSRF token restored from storage would fail here, and that is the failure this beat exists to rule out.

20. 20 Guest No poster yet — they skip the prompt 0:47 ▣