It's a little weird to see this pattern, where we await one Promise and but then don't await the subsequent one.

It would be good to add a code comment explaining why we're doing this:

1. verifyUserLoggedIn needs to be awaited because:
   • Currently, the code for getting one-time keys to initiate the notif ratchet could have a race with the verifyUserLoggedIn code, leading to one-time keys getting erroneously marked as published. This will no longer be true after we update that code to source one-time keys from identity service, but...
   • In the future, we expect that having a commServicesAccessToken will be required for normal keyserver functioning
2. On the other hand, createAndMaintainTunnelbrokerWebsocket doesn't need to be awaited because:
   • The connection to Tunnelbroker isn't strictly necessary for normal keyserver functioning at this time
   • The call to createAndMaintainTunnelbrokerWebsocket doesn't return anything that we need ahead of forking the Express server threads

Please apply this feedback to every place in the diff that it applies to

You should not be awaiting something that doesn't return a promise

Please apply this feedback everywhere

If we're not doing anything with err, we can omit it

Minor changes

My feedback from the last review appears to have been ignored:

{F695889}

Remember – a reviewer should never have to repeat feedback. This is a common issue for you... please review feedback carefully before updating a diff. Go line by line for each comment you received, and make sure you addressed it 100%. It shouldn't ever be necessary for me to repeat feedback to you.