I will have a look, didn't even know about kernel.org, nobody before you mentioned it.

its mostly developer documentation about programming APIs, but there's also admin docs, not only at the admin-guide pages.

if the script would get executed whenever I start the machine or go out of standby. Which is not the case, sometimes it just doesn't happen and I have to do it manually.

what is its current trigger?

if yours is a systemd based system, it's often recommended to make a service unit file for the script, like this:

[Unit]
Name=restore gamma on resume
WantedBy=sleep.target

[Service]
After=sleep.target
Exec=/usr/local/bin/yourscript.sh

save this in /etc/systemd/system/gammasleep.service (runs services as root), and run systemctl daemon-reload for it to notice the new file. systemctl enable --now to start it and make it autostarted on boot.

I have written this from memory on phone, so it might need corrections, but this is basically it, plus edit the exec line. docs is in man systemd.service, man systemd.unit. man systemd.directives tells you which man page documents a specific key.

you can check logs with journalctl -u gammasleep.service. an f gives you a running log with shorter history.

probably I could have written all of this after you confirmed you did not use a systemd service yet...

It's all those little inconvenient and unreliable things that keep me from using Linux for anything that goes beyond browsing the web or doing office stuff

oh I felt the same when I first tried to switch to linux on my main desktop. everything was inconvenient without my usual tools and the system was breaking down from time to time. I got burned out, 2 years later I retried and now I haven't gone back to the windows install for months, and there's not much problems now. probably I was being clumsy and doing things the wrong way 2 years ago, but it's hard to tell because I don't remember.