If your needs are met otherwise stick to that and move on.

Not everything needs to fit your needs, including the documentation. Bizarre how you seem to think someone else owes you answers to questions you don't seem to want to try and answer yourself.

Since I am here though and find this project actually interesting; I like the idea of systems that offer, overall, the same utility but are implemented to be as minimal as possible. LLMs are exactly that; look at all the utility from some for loops sorting a huge pile of data. So a harness that's also minimal at its core and endlessly self extending just corner cases unlike pi's ponytail skills which ironically packs a ton of opinions into a workflow up front, pitching the minimalism it aspires to in the bin, seems like a Homer car to me.

But I am a hardware engineer biased by experience with minimalism; I got a single data structure (electromagnetism) to manipulate and BOMs that come with hard constraints.

On the contrary, web SaaS devs want to run a business/rocket to the moon moreso than be an engineer. As such git pulling, pip installing the world allows them to focus on their get rich quick with as little labor involved as possible goal front and center.

> Bizarre how you seem to think someone else owes you answers to questions you don't seem to want to try and answer yourself.

This, of course, depends on your goals, but if your goal is for your project to reach more people for whom it is relevant, it is not crazy to provide some basic motivation.

"Why anyone should use this" is the fundamental question that anyone building something with the intention of other people using it should be thinking about. For example, Pi agent provides lots of information on the thinking and motivation behind the design. Even if I don't use the project, I come away learning something interesting.