Inconsistent tracking status website vs. CLI

The website and the CLI are giving me different results for who I am tracking.

How I got there is:
1. Setup keybase with a website generated key and play around a bit including following a couple people.
2. Decide I wanted to use the service but without keybase hosting my private key
3. Nuke the keybase generated key and use a local GPG generated key instead, uploading only the public part.
4. Track a few more people.

The result of this process in an inconsistent list of who I'm tracking:
- The web interface now only shows everybody I've ever tracked.
- The CLI shows only the people I have tracked using me new key pair.

Using the CLI to re-track people brings the lists in sync, but it's entirely unclear from the UI that this needs to be done or why.

Start by reproducing the key migration described in the issue: replace the website-generated key with a local GPG key, then compare the tracking lists in the website and CLI. Trace how each interface determines tracked users; done means both lists agree or the UI clearly explains why re-tracking is required.

Written by the indexing model from the issue text.