Shutting the project down gracefully doesn't mean it has to end, and it doesn't mean failure: shutting down the project gives invested community members the chance to fork it and demonstrate that they want to put the work in to run a natural successor to your project, and people will naturally gravitate towards the best fork over time. Afterall, without people with a vision leading it, it's just code.
Handing over ownership feels cleanest but it's rarely the best outcome (unless you're handing it over to a natural successor).
Just wanted to say thank you for creating and support jsweet all these years :) I hope you find a good owner.