both ~/.config/Keybase and ~/.config/keybase are created and used

Looking in my ~/.config/, I see this:

$ ls -lad .config/?eybase
drwx------ 2 rsrchboy rsrchboy  56 Oct  8 12:31 .config/keybase
drwx------ 4 rsrchboy rsrchboy 141 Oct  8 12:30 .config/Keybase

This feels... wrong. Like "expecting a case-insensitive filesystem" wrong.

I've been called insensitive before (usually in a very insensitive way), but I'm very sensitive as to the case sensitivity of my filesystems (FWIW, XFS under Ubuntu trusty). This has to be a bug, yes?

Here's the contents of those directories:

$ ls -la .config/?eybase
.config/keybase:
total 12K
drwx------  2 rsrchboy rsrchboy   56 Oct  8 12:31 .
drwx------ 55 rsrchboy rsrchboy 4.0K Oct  8 15:52 ..
-rw-------  1 rsrchboy rsrchboy  287 Oct  8 12:31 config.json
-rw-------  1 rsrchboy rsrchboy  692 Oct  8 12:31 secretkeys.rsrchboy.mpack

.config/Keybase:
total 16K
drwx------  4 rsrchboy rsrchboy  141 Oct  8 12:30 .
drwx------ 55 rsrchboy rsrchboy 4.0K Oct  8 15:52 ..
-rw-rw-r--  1 rsrchboy rsrchboy  233 Oct  8 16:46 app-state.json
drwx------  2 rsrchboy rsrchboy   85 Oct  8 12:32 Cache
-rw-r--r--  1 rsrchboy rsrchboy 7.0K Oct  8 12:32 Cookies
-rw-r--r--  1 rsrchboy rsrchboy    0 Oct  8 12:32 Cookies-journal
drwx------  2 rsrchboy rsrchboy   70 Oct  8 12:30 GPUCache
lrwxrwxrwx  1 rsrchboy rsrchboy   20 Oct  8 12:30 SingletonCookie -> 16296146868386552595
lrwxrwxrwx  1 rsrchboy rsrchboy   12 Oct  8 12:30 SingletonLock -> athena-23379
lrwxrwxrwx  1 rsrchboy rsrchboy   47 Oct  8 12:30 SS -> /tmp/user/1000/.org.chromium.Chromium.ozNxUW/SS

No source file, test, or entry point is identified. Start by tracing where the client creates or selects ~/.config/keybase and ~/.config/Keybase on a case-sensitive filesystem, then reproduce the directory split and define which single path should remain before adding coverage.