Authorization of new device with device files but not device?

I tested Keybase in 2017 and it didn't have the feature set my work required, and I'm super excited to say now it does! However, I no longer have the devices that I tested it within 2017 and with my account, I grabbed team names relevant to the organizations I do work with.

I'd prefer not to reset/wipe my account and not be able to use the team names I grabbed. If I will still be able to use them then it's fine. That's my only concern.

I can currently log into my account (with email and password). And I have OSX timemachine backups of my old keybase files with a little hunting I found what appears to be the main private key

`MBPR-SSD/Users/--USER---/Library/Application\ Support/Keybase/secretkeys.--USER--.mpack`
(the rest of the folder is also present if needed)

Anyway I can authorize my account again? Thanks!

Start with the backed-up secretkeys.--USER--.mpack file and the rest of the Keybase application-support folder described in the report, then trace the account and device authorization entry point. Done should be defined as determining whether the account can be reauthorized from the available credentials without resetting it or losing its team names.

Written by the indexing model from the issue text.