Keybase does not recognize key after keybase gen

First, thanks for being awesome. I love the idea and appreciate y'all making security more usable.

I've run into an issue where I cannot `keybase push` after adding a couple `uid`s to the key that I generated with `keybase gen`. Here's roughly what I've done so far:

``` shell
> keybase -v
0.1.0

> keybase gen
... follow the prompts ...

> gpg
... adduid, trust, and save ...

> ls -al ~/.gnupg
total 72
drwx------ 10 sethholloway staff 340 Mar 25 16:23 .
drwxr-xr-x+ 95 sethholloway staff 3230 Mar 25 16:23 ..
srwxr-xr-x 1 sethholloway staff 0 Mar 25 16:08 S.gpg-agent
-rw------- 1 sethholloway staff 8948 Mar 25 16:08 gpg.conf
drwx------ 2 sethholloway staff 68 Mar 25 16:08 private-keys-v1.d
-rw------- 1 sethholloway staff 4019 Mar 25 16:19 pubring.gpg
-rw------- 1 sethholloway staff 4019 Mar 25 16:18 pubring.gpg~
-rw------- 1 sethholloway staff 600 Mar 25 16:09 random_seed
-rw------- 1 sethholloway staff 6677 Mar 25 16:18 secring.gpg
-rw------- 1 sethholloway staff 1360 Mar 25 16:19 trustdb.gpg

> gpg --list-keys
/Users/sethholloway/.gnupg/pubring.gpg
--------------------------------------
pub 4096R/B0CBA24D 2014-03-25 [expires: 2024-03-22]
uid Seth Holloway
uid keybase.io/sethholloway
uid Seth Holloway
sub 4096R/C8B33711 2014-03-25 [expires: 2024-03-22]

> keybase -d push
debug: + opening config file: /Users/sethholloway/.keybase/config.json
... load config, lookup user, etc ...
debug: ++ sethholloway: storing signature chain
debug: -- sethholloway: stored signature chain
debug: - sethholloway: loaded user
debug: + sethholloway: check public key
debug: - sethholloway: check_public_key: ret={}; err=undefined
debug: Call to gpg: { args: [ '-K', '--keyid-format', 'long' ] }
error: No local keys found! Try `keybase gen` to generate one.

> gpg -K --keyid-format long
/Users/sethholloway/.gnupg/secring.gpg
--------------------------------------
sec ...
uid keybase.io/sethholloway
uid Seth Holloway
uid Seth Holloway
ssb ...
```

What am I missing?

Reproduce the report with `keybase gen`, the shown GPG UID changes, `gpg -K --keyid-format long`, and `keybase -d push`. Start by tracing the CLI's local-key discovery and compare its GPG invocation with the command that lists the secret key; done means the generated key is recognized and `keybase push` proceeds without the “No local keys found” error.

Written by the indexing model from the issue text.