I just took a deep dive into the documentation- which is comprehensive - and I feel the complete opposite; the author has a very well refined mental model of a PaaS and has created a modularized source-code expression of that model that I found very interesting. The CI module is called “patrick”, which gave me a chuckle.
You have some good feedback in your post, but I feel like the author may not be trying to replace hosted PaaS; they are essentially using tiny-go to build small distributable wasm modules that can interoperate in a distributed network, which aligns very closely with the localfirst ethos that brings compute and storage out of the datacenter. Does it feel a bit silly to even SAY “client-side CI”? Objectively, yes, but if a future architecture might need to safely deliver code to clients in a mesh this is a really interesting way to experiment with solutions.