Exactly: that's tight feedback loops. Agents are also capable of reading docs and source code prior to generating new function calls, so they benefit from both of the solutions that I said people benefit from.

As an even more obvious example: students who put wrong answers on tests are "hallucinating" by the definition we apply to LLMs.

This also makes me realize that I sometimes enunciate "the" unvoiced.

Fair, but it's one that the typical tools for finding bugs, tests and static analysis, cannot actually help with.

Desktop Linux is still an extremely niche userbase, even with SteamOS and Microsoft doing its absolute best to aggravate users.

Fair!

Harder than C?

Oh, I thought by "already" you meant right now. I would expect that you can use any Wayland-compatible compositor once their Wayland support is complete, yeah.

Not sure about Steam.

For what it's worth, I agree with you about branches, and there are various ongoing discussions about how to make working with branches more convenient. I use an experimental feature called "advance branches" that makes it mostly fit my workflows, and the other benefits of jj are sufficient that I haven't switched back to git.

I create log files of runs, temporary helper scripts, build output, etc. in my working copy all the time.

The solution to this is to just have a more aggressive .gitignore. But also, note that the "working copy commit" isn't generally something you want to push or keep; think of it more like a combination of the git staging index and an automatic stash.

They explained pretty clearly that they use Linux exclusively for work.

In addition to not actually being correct, I don't think the information you've provided is particularly helpful in answering OP's question.