Who hears that something happened

Steps

1. 1 None Offstage: provisioning an event to sell (the instance had none on sale) 0:01
2. 2 Member Open the event as member 0:06 ▣
3. 3 Member Buy one General Admission ticket 0:07

   Reserving takes the seat out of inventory and starts a 5-minute hold; the countdown on the next page is that hold.

4. 4 Member The hold timer is running on the checkout page 0:08 ▣

   If the hold expires the seat goes straight back into inventory — the scheduler sweeps it, nobody has to click anything.

5. 5 Member Pay for the order 0:09 ▣

   Charged through the mock payments adapter with token tok_success.

6. 6 Member Land back on My Club, purchase confirmed 0:11 ▣

   The hub is where a member already lives — tickets, credit, listings and comps — so the purchase confirms in context rather than on a receipt page they have to navigate away from.

7. 7 Member Open the site menu 0:12

   The collapsed bar is one row at every role; the full role-gated navigation lives in this panel and closes as soon as you leave.

8. 8 Member The ticket is in the wallet 0:13 ▣
9. 9 Member The ticket, before anything goes wrong 0:14 ▣

   A paid ticket to a night that is going ahead.

10. 10 Member Offstage: the venue cancels the night, and has to say why 0:16
11. 11 Member Back to the tickets they paid for 0:18 ▣

    Nothing about this page changed when the night was called off. The card showed the TICKET's status — still `issued` — so it offered a QR code and a Sell button for a show that is not happening.

12. 12 Member The same page on a desktop 0:20 ▣

    The venue's reason travels with the cancellation, on the one surface the member actually holds.