ambitious success/fail output with 'key base track' (GPG In the background)

This is probably clearer if you can see the syntax highlighting so I'll try to attach an RTF of the output as well (Edit: RTF not supported. I guess I'll screenshot it.)


I've just performed two track operations which have succeeded, but the console output is a little ambiguous as to whether I had or not, due to a nonzero exit code from GPG in the background (which appears to be propagated to a nonzero exit code in key base)

```
$ keybase track kinnison
info: ...checking identity proofs
✔ public key fingerprint: 1956 8523 759E 2A28 58F4 606B 3CCE BABE 206C 3B69
✔ "dsilverstone" on twitter: https://twitter.com/dsilverstone/status/449296873296510976
✔ "kinnison" on github: https://gist.github.com/9819384
✔ admin of www.digital-scurf.org via HTTP: http://www.digital-scurf.org/.well-known/keybase.txt
Is this the kinnison you wanted? [y/N] y
Permanently track this user, and write proof to server? [Y/n] y
info: Updated file: /Users/njd33/.keybase/session.json

You need a passphrase to unlock the secret key for
user: "Jon Dowland "
4096-bit RSA key, ID 0907409606AAAAAA, created 2009-09-14

error: `gpg` exited with code 2
warn: gpg: key 206C3B69: public key "Daniel Silverstone " imported
warn: gpg: Total number processed: 1
warn: gpg: imported: 1 (RSA: 1)
warn: gpg: public key of ultimately trusted key 10E1A997 not found
warn: gpg: 3 marginal(s) needed, 1 complete(s) needed, PGP trust model
warn: gpg: depth: 0 valid: 4 signed: 22 trust: 0-, 0q, 0n, 0m, 0f, 4u
warn: gpg: depth: 1 valid: 22 signed: 27 trust: 22-, 0q, 0n, 0m, 0f, 0u
warn: gpg: next trustdb check due at 2014-06-02
$ echo $?
254
```

Start by reproducing the `keybase track kinnison` command and inspect how the client handles the background GPG exit status. Compare the successful tracking output with the propagated nonzero shell status; done means a successful track is reported unambiguously and does not appear to fail solely because of that GPG result.

Written by the indexing model from the issue text.