Replaced key causes check failures

In #1926 I replaced an old, expired key. Its ghost is haunting me still.

In trying to use keybase encrypt djmitche, a colleague of mine sees:

▶ INFO Identifying recipient djmitche
✔ <tracked> public key fingerprint: D809 7934 A92E 4B42 1036 8102 FF8B 7AC6 154E 3226
✔ <Deleted proof: c03d5638bd2b4356e8a39fe07625403d7f0d15b1> public key fingerprint: C03D 5638 BD2B 4356 E8A3 9FE0 7625 403D 7F0D 15B1
You last tracked djmitche on 2016-03-18 11:11:37 PDT
✔ <tracked> "djmitche" on github: https://gist.github.com/3f35dcb1b37cb279906e [cached 2016-03-18 11:09:37 PDT]
✔ <tracked> admin of code.v.igoro.us via HTTP: http://code.v.igoro.us/keybase.txt [cached 2016-03-18 11:09:37 PDT]
✔ <tracked> admin of DNS zone igoro.us: found TXT entry keybase-site-verification=d7b4WApFG4xXAg1iRTczXLLbYufiWXtG8_WoC2eBJoY [cached 2016-03-18 11:09:37 PDT]
▶ ERROR For user "djmitche": 1 track component failed

the third line is in red, so I'm guessing (despite the checkmark) that's the component that's failing. What can I do to fix this?

Start by reproducing the keybase encrypt djmitche command and inspect the track-component output for the tracked and deleted proofs. Determine why the replaced key still appears during recipient identification; done means the old key no longer causes the command to report a failed track component.