Keybase git repos not working

Most of the git repos in one of my teams have not been working for several months.

I can't clone them ...

```
$ git clone keybase://team/teamname/obsidian-personal
Cloning into 'obsidian-personal'...
Initializing Keybase... done.
Syncing with Keybase... done.
git-remote-keybase error: (1) Server: block does not exist

$ git clone keybase://team/teamname/obsidian-work
Cloning into 'obsidian-work'...
Initializing Keybase... done.
Syncing with Keybase... done.
git-remote-keybase error: (1) Server: block does not exist
```

And I can't delete them ...

```
$ keybase git delete --team teamname obsidian-personal
Deletion is permanent. Are you sure you want to delete "obsidian-personal"? (type 'YES' to confirm): YES
▶ ERROR (code 2704)
$ keybase git delete --team teamname obsidian-work
Deletion is permanent. Are you sure you want to delete "obsidian-work"? (type 'YES' to confirm): YES
▶ ERROR (code 2704)
```

FWIW I was able to recover their contents by rsync'ing the raw files from the `/keybase/team/teamname/.kbfs_git/` directory (I told one of the devs about this at the time), and I created the repos under a different team where they seem to be working okay, but it would be nice if these non-working repos could be deleted, especially where they can't be cloned anymore (I'm assuming "Server: block does not exist" means exactly what it sounds like, i.e. one or more of the S3 encrypted data storage blocks are just plain gone).

My log id: fc0e299da940ee6a52542f1c

And here's the number 345567, to make your bot happy.

Start by reproducing the reported git clone and keybase git delete commands for the affected team repositories, using the provided log id to inspect the failure. Review the raw repositories under /keybase/team/teamname/.kbfs_git/ and determine what behavior should be restored; done means the repositories can be handled without the reported block-not-found and deletion errors.

Written by the indexing model from the issue text.