Pushing to a git repo fails - worktree should be provided

```

> ls -la
drwxr-xr-x - avioli 9 Jul 10:50 .git
.rw-r--r-- 150 avioli 9 Jul 10:11 docker-compose.yaml
.rw-r--r-- 260 avioli 9 Jul 10:09 Dockerfile
.rw-r--r-- 184 avioli 9 Jul 10:28 Home.md
.rw-r--r-- 32 avioli 9 Jul 9:45 readme.md

> keybase git create --team=stamatovs wiki
Repo created! You can clone it with:
git clone keybase://team/stamatovs/wiki
Or add it as a remote to an existing repo with:
git remote add origin keybase://team/stamatovs/wiki

> git remote add origin keybase://team/stamatovs/wiki

> git push -u origin master
Initializing Keybase... done.
Syncing with Keybase... This operation conflicted with another operation on the server, or it took too long. Please try again.
git-remote-keybase error: (1) This operation conflicted with another operation on the server, or it took too long. Please try again.

> git push -u origin master
Initializing Keybase... done.
Syncing with Keybase... worktree should be provided
git-remote-keybase error: (1) worktree should be provided

> git push -u origin master
Initializing Keybase... done.
Syncing with Keybase... worktree should be provided
git-remote-keybase error: (1) worktree should be provided

> keybase --version
keybase version 4.1.0-20190612165948+952fee6c59
```

my log id: 63151da48f044a9354c5fd1c

No source file or test is named. Reproduce the failure with the shown `git push -u origin master` commands against the Keybase remote, using the reported client version and log ID, then trace the git-remote-keybase path that reports “worktree should be provided.” Done means the push succeeds or the failure is reported with a clear, covered regression case.

Written by the indexing model from the issue text.