I think it wouldn't be too much to ask to have the file try to decrypt every time the passphrase is updated (maybe with a debounce), then present the name of the database ahead of "Start sign-in" once the passphrase is valid
Also, if there's an existing event, it should check if the event name matches, and either stop the user from using the new list, or give them an opportunity to "switch lists" if there's been an organizational dysfunction and they somehow started with the list from a previous event (this is something that would also be facilitated by #14).
I think it wouldn't be too much to ask to have the file try to decrypt every time the passphrase is updated (maybe with a debounce), then present the name of the database ahead of "Start sign-in" once the passphrase is valid
Also, if there's an existing event, it should check if the event name matches, and either stop the user from using the new list, or give them an opportunity to "switch lists" if there's been an organizational dysfunction and they somehow started with the list from a previous event (this is something that would also be facilitated by #14).