`torus panic`

Nobody has claimed this yet.

```
$> torus panic
Take a deep breath. You don't have to panic.

Did you lose your paper key, or has someone else seen it [y/n]? n
Did someone else get access to your passphrase [y/n]? y

Ok. It's going to be fine. First, you'll have to pick a new passphrase.
Then, I'll remove your account's access to secrets in any orgs you belong to,
just in case someone bad does have your old passphrase and tries to use it.

Next, I'll let the other members of the orgs know that they need to re-add your
access to the secrets. They'll just need to confirm that it's ok; it won't be much
work for them at all.

Finally, I'll track all of the secrets you used to have access to, and help you and
your friends change the values, in case someone bad did access them.

Let's get started.

Enter your new passphrase:
```

On the hierarchy of fixing oopses, `torus panic` is the final stop:
- `torus profile update`: change your password just because
- `torus profile recover`: (https://github.com/manifoldco/torus-cli/issues/144) Create a new password using your backup paper key, when you've just forgotten it.
- `torus panic`: You've lost your physical paper key, or you suspect someone has stolen your passphrase. Revoke all of your existing access, regenerate your compromised parts, and track secret rotation.

Start by locating the existing `torus profile update` and `torus profile recover` command entry points, then compare their passphrase and recovery flows with the proposed `torus panic` flow. Done means the command handles compromised paper keys or passphrases, revokes affected access, supports secret rotation tracking, and communicates the required org re-authorization steps.

Written by the indexing model from the issue text.