(somehow, Github renders this suggestion weirdly. I mean: remove trailing whitespaces, please, i.e., keep the line empty)

Here too.

As far as I understand this (very weird; why not just use '/' as a token and use the first and last element of the string) parsing step, this basically assumes that all files were generated from root. This invites potential footguns IMHO and also might lead to maybe unrelated files (something about boards/ e.g.) hogging the already quite crowded root path. I'd rather have a mapping somewhere, where the name of the generated file is mapped to the original source. It can be in this file, but maybe it makes sense to hook this directly into the generation somehow. This way, we would avoid risks of the generation and the edit links going potentially out of sync.

"tech debt", the code was different before and I only later realized one issue with it

I looked into different solutions for this and if I'm being honest all of them felt really weird. Currently the only reason we'd ever have documentation on that exact /doc/guides/generated path is when they are root files and I don't foresee new files outside of root being added to that path

As I said: I see it feasible to have some guide on a specific module or test, e.g., in a markdown file with that. But fine. I don't want to block the PR just because of that if you disagree.

Nah I get what you mean, however, any good solution would probably require moving away from the current setup for generated sites we have (because it grew a bit too big for the initial "hacky" solution already) so all my attempts of adressing the feedback ended up with unsatisfactory solutions