I've always thought GOAT stands for Gentleman Of All Trades. I make a wild guess it's Girl Of All Trades in this case?

That's a really neat feature.

Well, yeah. Hard drive failure can force a reinstall. And with laptops there isn't usually another place for a hard drive, from where to restore the system.

Yes. I agreed with you. But I made it sound like something else. Bad wording on my side.

As I'm too Gentoo openrc user. I also use seatd+greetd instead of (e)logind and replacing sysvinit with openrc-init. The availability of choices made me do it!

Yes.

Really the hardest part of desktop linux for a regular, so called "internet user", in the installation.

They don't have no clue how to install an operating system, even windows.

I once installed CentOS workstation for my father on his ThinkPad. Firefox and Libreoffice is all he needs. Automatic updates in the background make sure all the latest security patches are applied. There have been few time when, after the update, the laptop hangs at boot. I've since told him to choose the second-to-last boot option from the "start-up menu" until the fix for the bug has been deployed (usually in within a 24h).

So really using Linux isn't the hard part. Back in 2004 (ish) I went the painful route of installing my first Linux - Gentoo. But boy I learned a lot from it. Yes, I had a helping friend to get me over the hardest parts.

because it’s actually designed modular

Oh? Try to use systemd without logind or journald. logind isn't so bad, but journald was bad enough, that I gave up with systemd.

Rolling with Gentoo here. Reinstall is not performed even when complete hardware upgrade has been done.

Yeah. I keep one root tmux session open on my main PC for administrative tasks.

sudo is a setuid binary, but it’s a fairly simple program

Some people would disagree to this.

The brief description of run0 already has too many potential points of failure.

If the "listener" is PID1, which will run the privileged command, in theory, it would be quite bullet proof (in a working system PID1 is always there). But since this is systemd, PID1 is much more than that and much more complex. On the other hand spawning another daemon from PID1 to be the "listener" makes it, perhaps, even more complicated. You'd have to make sure the listener is always running and have some process supervisor there to watch if it exits... and maybe even a watchdog polling it to make sure it isn't frozen.

So my conclusion is the same as yours:

a solution in search of a problem

We already have a working solution. Have a well written SUID program. I've been using doas for some years now. It's simple enough that I trust it.

Sir, your thinking is certainly what kids call "next-level".

Yeah.

At maximum a bug/issue tracker is needed.

"server"