wrong CLI message on curl+GPG revocation

I just removed my chriscoyne.com https proof (that server is physically unreachable for the next couple days and went down), so I revoked it via hardcore mode.

Instead of the usual "check your browser" message I just got a status code printed in my terminal. Even though it worked:

```
{"status":{"code":0,"name":"OK"},"csrf_token":""}
```

Reproduce the hardcore-mode revocation described in the issue using the curl and GPG flow, and compare the terminal output with the usual browser message. The report names no source file or test, so first locate the CLI path that handles this successful revocation; done means it shows the intended message instead of the JSON status response.

Written by the indexing model from the issue text.