I can't speak on behalf of the author, but I have been "stuck" in similar limbo projects myself (an iOS game).
Admitting to yourself that the project has failed, and "just one more push" can't rescue it, and shutting it down is emotionally difficult enough. Handing it over involves finding a suitable recipient, instructing them, transferring domains and accounts, and making sure the clients understand the ownership has changed. And refusing to answer requests for help or documentation over email can be impossible, especially if you cared about the project or its users. Without this documentation and knowledge, a code repository is of almost no use to anyone.
If someone is capable of walking away with zero documentation or help, they would have shut down a limbo project much earlier.
Admitting to yourself that the project has failed, and "just one more push" can't rescue it, and shutting it down is emotionally difficult enough. Handing it over involves finding a suitable recipient, instructing them, transferring domains and accounts, and making sure the clients understand the ownership has changed. And refusing to answer requests for help or documentation over email can be impossible, especially if you cared about the project or its users. Without this documentation and knowledge, a code repository is of almost no use to anyone.
If someone is capable of walking away with zero documentation or help, they would have shut down a limbo project much earlier.